Configuration reference

The .NET version is configured in appsettings.json, next to the application. Secrets (webhook keys, credentials for your systems) never go there: they go in the secrets file.

Format

Keys are nested JSON sections. The Connector:filesystem:OutputPath key is written like this:

{
  "Connector": {
    "filesystem": {
      "OutputPath": "D:\\SESARWebHook\\Output\\"
    }
  }
}

In a Windows path, double each backslash. As in any ASP.NET Core application, an environment variable can replace a key, with __ as the separator: Connector__filesystem__OutputPath.

Keys

Key	Default	Effect
DefaultConnectorId	filesystem	Connector called by POST /api/webhook.
HandlersPath	Handlers, in the application folder	Folder of handler DLLs. The path is used as is: ~ is not resolved. The POST /api/handlers/rescan route ignores this setting and reads the default folder again.
ConnectorsSecretsPath	connectors.secrets.json, in the application folder	Full path of the secrets file, file name included.
FileEntropy	empty	DPAPI entropy, in Base64. See Secrets and DPAPI.
DataProtectionScope	CurrentUser	DPAPI scope: CurrentUser or LocalMachine. Any other value gives CurrentUser.
EnableDebugEndpoints	false	true turns on the /api/debug/* routes. Never in production.
Connector:{id}:*	depends on the connector	Settings of a built-in connector: see its page.
Connector:generic:DefaultHandlerId	none	Handler called by POST /api/webhook/generic.
Handler:{id}:*	none	Settings of a handler, passed to its Initialize.
AllowedHosts	*	Host names accepted by ASP.NET Core. Restrict it to your server's name.
Logging:LogLevel	Information, Warning for Microsoft.AspNetCore	ASP.NET Core logging.

Keys without effect in this version

These keys appear in appsettings.json, but no processing applies them:

Key	What it actually does
Connector:{id}:Enabled	Shown by GET /api/connectors. It does not disable the connector: it processes the requests received at its address.
Handler:{id}:Enabled	Shown by GET /api/handlers. Same limit.
EnableDetailedLogging	Shown by GET /api/health/status.
LogPath	No log is written there.

For a connector never to be called, leave reachable only the address SESAR uses: see Secure the deployment.

Settings and secrets of a connector or handler

For each connector or handler, the application merges:

1. the keys of its section in appsettings.json (Connector:{id} or Handler:{id});
2. its secrets in the secrets file (Connectors.{id}.Secrets or Handlers.{id}.Secrets).

A secret wins over a key with the same name. The result is read only once, then kept in memory: restart the application after any change.