Source note · Local Gateway design and configuration
Webex Calling accepts a Local Gateway certificate carrying only the Server Authentication extended key usage and does not validate or enforce the presence of Client Authentication extended key usage during TLS handshake establishment.
Checked 2026-09-15
Certificates containing only Server Authentication Extended Key Usage (EKU) are supported. Webex Calling doesn’t validate or enforce the presence of Client Authentication EKU during TLS handshake establishment.
- Vendor
- Cisco
- Product
- Webex Calling
- Subsystem
- Local Gateway
- Deployment
- not restricted
- Region
- not restricted
- Release range
- not restricted
- Checked
- 2026-09-15
Sources
- Get started with Local Gateway — Cisco Systems, Inc. (Webex Help Center) · tier 2 current vendor documentation · Table 2 Compare trunking models, CA and certificate requirements row; repeated under Troubleshooting TLS Handshake establishment
Cite this note
APA
WarmTransfer. (2026, September 15). Local Gateway design and configuration: source note wxlgw-client-auth-eku-not-enforced-by-webex. WarmTransfer. https://warmtransfer.net/knowledge/claims/wxlgw-client-auth-eku-not-enforced-by-webex
BibTeX
@misc{warmtransfer-claim-wxlgw-client-auth-eku-not-enforced-by-webex,
title = {Local Gateway design and configuration: source note wxlgw-client-auth-eku-not-enforced-by-webex},
author = {{WarmTransfer}},
year = {2026},
url = {https://warmtransfer.net/knowledge/claims/wxlgw-client-auth-eku-not-enforced-by-webex},
note = {Source note wxlgw-client-auth-eku-not-enforced-by-webex, checked 2026-09-15}
}