Create a Mac or iOS SCEP Profiles Policy

This policy configures Simple Certificate Enrollment Protocol (SCEP) for your macOS and iOS devices. SCEP makes issuing digital certificates easier, more secure, and scalable. You’ll need a Certificate Authority (CA) to issue the device credentials using SCEP. The fields in this SCEP Profiles policy are added to the SCEP payload.

The macOS policy works on all JumpCloud macOS supported operating systems that are enrolled in Mobile Device Management (MDM). The iOS policy works on all JumpCloud iOS and iPadOS supported operating systems on devices that are enrolled in MDM.   

To create a macOS or iOS SCEP Profiles Policy:

  1. Log in to the JumpCloud Admin Portal.
  2. Go to DEVICE MANAGEMENT > Policy Management.
  3. In the All tab, click (+).
  4. On the New Policy panel, select the Mac or the iOS tab.
  5. Select the Mac or iOS SCEP Profiles policy from the list, then click configure.
  6. (Optional) Enter a new name for the policy or keep the default. Policy names must be unique.
  7. For Policy Notes, enter details like when you created the policy, where you tested it, and where you deployed it.
  8. (Optional) Enter a Base64 encoded string in the Fingerprint field.
    1. You will need to convert the current SHA1 or SHA256 fingerprint, represented as a series of hexadecimal values, to a Base64 encoding of a “bytes” object. From the macOS Terminal, run the following command, replacing the fingerprint value with your Certificate Authority’s:
      • Note: The characters delimiting the hexadecimal pairs within the fingerprint value are not sensitive – meaning that strings using colons, spaces, or no delimiters at all are equally valid for input.
      • Enter the resulting Base64 encoded string in the Fingerprint field.

echo "11:22:33:44:aa:bb:cc:dd" | xxd -r -p | base64

  1. For Challenge, enter the pre-shared secret, which generally identifies the request or the user who is requesting the profile. This policy type requires a static challenge and will not work with a dynamic challenge.
  2. Click Key Size to choose the size of the key: 1024, 2048, or 4096 bits. The default is 1024.
  3. For Subject, click Add Value and enter the Object Identifier (OID) and its value for the X.500 name. For example: /C=US/O=ABCEnterprise/CN=foo/1.2.5.3=bar. This field supports one OID statement, so you should encapsulate all the fields in a single statement.
  4. For Retries, enter the number of times the device should retry if the server sends a Pending response. The default is 3.
  5. Select Extractable Key to export the private key from the keychain. Generally, you should not export this private key. 
  6. For Key Usage, enter the purpose for the SCEP certificate and keypair, and which bitmask to use for the private key. Enter Signing for digital signature or Encryption for encryption.
  7. For Retry Delay, enter the number of seconds to wait between subsequent retries. The first retry is attempted without this delay. The default is 10. 
  8. For URL, enter the SCEP server’s URL. For example: http://scep-server/cgi-bin/pkiclient.exe.
  9. For Name, enter a unique name for the payload that’s understood by the SCEP server. For example, WiFi Certificate. If a CA has multiple CA certificates, this field is used to distinguish which is required. 
  10. Select Include Root Certificate to upload the certificate for the Certificate Authority to add to the device’s trusted anchors list. 
  11. If you selected Include Root Certificate, click upload file for Root Certificate This certificate should not include public keys and should be in the .cer or .crt format. File size must be smaller than 1 MB. 
  12. Select Set Subject Alternative Name to determine subject alternative names characteristics for the SCEP certificate.
  13. If you selected Set Subject Alternative Name, under Subject Alternative Name choose one or more values that are required by the CA to issue a certificate:
    1. For DNS Name, enter the DNS name of the CA server. For example, mac1.example.com. This can be a variable from the device’s current status as drawn from Apple’s list of hardware variables. 
    2. For Principal, enter the name of the NT principal used in the organization. This can be a variable from the device’s current status as drawn from Apple’s list of hardware variables. 
    3. For RFC 822, enter the email address needed for the certificate request.This can be a variable from the device’s current status as drawn from Apple’s list of hardware variables. 
    4. For URI, enter the fully-qualified Uniform Resource Identifier for the CA server. This can be a variable from the device’s current status as drawn from Apple’s list of hardware variables.
  1. (Optional) Select the Device Groups tab. Select one or more device groups where you’ll apply this policy. For device groups with multiple OS member types, the policy is applied only to the supported OS.
  2. (Optional) Select the Devices tab. Select one or more devices where you’ll apply this policy.

Tip:

For this policy to take effect, you must specify a device or a device group in Step 10 or Step 11.

  1. Click save.

Still Have Questions?

If you cannot find an answer to your question in our FAQ, you can always contact us.

Submit a Case