# Simple Certificate Enrollment Protocol (SCEP)

Last updated: August 14, 2026

Simple Certificate Enrollment Protocol (SCEP) is a protocol standard used in MDM for automated, scalable certificate management. This page explains how SCEP enables certificate-based authentication for Wi-Fi, VPN, and email services without user intervention, eliminating the manual overhead of distributing certificates across large organizations. It covers supported SCEP CA integrations including Generic SCEP, ACME, DigiCert, Microsoft AD CS (NDES), and EJBCA, along with the full set of configurable SCEP profile settings available in MDM.

Simple Certificate Enrollment Protocol (SCEP) is a protocol standard used for certificate management. SCEP is predominantly used for certificate-based authentication, whereby access to services such as Wi-Fi, VPN, and securing email through encryption is carried out using certificates.

The major advantages of certificate-based authentication are:

- Zero-user intervention as users are authenticated via certificates.
- Secure network communication as the data is encrypted and authenticated using certificates.

However, manually distributing certificates is a cumbersome task for IT administrators in large-scale organizations. SCEP helps network administrators easily install certificates on devices. SCEP provides a simplified and scalable method for handling certificates in large organizations. The difference between Certificate and SCEP is that a SCEP policy is used for distributing client certificates to devices, while a Certificate policy distributes CA certificates to devices.

> The device directly contacts the SCEP server to generate the certificate; therefore, ensure the SCEP server is reachable from the device. It is not necessary for the SCEP server to be reachable from MDM.

## Configuring SCEP in MDM

1. You can verify server details such as the enrollment challenge password from **https://<your-server>/CertSrv/mscep_admin** and **http://<Your-Server>/crtsrv/mscep/mscep.dll**

## Types of SCEP Integrations

[Generic SCEP CA Integration](https://www.manageengine.com/mobile-device-management/help/certificate_management/mdm_integrating_generic_scep.html)

[ACME CA Integration](https://www.manageengine.com/mobile-device-management/help/certificate_management/mdm_integrating_ACME.html)

[DigiCert Integration](https://www.manageengine.com/mobile-device-management/help/certificate_management/mdm_digicert_certificate_management.html)

[Microsoft AD CS Integration](https://www.manageengine.com/mobile-device-management/help/certificate_management/mdm_integrating_microsoft_adcs.html)

[EJBCA CA Integration](https://www.manageengine.com/mobile-device-management/help/certificate_management/mdm_integrating_ejbca.html)

| PROFILE SETTINGS | DESCRIPTION |
|---|---|
| SCEP Configuration Name | The user-defined configuration name, which is used to refer to this configuration in other configurations such as Wi-Fi, VPN, etc. |
| SCEP SETTINGS |  |
| Server URL | The URL to be specified in the device to obtain a certificate. Provide an 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.<br><br>For [NDES](https://social.technet.microsoft.com/wiki/contents/articles/9063.network-device-enrollment-service-ndes-in-active-directory-certificate-services-ad-cs.aspx), the server URL format: **https://&lt;your-server&gt;/CertSrv/mscep/mscep.dll** |
| Certificate Authority Name | Specify the name of the Certificate Authority issuing certificates. |
| Subject | Specify the details (%username%, %email%, %domainname%, %devicename%) to map the corresponding details in the device.<br><br>**Note:** CN=%firstname%,OU=Zylker,O=Zylker,DC=Zylker,DC=com |
| Subject Alternative Name Type | Specify the alternate details (RFC 822 Name, DNS Name, Uniform Resource Identifier). |
| Subject Alternative Name Type Value **(Can be configured only if Subject Alternative Name Type is configured)** | Specify the value for alternative name type. |
| NT Principal Name | Specify the NT Principal Name used in the organization. |
| Maximum Number of Failed Attempts | Number of attempts to obtain the certificate from the CA. |
| Time interval between attempts | Time to wait before subsequent attempts to obtain certificate. |
| Challenge Type | A pre-shared secret key provided by the CA, which adds an additional layer of security. |
| Enrollment Challenge Password | Provide the challenge password to be used. |
| Key Size | Specify whether the key is 1024 or 2048 bits. |
| Use as Digital Signature | Enabling ensures the certificate can be used as a digital signature. |
| Use for Key Encipherment | Enabling ensures the certificate can be used for key encipherment. |

## Frequently Asked Questions

### 1. What's the difference between a Certificate profile and a SCEP profile?

A Certificate profile distributes CA certificates to devices, while a SCEP profile is used for distributing user-specific client certificates to devices.

### 2. Does the SCEP server need to be reachable from the MDM server?

No. The device contacts the SCEP server directly to generate the certificate, so the SCEP server only needs to be reachable from the device, not from MDM.

### 3. Which certificate authorities can be integrated with MDM using SCEP?

MDM supports Generic SCEP CA, ACME CA, DigiCert, Microsoft AD CS (NDES), and EJBCA CA integrations.