SCEP device management payload settings for Apple devices
You can configure SCEP settings to obtain certificates from a certificate authority (CA) for Apple devices that enroll in a device management service. Use the SCEP payload to specify settings that allow the device to obtain certificates from a certificate authority (CA) using the Simple Certificate Enrollment Protocol (SCEP).
The SCEP payload supports the following. For more information, see Payload information. To see a list of SCEP variables, see Variables settings for device management payloads for Apple devices.
Supported payload identifier: com.apple.security.scep
Supported operating systems and channels: iOS, iPadOS, Shared iPad device, macOS device, macOS user, tvOS, watchOS 10, visionOS 1.1.
Supported enrollment methods: User Enrollment, Device Enrollment, Automated Device Enrollment.
Duplicates allowed: True—more than one SCEP payload can be delivered to a user or device.
You can use the settings in the table below with the SCEP payload.
Setting | Description | Required | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
URL | The address of the SCEP server. | Yes | |||||||||
Name | Any string understood by the certificate authority. It can be used to distinguish between instances. | No | |||||||||
Subject | The representation of an X.500 name represented as an array of OID and value. For example, /C=US/O=Apple Inc./CN=foo/1.2.5.3=bar, which translates to: [ [ [“C”, “US”] ], [ [“O”, “Apple Inc.”] ], ..., [ [ “1.2.5.3”, “bar” ] ] ] | No | |||||||||
Subject Alternative Name Type | Specify the type of an alternative name for the SCEP server. Types are RFC 822 Name, DNS Name, and Uniform Resource Identifier (URI). This can be the Uniform Resource Locator (URL), Uniform Resource Name (URN), or both. | No | |||||||||
Subject Alternative Name Value | The value of the subject alternative name. | No | |||||||||
NT Principal Name | The principal name to be used in the certificate request. (optional) | No | |||||||||
Retries | The number of times to poll the SCEP server for a signed certificate before giving up. | No | |||||||||
Retry Delay | The number of seconds to wait between poll attempts. | No | |||||||||
Challenge | The preshared secret the SCEP server uses to identify the request or user. | No | |||||||||
Certificate expiration notification threshold (macOS) | The number of days, in advance, before the certificate starts showing an expiration notification. | No | |||||||||
Key size | Select a key size (in bits), and—using the checkboxes below this field—select the acceptable uses of the key. The options are1024, 2048, and 4096. | No | |||||||||
Key usage | Select to use the key for any of the following:
| No | |||||||||
Fingerprint | If your CA uses HTTP, use this field to provide the fingerprint of the CA’s certificate, which the device uses to confirm the authenticity of the CA’s response during enrollment. You can enter a SHA1 or an MD5 fingerprint, or select a certificate to import its signature. | No | |||||||||
Allow export from the Keychain (macOS) | Allow the private key to be exported from the Keychain. | No | |||||||||
Allow access to all apps (macOS) | Allow all apps to access the certificate in keychain. Note: This key needs to be used in macOS to allow a third-party VPN agent to use a certificate for authentication. The certificate payload needs to be in the same profile as the ACME or SCEP payload. | No | |||||||||
Note: Each device management service developer implements these settings differently. To learn how SCEP settings are applied to your devices and users, consult your developer’s device management service documentation.