
Five real-world public key infrastructure examples, how PKI works, and the key steps and pitfalls when you implement it.
How MDM manages certificates on iPhone and iPad: the APNs push certificate, SCEP and PKCS identity certificates, trusted roots, renewal and revocation.


Content writer, trio.so
iOS certificate management is how an organization gets the right digital certificates onto its iPhones and iPads, keeps them trusted and renews them before they expire. Three kinds matter. The Apple Push Notification service (APNs) certificate lets the MDM server reach every enrolled device, and it expires every year. Identity certificates, issued through SCEP or ACME or installed as a PKCS#12 file, let a device prove who it is to Wi-Fi, VPN and email. Root and intermediate CA certificates make the device trust your own certificate authority. An MDM installs all of them through configuration profiles, so users never handle a certificate signing request, and it should warn you before the APNs certificate expires, because a lapsed one cuts the MDM off from every device.
If you manage iPhones and iPads and want to know which certificates your MDM depends on and how to keep Wi-Fi, VPN and email working, the sections below go through each type in the order most teams meet them. (If you searched for iOS certificates to sign apps, that is a different thing: code-signing certificates are managed in your Apple Developer account.)
Without an MDM, every certificate on every device is a manual job. These are the problems that show up first.
An identity certificate starts with a key pair and a certificate signing request (CSR). Done by hand, someone creates the key and CSR with OpenSSL or Keychain Access, sends the CSR to a certificate authority (CA), downloads the signed certificate and converts it to the format the device needs. Every step is a chance to lose or expose the private key.
The signed certificate then has to reach the device, usually inside a configuration profile sent by email or a web page. Each user has to download it, install it and sometimes enter a password. Across hundreds of devices that means support tickets and devices that never finish.
Certificates expire on different schedules: the APNs certificate every year, Wi-Fi and VPN identity certificates when their validity ends, S/MIME email certificates on their own cycle. A missed renewal shows up as an outage: no MDM commands, no VPN, no Wi-Fi.
If you run an internal CA, every device needs its root certificate, and often an intermediate one, before it will trust the certificates that CA issues. Installing them by hand on each device is slow, and a device without the chain refuses the connection.
When a device is lost or a key is exposed, the certificate on it has to stop working. That means revoking it at the CA and removing it from the device, which is hard to do quickly without central control.
Every Apple MDM needs an APNs certificate. The MDM server uses Apple's push service to tell enrolled iPhones, iPads and Macs to check in, so without a valid certificate it cannot send any command. The certificate is created in Apple's Push Certificates Portal and is valid for one year.
The MDM creates the signing request for you. You download it from the MDM console; there is no OpenSSL step.
You sign in to the Push Certificates Portal (identity.apple.com/pushcert) with an Apple Account, upload the request and download the signed certificate. Use an account that IT keeps, not a personal one, because renewal has to happen with the same account.
Upload the certificate back to the MDM. When you renew the existing certificate in the portal, rather than creating a new one, devices keep working without any action. If a new certificate is created by mistake, every device has to enroll again, so always choose Renew.
Because the certificate lasts a year and the renewal involves Apple's portal, the risk is simply forgetting. A good MDM shows the expiry date and warns you before it arrives. Put the date in a shared calendar as well, and write down which Apple Account owns the certificate.
Most organizations also need identity certificates on their devices: for Wi-Fi with EAP-TLS, for VPN and for email signing and encryption. The Simple Certificate Enrollment Protocol (SCEP) lets each device request its own certificate from your CA, so the private key is created on the device and never travels. On recent Apple platforms, ACME with managed device attestation does the same job and can tie the key to the device's hardware.
Assign the payload to the devices or users that need the certificate, for example all company iPads or the sales team, together with the Wi-Fi or VPN payload that will use it.
Before the certificate expires, the MDM sends the SCEP payload again so the device requests a new certificate. How far ahead that happens depends on the MDM and your CA's validity period; check it before your first certificates expire.
Some certificates cannot be requested by the device, for example ones a vendor issues or that come from a CA without SCEP. For those, the MDM can install a PKCS#12 file (.p12 or .pfx), which holds the certificate and its private key.
Upload the .p12 file to the MDM's certificate payload and enter its password. Because the file contains a private key, keep it away from email and shared drives.
Decide what the certificate is for (Wi-Fi, VPN, email) and assign the payload only to the devices or users that need it.
Devices install the certificate and key from the profile, and the Wi-Fi, VPN or mail payload that refers to it can use it straight away.
To replace a certificate, push a profile with the new one and remove the old one. If a key was exposed, revoke the certificate at the CA as well, because removing it from devices does not stop a copy being used elsewhere.
Where the CA supports it, prefer SCEP or ACME, so that private keys never leave the device.
If you run an internal public key infrastructure (PKI), every device must trust your root CA, and usually one or more intermediate CAs. Without the chain, the device refuses identity certificates from that CA, warns that websites are not trusted and fails to join EAP-TLS Wi-Fi or VPN.
Add a trusted root certificate payload to the MDM with your root CA's certificate (.cer, .crt, .pem or .der), and the intermediate certificates if your CA uses them.
A root certificate installed through MDM is trusted automatically. A root certificate a user installs by hand is not fully trusted for websites until they turn it on in Settings.
On a single iPhone without an MDM:
Send the whole chain, root and intermediates, so the device can build the path from a certificate to the root without fetching anything.
When you add a new intermediate CA or retire an old one, update the trusted certificate payload so devices get the new chain and lose the old one.
Keep a list of every certificate type your devices depend on: the APNs certificate, each SCEP or ACME profile and its CA, any PKCS#12 certificates and the root chain, with their expiry dates and owners. Many MDMs show which profiles each device has installed.
Renew SCEP and ACME certificates through the MDM before they expire, and renew the APNs certificate in Apple's portal each year. PKCS#12 certificates have to be replaced by hand, so they need a calendar entry.
When a device is lost or compromised, revoke its certificates at the CA (which publishes the revocation through CRL or OCSP), remove the profiles from the device or wipe it, and issue new certificates to its replacement.
Go to Settings > General > VPN & Device Management, tap the profile that installed the certificate and tap Remove Profile. Certificates installed by an organization's MDM can only be removed by that organization, or by removing management altogether.
Here is how the pieces fit together for field sales iPads that need a certificate-based VPN.
On a Microsoft AD CS server, add the Network Device Enrollment Service (Microsoft's SCEP server) and a certificate template for VPN clients with client authentication and a one-year validity.
Add the root and issuing CA certificates to a trusted certificate payload.
Create a SCEP payload with the NDES URL, the challenge, a 2048-bit key, client authentication usage and a subject that includes the user name or device name.
Create an IKEv2 VPN payload that authenticates with the certificate from the SCEP payload, with the VPN server's address.
Assign the trusted certificate, SCEP and VPN payloads to the group of sales iPads.
Each iPad installs the root chain, requests its own certificate, installs it and sets up the VPN, without the user handling any certificate.
Track the certificates' expiry, and resend the SCEP payload before they expire so the VPN keeps working.
| Practice | What to do | Why |
|---|---|---|
| Renew the APNs certificate on time | Renew in Apple's portal with the same Apple Account, before the yearly expiry | A lapsed or replaced certificate cuts the MDM off from every device |
| Use SCEP or ACME for identity certificates | Let each device create its own key | Private keys never travel, and each device has its own certificate |
| Keep the trust chain current | Update the trusted certificate payload when CAs change | Avoids broken chains and trust warnings |
| Keep validity periods short | One or two years for device certificates | Limits the damage if a key is exposed |
| Limit who can enroll | Use challenge passwords and scope payloads to the right groups | Stops certificates being issued to the wrong devices |
| Revoke on loss | Revoke at the CA and remove the profile or wipe the device | A lost device's certificate cannot be reused |
| Document everything | Record each certificate, its CA, owner and expiry | Makes renewals, audits and handovers straightforward |
For the Wi-Fi side of certificate-based sign-in, see Wi-Fi authentication methods, and for directory certificate services, Active Directory security.
trio.so installs PKCS#12, SCEP and trusted root certificates on iPhones, iPads, Macs and Windows PCs through a certificate policy. It enrolls company iPhones and iPads through Apple Business and warns you before the Apple push (APNs) certificate expires. See Apple device management.

Certificates keep iPhones and iPads connected to the MDM, to Wi-Fi, to VPN and to email. Renew the APNs certificate every year with the same account, let devices request their own identity certificates through SCEP or ACME, install PKCS#12 files only where you must, keep the root chain current, and revoke certificates as soon as a device is lost. With an MDM doing the installing, users never have to touch a certificate.
Related reading: iPhone enrollment profiles, add MDM to Apple Business Manager, Apple VPP token and account-driven User Enrollment.
trio.so installs certificates on iPhones, iPads, Macs and Windows PCs, enrolls company iPhones and iPads through Apple Business, and warns you before the Apple push certificate expires.
trio.so brings device management, patching and security policies for Windows, macOS, Linux, iOS/iPadOS and Android into one console. Enroll a device and see it in the console within minutes.
trio.so brings device management, patching and security policies for Windows, macOS, Linux, iOS/iPadOS and Android into one console. Enroll a device and see it in the console within minutes.





Have questions? We've got answers. This section covers some of the most commonly asked questions related to this topic.
Related
The related industry news, interviews, technologies, and resources.

Five real-world public key infrastructure examples, how PKI works, and the key steps and pitfalls when you implement it.

What AD CS is, best practices for a Microsoft certificate authority, and how to close the known AD CS attack paths such as ESC1.

Wondering how to strengthen your security? Explore the five essential certificate management best practices every organization should implement.

How to create and renew the Apple push (APNs) certificate your MDM needs, what happens when it expires, and how to avoid re-enrolling devices.

Android certificate management enables secure device authentication and encrypted communications through systematic deployment and lifecycle control of digital certificates.
14-day free trial. No credit card required.
trio.so for MSPs: one console, separate clients