SCEP Profile
SCEP Profile specifies the configurations of the SCEP server behaviour. It holds the configuration listed below:
| Configuration | Purpose | Default Value | Mandatory |
|---|---|---|---|
| Name | SCEP Profile Name | Yes | |
| Description | Description of the SCEP Profile | No | |
| Challenge Source | How an enrollment is authenticated: with the Challenge Password of the profile, or with the challenge of a certificate registration. See Challenge source | Protocol Default | No |
| Challenge Password | Challenge Password to authorize certificate request | No | |
| Renewal Threshold | Number of days before the certificate expiration date to allow renewal request | Half-time of the validity period of the Certificate | No |
| Include CA Certificate | Include certificate of the issuer in the certificate response | false | No |
| Include CA Certificate Chain | Include complete chain in the certificate response | false | No |
| Enable Intune | Enable Microsoft Intune integration for certificate request validation | false | No |
| Intune Tenant | Microsoft Intune Tenant to be used for request Validation | No | |
| Intune Application ID | ID of the Microsoft Intune Application | No | |
| Intune Application Key | Secret to authenticate with the Intune application | No | |
| CA Certificate | Certificate to be used as SCEP CA certificate (for decryption and signing) | Yes |
SCEP Profile certificate requirements
The certificate to be used for the SCEP Profile should meet the following criteria
- Certificate should have associated private key managed by the platform
- The key algorithm should be one of the supported
RSAorECDSA - The key pair should have appropriate key set enabled (for encryption and signing)
For Microsoft Intune validation, there may be additional requirements for the certificate. See the Intune Integration Guide for more information.
Operations on SCEP Profile
The following operations can be performed on the SCEP Profile:
| Operation | Description |
|---|---|
| Create | Create a new SCEP Profile. New SCEP Profile is disabled by default |
| Update | Update configuration of already existing SCEP Profile |
| Delete | Delete existing SCEP Profile |
| Disable | Disable existing SCEP Profile. All request to disabled SCEP Profile will be rejected |
| Enable | Enable existing SCEP Profile |
Challenge source
With the challenge source Protocol Default, a request must carry the Challenge Password of the profile, when one is configured.
With Certificate Registration, an initial enrollment (PKCSReq) must match a registered certificate of the RA Profile that serves the request, by its subject DN, with the values exactly as registered, and by its full set of SANs. The challenge password of the request is the challenge of that registration. See Challenge source for how a failed request is refused.
With either challenge source, a renewal needs no challenge password, even for a certificate whose registration is Active. A renewal is a PKCSReq signed with the key of an issued certificate of the same RA Profile, with the same subject and no SANs that the certificate does not have.
The following restrictions apply to a profile with the challenge source Certificate Registration:
- A challenge password cannot be configured
- Intune cannot be enabled
- The CA certificate must have an RSA key