Integrating Microsoft AD CS server with MDM
Microsoft Active Directory Certificate Services (AD CS) provides digital certificates that can be used to encrypt, digitally sign and authenticate users and devices on a network. By integrating Microsoft AD CS with Mobile Device Manager Plus, IT admins can leverage AD and Groups Policy for certificate registration and assignments. It allows organizations to dynamically create user-specific certificates, distribute certificates at large scale and automatically renew the certificates on devices, thereby ensuring data security and compliance to organizational standards.
NDES must be installed in a Windows Server machine
- Click on Start Menu, select Run, type mmc and click OK.
- Click File and select Add/Remove Snap-in....Select Certificate Templates, click Add and then click OK.
- Right click Certificate Template and select Manage.
- Click on User and select Duplicate Template.
- Specify a Template display name and save it by clicking OK.
- Click on Extensions,select Application Policies. Click Edit and select Client Authentication, to add it to Application Policies.
- Click on Cryptography and specify the Minimum key size. The recommended key size is 2048, as it enhances the security. This key size is to be specified while configuring SCEP in MDM.
- Click on Security and select the Group(s), to which the policy is to be applied. Ensure Enroll is an allowed permission for the selected domain(s).
- Click on Subject Name and select Supply in the request, for subject names to be specified in the certificate request.
- Add Certificate Authority as a snap-in in the Microsoft Management Console(MMC).
- Expand Certification Authority and right-click on Certificate Templates. Click New and select Certificate Template to Issue.
- Select the Certificate Template created before and click OK.
- Click on Start Menu, select Run, type regedit and click OK.
- Expand HKEY_LOCAL_MACHINE -> SOFTWARE -> Microsoft -> Cryptography -> MSCEP.
- Right-click on Encryption Template and click Modify.
- Specify the name of the created Certificate Template for Value date. Repeat the same for GeneralPurposeTemplate and SignatureTemplate. Restart the server machine once for the changes to take place
To change the default certificate template used by Microsoft NDES, windows registry values are to be changed.
- Open regedit and expand HKEY_LOCAL_MACHINE -> SOFTWARE -> Microsoft -> Cryptography -> MSCEP -> UseSinglePassword.
- Right-click UseSinglePassword and change the value of data as 1.
If you're using Challenge password(recommended), then registry values must be modified to prevent expiry of Challenge password.
After configuration is complete, restart the NDES Server.
Configuring SCEP in MDM
- The value for Subject should be in LDAP DN format as explained here.
Follow the steps given below to configure SCEP in MDM
- On the MDM console, navigate to Device Mgmt -> Certificates
- Click on the CA Servers tab and click on Add CA server
- Provide the following details:
|Server Type||Specify server type as Microsoft AD CS.|
|Certificate Authority Name||Specify the name of the Certificate Authority issuing certificates.|
|Server URL||The URL to be specified in the device to obtain certificate. Provide HTTP Server URL, if the SCEP server is within the organization network and not exposed to external networks. The certificate is requested through this URL.|
|Add CA Certificate||Upload the Certificate Authority's certificate|
Creating templates for the CA servers
For creating user-specific certificates, a template needs to be configured based on which all the certificates will be issued by the CA.
Follow the steps given below to configure the template on MDM:
- On the MDM console, navigate to Device Mgmt -> Certificates.
- Click on Templates tab and click on Add Templates
- Select the server to which the template belongs
- Provide the following details:
|Certificate Template Name||Specify the certificate template name.|
|Subject||Specify the Subject DN that needs to be present in the certificate. You can use dynamic keys such as %username%, %email%, %firstname% to fetch the the corresponding details mapped to the device. For instance, you can specify C=US,O=Zylker,OU=Zylker,CN=%firstname%.
|Subject Alternative Name Type||Specify one of the following values None, RFC 822 Name, DNS Name or Uniform Resource Identifier for the subject alternative name type|
|Subject Alternative Name Value (Can be configured only if Subject Alternative Name Type is configured)||Specify a value for subject alternative name value. The values to be entered can include DNS name, URI or email. For instance, you can use the dynamic key %email% for the subject alternative name value, email.|
|NT Principal Name||Specify the NT Principal Name used in the organization.|
|Maximum Number of Failed Attempts||Maximum number of failed validation attempts allowed to obtain the certificate from the CA. Once the maximum limit is exceeded, users will be temporarily restrcted from attempting to vaildate the user account.|
|Time interval between attempts||Time to wait before subsequent attempts to obtain the certificate|
|Challenge Type||A pre-shared secret key provided by the CA, which adds additional layer of security. If Static is chosen, the challenge password will be submitted to the SCEP server for authentication and all the devices will use the same password for authentication. If Dynamic is chosen, each device will use a unique challenge password for authentication. If None is chosen, no authentication is requested by the SCEP server and any device can receive the certificate by accessing the SCEP URL.|
|Enrollment Challenge Password (Can be configured only if Static challenge type is selected)||Provide the challenge password to be used for authentication.|
|Challenge URL (Configurable only if challenge type is set as Dynamic)||Specify the AD CS MSCEP admin endpoint URL.|
|Challenge Username (Configurable only if challenge type is set as Dynamic)||Specify the AD CS MSCEP admin username to be used.|
|Challenge Password (Configurable only if challenge type is set as Dynamic)||Specify the AD CS MSCEP admin password to be used.|
|Key Size||Specify whether the key is 1024 or 2048 bits|
|Use as Digital Signature||Enabling this option ensures the certificate can be used for Digital Signature|
|Use for Key Encipherment||Enabling this option ensures the certificate can be used for Key Encipherment|
|Certificate Auto Renewal||Enabling this option ensures the certificates are renewed automatically before it expires.|
|Certificate Automatic Renewal Before||Specify the number of days before which the the certificate must be auto-renewed.|
Creating a SCEP profile
To distribute certificates to managed devices, a SCEP profile need to associated with these devices. Follow the steps given below to create and associate the SCEP profile to devices
- Navigate to Device Mgmt -> Profiles and create either an Apple, Android or Windows profile.
- Select SCEP from the left pane.
- Select the created Certificate template.
- Click on Save and publish the profile.
It is recommended to distribute the profile to a device for testing before distributing it to your production environment. Once testing is complete, you can distribute the profile to your production environment using Groups.