Kandji

Issue certificates in Kandji by connecting SCEPman as an External CA. Devices will be able to obtain certificates using SCEPman's static interface and a challenge password enrolled.

SCEPman can be connected to Kandji as an External CA via SCEPman's static interface, and a challenge password enrolled devices will be able to obtain certificates.

For more general information about other MDM solutions and SCEPman integration, please check here.

Enable Kandji Integration

Integration of SCEPman can be easily enabled via the following environment variables on SCEPman App Service:

You can differentiate between the SCEPman App Service and the Certificate Master by looking for the App Service without the "-cm" in its name

Setting

Description

Value

AppConfig:StaticValidation:Enabled

Enable 3rd-party validation

true to enable, false to disable

AppConfig:StaticValidation:RequestPassword

Certificate signing requests sent to SCEPman for signing are authenticated with this secure static password Recommendation: Store this secret in Azure KeyVault.

generate a 32 character password

AppConfig:StaticValidation:ValidityPeriodDays (optional)

Days certificates issued via Kandji are valid

365

AppConfig:StaticValidation:EnableCertificateStorage (optional)

Store requested certificates in the Storage Account, in order to show them in SCEPman Certificate Master

true to enable, false to disable

After adding or editing SCEPman configuration parameters, you need to restart the App Service.

Kandji Configuration

SCEPman Root Certificate

As a first step, you must deploy SCEPman's root certificate. Download this CA certificate via the SCEPman website:

In Kandji, navigate to Library on the left navigation bar and add a Certificate Library Item to your Blueprint.

To upload the certificate, first select PKCS #1-formatted certificate under Certificate type, secondly provide an optional name, upload your SCEPman CA certificate, and eventually save it.

SCEP Profile

The second step is to add a SCEP Profile to your Blueprint. Therefore, add a new SCEP Library Item and configure it as below:

URL: The static SCEP endpoint of SCEPman you configured above
Name: An optional SAN attribute
Challenge: Is required to authenticate CSR requests sent to SCEPman's static SCEP interface. It must match the value you have configured above.
Fingerprint: Optional CA fingerprint. It is highly recommended to configure this value as it provides an additional level of security. You can find it on your SCEPman website as CA Thumbprint.
Subject: Optional subject name. CN=$PROFILE_UUID will be automatically added from Kandji as default common name. Kandji allows you to add multiple CNs.

We have seen cases where macOS and iOS had problems in auto-selecting client certificates for network authentication purposes where more than two CNs were added.