Client identity selection and chain presentation when an intermediate CA in the identity’s chain is revoked

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.

  1. 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?
  2. 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?
  3. 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.

Keep in mind that the Apple Developer Forums are primarily focused on helping folks with Apple APIs, developer tools, and so on. So, I can address the API side of this. It’s possible that someone else might chime in on your Safari, EAP-TLS, and MDM questions but, if not, my advice is that you seek formal help on that topic from Apple Support.

And that brings me to this:

Written by Naohito_Sasao in 858060021

1- 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 handling a URLSession client certificate challenge … ?

URLSession doesn’t automatically respond to client certificate authentication challenges, so this question is basically the same as question 3.

Written by Naohito_Sasao in 858060021

3- 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?

No. URLSession just prepends the certificate from the digital identity and then passes the entire certificate chain to the TLS peer.

Share and Enjoy
—
Quinn “The Eskimo!” @ Developer Technical Support @ Apple
let myEmail = "eskimo" + "1" + "@" + "apple.com"

Safari on iOS performs just two checks to find candidate client identities:

  1. If the certificate is not currently within its validity period (the Not Before and Not After times), it is filtered out.
  2. If the web server provided one or more Distinguished Names (DNs) in the client cert challenge, it filters out any identities whose certificate chain does not contain one of them.

If there's only one candidate, Safari uses that, otherwise it prompts the user to pick one.

Once an identity is is selected, it builds the best chain it can until it finds a fully trusted chain. The details for how it scores the "best chain" are very complex and not worth detailing here. In your situation you care about a revoked intermediate and a non-revoked intermediate. In this case it will use the non-revoked intermediate. Then this best chain is provided to the web server in the response to the client cert challenge.

So if the web server doesn't already have access to the non-revoked intermediate, make sure to install it on the device and Safari should provide it.


Bob Whiteman - Device management engineer