This document describes how the removal of the Client Authentication Extended Key Usage (EKU) from public CA-issued certificates, driven by the Chrome Root Program Policy, affects Cisco Expressway. It also describes the supported solution.
Digital certificates are electronic credentials issued by trusted Certificate Authorities (CAs) that secure communication between servers and clients by ensuring authentication, data integrity, and confidentiality. These certificates contain Extended Key Usage (EKU) fields that define their purpose:
Traditionally, a single certificate could contain both Server and Client Authentication EKUs, allowing it to serve dual purposes. This is particularly important for products like Cisco Expressway that act as both server and client in different connection scenarios.

The Chrome Root Program Policy requires root CA certificates included in the Chrome Root Store to be dedicated to TLS server authentication. Multi-purpose root hierarchies have been phased out, with enforcement from June 15, 2026. As a result, publicly trusted CAs no longer issue TLS certificates that contain the Client Authentication EKU.
Note: This policy applies only to certificates issued by public CAs. Private PKI and self-signed certificates are not affected by this policy.
– Support for separate server and client certificate for Expressway
Per Field Notice FN74362, all Cisco Expressway versions are affected:
| Product |
Affected Releases |
Impact |
| Expressway Core and Edge |
X14 (All versions) |
X14.0.0 through X14.3.7 - All releases affected |
| Expressway Core and Edge |
X15 (versions earlier than X15.5) |
X15.0.0 through X15.4.x – all releases affected. Upgrade to X15.5 or later. |
Cisco Expressway products (Expressway-C and Expressway-E) act as both server and client in various connection scenarios, requiring certificates with both Server and Client Authentication EKUs.
Expressway E as Server (Server Authentication EKU required):
Expressway E as Client (Client Authentication EKU required):
The Expressway Server Certificate is the certificate that historically carried the Client Authentication EKU for mTLS. It is used for these mTLS connections:
Browser-trusted public CAs no longer provide certificates with Client Authentication EKU, so the supported path for every deployment is:
Per Field Notice FN74362:
Cisco Expressway X15.5 is the fixed release that addresses the Chrome Root Program requirements. It lets Expressway use public CA certificates that contain only the Server Authentication EKU. Cisco recommends the latest available X15.5.x (or later) maintenance release.
Note: Both Cisco Expressway E and Expressway C must be upgraded to the same version.
Note: If you run X15.4, upgrade to X15.5 or later. X15.4 was an interim release that only partly addressed this issue and is no longer recommended.
Segregation of client and server certificates
UI and backend enhancements
Option to disable the Client Authentication EKU check
Note: When Expressway reuses a server-only certificate as its client certificate, the remote peer must also be configured to ignore the Client Authentication EKU

