Protocols
Saved & recent

Mutual TLS

Also called: mTLS, client certificate authentication

Mutual TLS authenticates the client as well as the server using certificates and proof of possession of their private keys. Each side applies its configured trust and identity checks. This is useful when services need an authenticated machine identity before accepting a request.

For example, an inventory service can require a calling warehouse service to present an accepted client certificate. The certificate identifies the peer; application policy still decides which inventory it may change. Certificates also need issuance, renewal, and revocation handling. Mutual TLS does not automatically grant every authenticated client unrestricted access.

Read first
TLS, Certificate
Related
Authorization, Certificate authority, OAuth 2.0
Further reading
RFC 8705 — OAuth 2.0 Mutual-TLS Client Authentication and Certificate-Bound Access Tokens
client service server service client certificate client identity server certificate server identity client certificate + proof server certificate + proof one mutually authenticated channel private key stays local private key stays local verified client identity authorization check if allowed permission decision follows identity
Mutual TLS requires each peer to present credentials and prove private-key possession. Private keys remain local. After authenticating the client service, the server still applies its authorization policy.

View in the full Protocols collection