Skip to content

SCEP request policy requirements

A SCEP server relies on request policies to define how its certificates are issued. If the request policies are not configured correctly, SCEP server creation fails when Certificate Manager - SaaS provisions the server's registration authority (RA) certificates.

You can use SCEP with any certificate authority that Certificate Manager - SaaS supports, as long as the certificate authority meets the requirements below. Configure the request policies described in this topic before you create the server. The exact request policy settings vary by your certificate authority and MDM.

Overview

Setting up a SCEP server requires three separate request policies, each of which serves a different purpose. All three request policies must use the same certificate authority type (for example, all Microsoft, or all DigiCert):

  • Issuing certificates to enrolling clients (the end-entity certificate).
  • Signing SCEP responses (the server's RA signing certificate).
  • Encrypting client requests (the server's RA encryption certificate).

Note

Certificate Manager - SaaS has no special "SCEP" request policy type. A SCEP server uses three ordinary request policies that you configure to serve three different purposes. The purpose comes from how you configure each request policy, not from a request policy type you select.

For information about creating request policies, see Creating a request policy.

Required request policies and settings

Request policy Purpose Required settings
End-entity (device) Issues the certificates that enrolling clients receive. Allow user-provided CSRs. Issue the certificate type your devices require.
RA signing Issues the certificate the server uses to sign SCEP responses. Allow user-provided CSRs.
RA encryption Issues the certificate clients use to encrypt their requests to the server. Allow user-provided CSRs.

Note

All three request policies must allow user-provided CSRs. Enrolling clients provide their own CSR for the end-entity certificate, and Certificate Manager - SaaS provides the CSRs for the RA certificates.

Certificate authority requirements

The certificate authority behind the RA request policies must issue the RA certificates that Certificate Manager - SaaS requests. The CA must:

  • Allow enrollment from a user-provided CSR.
  • Issue the RA signing certificate with the Digital Signature key usage, and the RA encryption certificate with the Key Encipherment key usage.
  • Keep the two usages separate. The RA signing certificate must not also have Key Encipherment, and the RA encryption certificate must not also have Digital Signature.

The key usages that matter are the ones on the certificates the CA issues, which your CA template controls. If the CA refuses an RA request, or issues an RA certificate with the wrong or overlapping key usages, the server's Status changes to Failed. For how to recover, see Server status.

If you configure key usage on an RA request policy, make sure it matches the RA's purpose: Digital Signature only on the RA signing request policy, and Key Encipherment only on the RA encryption request policy. Setting both usages on either RA request policy causes the server to fail. If you do not configure key usage on the request policy, the certificate authority's own template determines the usage on the issued certificate.

Why the request policies must use the same certificate authority type

The RA certificates represent the issuing certificate authority to enrolling devices. Devices validate the RA certificates against the CA-chain policy supplied by their MDM, so all three request policies must use the same certificate authority type.

When you create a SCEP server, you select the End Entity Request Policy first. Certificate Manager - SaaS then filters the Registration Authority Signing Request Policy and Registration Authority Encryption Request Policy lists to show only request policies that use the same certificate authority type. Changing the End Entity Request Policy to one with a different certificate authority type clears both RA selections.

Common misconfigurations

  • Request policies use different certificate authority types. All three request policies must use the same certificate authority type. The creation wizard prevents this by filtering the RA request policy lists to match the certificate authority type of the selected End Entity Request Policy.
  • A request policy does not allow user-provided CSRs. All three request policies must allow user-provided CSRs, or SCEP server creation fails.
  • The CA issues RA certificates with the wrong key usages. The RA signing certificate needs Digital Signature and the RA encryption certificate needs Key Encipherment, with no overlap between them. Check the CA template behind each RA request policy.
  • A single, broad request policy is used for all three roles. Use separate request policies for the end-entity, RA signing, and RA encryption roles so that you can control each certificate type independently.