START: Do you use public CA certificates on Expressway?
│
├─ NO: Private PKI or self-signed
│ └─ Not affected by the policy. Upgrade to X15.5 or later is still recommended.
│
└─ YES: Public CA certificates in use
│
├─ Are they used for mTLS? (see Specific Affected Use Cases)
│
├─ NO: Server authentication only
│ └─ Server-only public certificates work. Upgrade to X15.5 or later
│ to allow server-only certificate upload and renewal on all nodes.
│
└─ YES: mTLS in use
├─ 1. Audit: list mTLS peers and the expiry date of any remaining
│ combined-EKU certificate (cannot be renewed)
├─ 2. Upgrade Expressway-C and Expressway-E to X15.5 or later
├─ 3. Expressway-C: deploy internal CA certificate (serverAuth + clientAuth)
├─ 4. Expressway-E: public CA server certificate (serverAuth only)
│ + internal CA client certificate,
│ OR disable Client Auth EKU check (peer must support it)
├─ 5. Distribute your root CA to all mTLS peers and partners
└─ 6. Add peers' roots to the Expressway trusted CA list, then test
both directions
Q: Do I need to worry about this if I use private PKI?
A: No. This policy only affects certificates issued by public root CAs. Private PKI and self-signed certificates are not affected.
Q: Can I still get a public CA certificate with Client Authentication EKU?
A: Not from a browser-trusted root. The major public CAs have stopped, and all Chrome-trusted CAs must stop by March 15, 2027. Some commercial CAs offer Client Authentication certificates from dedicated roots that browsers do not trust (for example IdenTrust Public Sector Root CA 1 or DigiCert Assured ID Root G2). These work only where every peer trusts that root, and they cannot be used for the Expressway-E server certificate. For details, see the Cisco blog “Changes to TLS clientAuth Certificates: Ensuring You’re Not Impacted”. Cisco recommends an internal (private) CA for Client Authentication certificates.
Q: What if I do not use mTLS connections?
A: If you only use standard TLS (server authentication), server-only certificates continue to work. However, check your use cases against the list in the Specific Affected Use Cases section, because some of them use mTLS by default.
Q: Will my standard HTTPS web connections to Expressway stop working?
A: No. Standard TLS connections are not affected. Browser access to Expressway works normally with server-only EKU certificates.
Q: Can I continue using my existing certificates?
A: An existing public certificate with combined EKU keeps working for TLS and mTLS until it expires, but it cannot be renewed with the Client Authentication EKU. Complete the upgrade to X15.5 and the internal PKI migration before it expires.
Q: How do I know if I am using mTLS or standard TLS?
A: Review the Specific Affected Use Cases section.
Q: What can I do now?
A: Cisco recommends these actions:
Q: Is there a security risk in disabling the Client Authentication EKU check on Expressway (X15.5)?
A: No significant change in security posture. Expressway still validates the certificate chain and the CN/SAN of the peer certificate to confirm the connection source. Only the EKU purpose check for the client role is skipped. Public certificates included the Client Authentication EKU by default until the Chrome policy change, so this check added little extra assurance.
Q: I use Let’s Encrypt with ACME on Expressway. What can I do?
A: Let’s Encrypt certificates now contain only the Server Authentication EKU. Upgrade to X15.5 or later. You can then use the ACME-issued certificate as the Expressway-E server certificate. For mTLS where Expressway-E is the client, use an internal CA client certificate or disable the Client Authentication EKU check.
Q: Can I modify the ACME profile to keep getting combined EKU certificates?
A: No. Let’s Encrypt no longer issues certificates with the Client Authentication EKU on any profile. With X15.5 or later, server-only ACME certificates are supported.
Q: Do I need to upgrade both Expressway-E and Expressway-C?
A: Yes. Both must be upgraded to the same version (X15.5 or later).
Q: I am running X15.4. Do I need to upgrade?
A: Yes. X15.4 was an interim release that only partly addressed this issue. X15.5 adds separate server and client certificates and the option to disable the Client Authentication EKU check. Upgrade Expressway-C and Expressway-E to X15.5 or later.
Q: After upgrading to X15.5, can I use Enforcing mode with server-only certificates in my cluster?
A: Yes. Expressway does not verify the Client Authentication EKU for mTLS ClusterDB connections, so TLS Verify can stay Enforcing even when cluster nodes have server-only certificates.
Q: Why can’t I upload my certificate through the Expressway web interface?
A: Releases earlier than X15.5 require the server certificate to contain the Client Authentication EKU. Upgrade to X15.5 or later, which accepts server-only certificates and provides a separate upload for the client certificate.
Q: I cannot register Smart Licensing after certificate renewal. Why?
A: Smart Licensing failure after certificate renewal is usually not related to EKU. Smart Licensing does not require the Client Authentication EKU. Check:
The CSSM server certificate is trusted in the Expressway trust store.
Q: Does MRA require the Client Authentication EKU on Expressway-E?
A: It depends on the Expressway version:
Q: My neighbor zones fail after I uploaded a server-only certificate. Why?
A: When TLS verify mode is On for a neighbor zone, the peer requires the Client Authentication EKU on the certificate that Expressway presents as client. On X15.5 or later, either upload a client certificate issued by your internal CA, or enable the option to ignore the Client Authentication EKU on both Expressway and the peer. Disabling TLS verification on the zone is not recommended.
Q: What certificates are needed for MRA to work properly?
A: For a typical MRA deployment on X15.5 or later:
| Component |
Certificate requirement |
EKU required |
Notes |
| Expressway-E |
Public CA |
serverAuth |
Client EKU check not required for MRA |
| Expressway-C |
Internal CA (recommended) |
serverAuth + clientAuth |
Acts as client in UC Traversal Zone |
| UC Traversal Zone |
One-way validation |
Exp-E: serverAuth; Exp-C: clientAuth |
Expressway-C validates the Expressway-E server certificate |
Q: MRA worked, but after renewing the Expressway-E certificate with server-only EKU, SIP registration fails. What is wrong?
A: On releases earlier than X15.5, MRA SIP signaling requires the Expressway-E certificate to contain both Server and Client Authentication EKUs. Upgrade both Expressway-E and Expressway-C to X15.5 or later. If the previous combined-EKU certificate is still valid, you can reinstall it temporarily until the upgrade is complete.
Q: Where do I get a certificate with the Client Authentication EKU now?
A: From an internal (private) CA. Browser-trusted public roots no longer issue them.
Q: My CA says they can only provide server-only certificates. What can I do?
A: This is expected for certificates from browser-trusted roots. Upgrade to X15.5 or later, and use the public server-only certificate as the Expressway-E server certificate. For Client Authentication certificates, use an internal CA.
Timeline Questions
Q: What changed on June 15, 2026?
A: New subordinate CAs created under Chrome-trusted public roots must be restricted to Server Authentication only. Existing certificates are not revoked, and Chrome does not stop trusting a certificate because it contains both EKUs.
Q: Are there any deadlines left?
A: Yes, two. By March 15, 2027, every public CA in the Chrome Root Store must issue TLS certificates with the Server Authentication EKU only (the major CAs already do). And each combined-EKU certificate still installed on your Expressways stops working for mTLS when it expires. Complete the X15.5 upgrade, the move to internal PKI, and the trust store updates before then.
Q: Do my existing combined-EKU certificates stop working on March 15, 2027?
A: No. Certificates issued before the change stay valid until they expire, even after March 15, 2027. They cannot be renewed with the Client Authentication EKU from a browser-trusted root.
: Support for separate server and client Certificate for Expressway 
The sunsetting of Client Authentication EKU in public CA certificates represent a significant security policy shift that impacts Cisco Expressway deployments using mTLS connections. While this is an industry-wide change, the impact rating is CRITICAL per Field Notice FN74362, and immediate action is required to prevent service disruptions.
| Revision | Publish Date | Comments |
|---|---|---|
2.0 |
13-Nov-2026
|
Updated content in Recommendations section. |
1.0 |
13-Feb-2026
|
Initial Release |