Certificates can be distributed manually or through configuration profiles on iPhone, iPad, Apple Vision Pro, and Mac. On mobile devices, users tap a certificate to review and install it; protected identity certificates require a password. On Mac, users open certificates in Keychain Access, verify their contents, choose a keychain—typically the login keychain—and add them. Certificates whose authenticity cannot be verified are marked untrusted, allowing users to decide whether to install them.
Configuration profiles support several certificate deployment methods: Active Directory Certificate Services for macOS, PKCS #12 identity certificates, ACME, and SCEP. Active Directory enrollment can provision machine or user identities, while ACME and SCEP generate certificate signing requests with the private key retained on the device. Keys may optionally be hardware-bound. PKCS #12 certificates are provisioned in password-protected files, and profiles can include the password to avoid user prompts.
Certificate payloads can be paired with services such as Wi-Fi EAP-TLS in the same profile, enabling authentication with the newly issued identity. Administrators must renew certificates before expiration; device management services can inspect installed certificates and deploy replacements. Active Directory certificates deployed through device profiles renew automatically by default on macOS 13 and later, though administrators can change this behavior.
Management services can inventory and remove certificates they installed. OCSP enables periodic revocation checks on supported systems. Users can manually remove certificates through device-management settings on mobile devices or Keychain Access on macOS, but removing certificates required by networks or accounts can interrupt access.
Article timeline
Build this article’s timeline
Extract dated events, key actors, and open questions using the same timeline analysis available in Signal.
Comments
Login to view and post comments.