Service configuration file - Single configuration

AppSettings.json

This file contains parameters to get access to the external services & configuration uses for the current service instance

This file is the standard configuration file for .NET 6 Core applications. It may be case-insensitive on Windows depending on specific Windows configurations. As a standard configuration file, there are many .NET Core options which need or can be specified. Worth mentioning, the "AllowedHosts" is and needs to be configured in this file. (Typically, if no security worries, we can simply specify it as "*". For more, please check https://docs.microsoft.com/en-us/dotnet/api/microsoft.aspnetcore.hostfiltering.hostfilteringoptions.allowedhosts?view=aspnetcore-6.0)

This file also contains parameters to get access to the external services & configuration uses for the current service instance.

Hint. By the first installation rename the file template_AppSettings.json to AppSettings.json This file contains all parameters required for service configuration and requires only to fill with the real values (e.g. URLs for the DPE services)

Configuration name

Multiple configurations can be defined for the service, and one configuration must be specified to use. To specify configuration used for the current service instance, add the parameter "ConfigurationName" to the file appsettings.json. E.g.

JS

"ConfigurationName": "1-st Configuration"

External services

Credentials encryption

Warning!

All credentials used for access to external services (login & password) are encrypted in the configuration file at service start.
To change the credentials, just enter new login and / or password in plain text. Service read the new unencrypted credentials and encrypted it at the next start
Login and password must not be started from *1* sequence

Parameter service

Service get access to the parameters stored in the DigaSystem registry via DPE Parameter service. All registries are read in followed sequence

Global registry
Local registry (overwrite parameters from global registry)
User registry (overwrite parameters from global & local registry)

To provide access to the Parameter service, add the configuration section "ParameterService" to the file appsettings.json. E.g.

JSON

"ParameterService": {
  "Host": "http://localhost/DpeWebApplication/",
  "Username": "",
  "Password": ""
}

Rights service

Service get access to the user rights via DPE Rights service. To provide access to the Rights service, add the configuration section "RightsService" to the file appsettings.json. E.g.

JSON

"RightsService": {
  "Host": "http://localhost/DpeWebApplication/",
  "Username": "",
  "Password": ""
}

Log service

The service uses the DPE Log service to log all errors. If the log service isn't available, the file log will be used. To provide access to the DPE Log service, add the configuration section "LogService" to the file appsettings.json. E.g.

JSON

"LogService": {
  "Host": "http://localhost/DpeWebApplication/",
  "Username": "",
  "Password": ""
}