Search…
⌃K

Static Validation

AppConfig:StaticValidation:Enabled

Applicable to version 1.6 and above
Value: true or false
Description: This setting helps you to request certificates from 3rd-party MDM systems (i.e. other than Intune and JAMF).
True: SCEPman listens at the additional SCEP server endpoint with the path /static. Use in conjunction with AppConfig:StaticValidation:RequestPassword. False (default): SCEPman does not issue certificates for 3rd-party MDM systems (i.e. other than Intune and JAMF).

AppConfig:StaticValidation:RequestPassword

Applicable to version 1.6 and above
Value: String
Description: A challenge password that a 3rd-party MDM system must include in every SCEP request to acquire a certificate. Only used if AppConfig:StaticValidation:Enabled is set to true.
We recommend to define this setting as Secret in Azure Key Vault. The Secret must have the name AppConfig--StaticValidation--RequestPassword.

AppConfig:StaticValidation:ValidityPeriodDays

Applicable to version 1.7 and above
Value: Positive Integer
Description: This setting further reduces the global ValidityPeriodDays for the Static endpoint. For example, you may define a low value like 10 days here and reduce the validity of certificates issued over the static endpoint, while still having a long validity for your regular client certificates.

AppConfig:StaticValidation:EnableCertificateStorage

Applicable to version 2.3 and above
SCEPman Enterprise Edition only
Value: true or false (default)
Description: When requesting certificates via the static endpoint, SCEPman stores those requested certificates in the Storage Account in Azure if this is set to true. This will make the issued certificates appear in SCEPman Certificate Master, where you can view and revoke them. If set to false or not set, SCEPman will not store issued certificates and the certificates are visible only in the logs or if the SCEP client stores them somewhere.