SCEP authentication¶
A SCEP server authenticates every enrollment request before it issues a certificate. When you create a SCEP server, you choose one of three authentication types: a static challenge, a dynamic challenge, or Intune.
The authentication type determines how clients prove they are authorized to enroll, and you set it in the Authentication Details step of the create wizard. If you manage devices with Microsoft Intune, use Intune authentication. For all other deployments, use a dynamic challenge.
Static challenge¶
A static challenge uses one shared enrollment secret for all certificate requests. Certificate Manager - SaaS generates a Challenge Password when you create the server, and every client presents that same secret with each request. The challenge password remains valid until you regenerate it.
A static challenge is simple to configure and works with any SCEP client, but the shared secret is long-lived and identical across all clients, which makes it less secure than a dynamic challenge.
Warning
Use a static challenge only for testing or evaluation, not in production. The shared challenge password is long-lived and identical for every client, so a single leaked secret lets any device enroll against the server. For production deployments, use a dynamic challenge.
Dynamic challenge¶
A dynamic challenge issues a unique, one-time challenge for each enrollment request. Instead of distributing a password to every client, you configure your mobile device management (MDM) platform with a credential that it uses to request a challenge from Certificate Manager - SaaS for each enrollment. This provides stronger security.
Dynamic challenge supports two credential types that the MDM uses to authenticate to Certificate Manager - SaaS:
- Service Account. A username and password. You can have Certificate Manager - SaaS generate the credentials (System Generated) or supply your own (Custom).
- Header Token. A single bearer token that the MDM sends in a request header.
Dynamic challenge requires an MDM that supports requesting a per-enrollment challenge.
Intune¶
With Intune authentication, Microsoft Intune issues the challenge. Intune puts a unique challenge in the SCEP certificate profile it sends to each managed device, and the device presents it when it enrolls. Certificate Manager - SaaS checks the challenge and the request with Intune before it issues the certificate. You don't distribute a password or configure a credential in the MDM.
Certificate Manager - SaaS connects to Intune through an Azure Cloud Provider. The cloud provider's Microsoft Entra application must have permission to validate Intune SCEP requests. You select the cloud provider when you create the server.
Intune authentication works only for devices that Intune manages. For the setup, see Integrate a SCEP server with Microsoft Intune.
Choosing an authentication type¶
If you manage devices with Microsoft Intune, use Intune authentication. For all other production deployments, use a dynamic challenge. Use a static challenge only for testing or evaluation, or for clients that cannot support a dynamic challenge.
Warning
For all production deployments, use a dynamic challenge or Intune. The static challenge password is long-lived and identical for every client, so a single leaked secret lets any device enroll against the server.
You select the authentication type when you create the server. For the configuration steps, see Configure a SCEP server.