Jamf Validation
These settings should only be applied to the SCEPman App Service, not the Certificate Master. Please refer to Application Settings.
Jamf is available in SCEPman version 1.7 and above
AppConfig:JamfValidation:Enabled
Value: true or false
Description: This setting helps you to request certificates via the Jamf MDM system.
True: SCEPman listens at the additional SCEP server endpoint with the path /jamf. Use in conjunction with AppConfig:JamfValidation:RequestPassword. False (default): SCEPman does not issue certificates for Jamf.
AppConfig:JamfValidation:DefaultEkus
Applicable to version 2.8 and above
Value: Oids of the extended key usages (EKUs) that are added to the certificate if the Jamf endpoint is used. The Oids are separated by a comma, semicolon, or space. The default is Client Authentication (1.3.6.1.5.5.7.3.2)
Description: If a certificate request does not contain any EKUs, SCEPman adds the EKUs defined in this setting to the certificate. If AppConfig:UseRequestedKeyUsages is set to false, the EKUs defined in this setting will be added to the certificate even if the certificate request contains EKUs.
AppConfig:JamfValidation:DefaultKeyUsage
Applicable to version 2.8 and above
Value: EncipherOnly|CrlSign|KeyCertSign|KeyAgreement|DataEncipherment|KeyEncipherment|NonRepudiation|DigitalSignature|DecipherOnly (defaults are in italic)
Description: If a certificate request does not contain a Key Usage, SCEPman adds the Key Usage defined in this setting to the certificate. If AppConfig:UseRequestedKeyUsages is set to false, the Key Usage defined in this setting will be added to the certificate even if the certificate request contains a Key Usage.
AppConfig:JamfValidation:RequestPassword
Value: String
Description: A challenge password (max 32 characters) that Jamf must include in every SCEP request to acquire a certificate. Only used if AppConfig:JamfValidation:Enabled is set to true.
We recommend to define this setting as Secret in Azure Key Vault. The Secret must have the name AppConfig--JamfValidation--RequestPassword.
AppConfig:JamfValidation:ValidityPeriodDays
Value: Positive Integer
Description: This setting further reduces the global ValidityPeriodDays for the Jamf endpoint.
AppConfig:JamfValidation:URL
Value: String
Description: The root URL of your Jamf instance. If you use Jamf Cloud, this will probably look like https://your-instance.jamfcloud.com/.
AppConfig:JamfValidation:ClientID
Applicable to version 2.9 and above
Value: String
Description: ClientID and ClientSecret are an alternative to APIUsername and APIPassword.
Enter the Client ID of an API Client matching the Client Secret configured in the AppConfig:JamfValidation:ClientSecret setting. Refer to the Jamf documentation on how to create an API Role and API Client. The API Client must have a role with these permissions:
Read Mobile Devices
Read Computers
Read User
AppConfig:JamfValidation:ClientSecret
Applicable to version 2.9 and above
Value: String
Description: The Client Secret value for the API Client configuration in AppConfig:JamfValidation:ClientID.
We recommend to define this setting as Secret in Azure Key Vault. The Secret must have the name AppConfig--JamfValidation--ClientSecret.
If you set this setting as a Secret in the Key Vault, you do not need to add the AppConfig:JamfValidation:ClientSecret to the SCEPman configuration anymore.
AppConfig:JamfValidation:APIUsername
Value: String
Description: Either use this and APIPassword or ClientID and ClientSecret. The name of a service account in Jamf that SCEPman uses to authenticate on your Jamf instance. SCEPman needs the following permissions to query for computers, devices, and users:
Computers -> Read
Mobile Devices -> Read
Users -> Read
AppConfig:JamfValidation:APIPassword
Value: String
Description: The password of the service account configured in AppConfig:JamfValidation:APIUsername.
We recommend to define this setting as Secret in Azure Key Vault. The Secret must have the name AppConfig--JamfValidation--APIPassword.
If you set this setting as a Secret in the Key Vault, you do not need to add the AppConfig:JamfValidation:APIPassword to the SCEPman configuration anymore.
AppConfig:JamfValidation:EnableCertificateStorage
Applicable to version 2.3 and above
SCEPman Enterprise Edition only
Value: true or false (default)
Description: When requesting certificates via the Jamf 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 manually. Additionally, certificates are revoked automatically if the corresponding Jamf object is deleted. If set to false, SCEPman will not store issued certificates and the certificates are visible only in the logs or if the SCEP client stores them somewhere. If this is not set, the behavior depends on the global setting AppConfig:EnableCertificateStorage.
Last updated