Azure KeyVault
Applicable to version 1.8 and above
Value: true or false
Description: This setting determines whether SCEPman generates its CA certificates with an Extended Key Usage extension. The extension is not required by the standards, but Cisco ISE sometimes requires it to make OCSP work.
True (default for 1.9 and above): SCEPman adds an Extended Key Usage extension to newly generated CA certificates.
False (default for 1.8 and before): SCEPman generates a CA certificate without Extended Key Usage extension.
The validity of the generated Root CA certificate in days. Defaults to 3650, i.e. about ten years. We recommend to not reduce this value, as this increases availability risks, with no security advantage -- stopping the distribution of the Root CA certificate is easy and much faster than waiting for the certificate expiration.
Changes can harm your service!
The length of the Root CA key in bits. New installations set this to 4096. If you remove the setting, it will default to 2048. It only applies when generating a new Root CA certificate, though.
Changes can harm your service!
The type of key created for the Root CA. RSA is a software-protected RSA key; RSA-HSM is HSM-protected. If you want to use an ECC key, please contact the SCEPman support for further instructions.
Changes can harm your service!
The Azure Key Vault URL. This setting is automatically configured during the setup.
This setting MUST be in the configuration of your App Service. It is NOT possible to define this setting as a Secret in Azure Key Vault!
Changes can harm your service!
The Root Certificate Name. This setting is automatically configured during the setup.
The name does not appear in the certificate itself and is only a reference to the CA certificate within Azure Key Vault. As it is part of the URL, there are name restrictions, like limitations to alphanumeric characters, numbers, and dashes.
Changes can harm your service!
The Root Certificate Subject. This setting is automatically configured during the setup. It is used only as input at the time of CA certificate creation and will not be used anyomre once a CA certificate exists.
Changes can harm your service!
Last modified 2mo ago