SCEPman Settings
Last updated
Was this helpful?
Last updated
Was this helpful?
The section describes additional settings for the behavior of SCEPman. All of these are optional, though, and we recommend just start with the defaults.
Settings can be added or changed manually if needed. Some changes can harm your service. Please carefully read all information about a setting before changing.
For each Setting, you can choose whether you want to define the setting in the App Service Configuration or in Azure Key Vault. If you define the same setting in both places, Azure Key Vault takes precedence.
We recommend defining settings in the App Service Configuration except for passwords.
All existing settings are available for both Windows and Linux App Services.
When configuring Environment Variables for Linux, colons must be replaced with two underscores.
For example, a Windows App Service accepts AppConfig:LicenseKey, while a Linux App Service accepts AppConfig__LicenseKey.
Especially for sensitive information, you can also configure settings as Secrets in Azure Key Vault. You must first grant edit rights to Secrets in the Azure Key Vault associated with your SCEPman instance to an administrator account. Then, you can use this administrator account to define new Secrets.
Remark: Use double dashes instead of colons in configuration names! For example, instead of AppConfig:DCValidation:RequestPassword, the Secret must be named AppConfig--DCValidation--RequestPassword.
We recommend using this type of configuration only for sensitive information.
