We deploy client-authentication identities (certificate + private key)
to iOS/iPadOS devices for mutual TLS and Wi-Fi EAP-TLS. The identities
are installed via MDM configuration profiles and used from Safari, from
our app via URLSession client certificate challenges, and by the system
for EAP-TLS.
The intermediate CA certificate in these identities’ chain (issued by a
publicly trusted root) will be revoked. A replacement intermediate
certificate with the same subject and public key, but a different serial
number, is valid, and the end-entity certificates will not be reissued.
The private keys are not exportable.
- If the revoked intermediate is known to the device through Apple’s
distributed revocation data, or only through the root CA’s CRL, does
iOS/iPadOS evaluate this when offering the identity for selection in
Safari, when handling a URLSession client certificate challenge, or
when using it for EAP-TLS? Could the identity be hidden, flagged, or
fail to be presented? - If we install the replacement intermediate on the device (e.g. via a
certificate payload in a configuration profile) and remove the
original, will the system build and present the chain through the
replacement certificate? - For URLSession, if our app supplies the chain explicitly in
URLCredential(identity:certificates:persistence:), is any revocation
evaluation performed on that chain on the client side?
The revocation is scheduled for 2026-11-20T09:00:00Z. Our users rely on
this system for patient care in medical institutions, so any guidance
before then would be greatly appreciated.