Mutual TLS (mTLS)
What is Mutual TLS (mTLS)?
Mutual TLS (mTLS) is a TLS handshake where the server also requests and verifies a certificate from the client, authenticating both sides instead of only the server a normal HTTPS connection authenticates. AdminKit's guide to securing an MQTT broker covers when issuing a certificate per device is worth the operational cost over username and password alone.
By AdminKit team, Netbase JSC · Updated
Mutual TLS (mTLS) extends an ordinary TLS handshake, where only the server proves its identity with a certificate, so the server also requests and verifies a certificate from the client — Cloudflare’s explanation of mTLS frames the same distinction as “in mTLS, both the client and server have a certificate, and both sides authenticate using their public/private key pair.” RFC 8446 (its IETF Datatracker entry lists it as a Proposed Standard obsoleting RFC 5246, the earlier TLS 1.2 specification)‘s CertificateRequest message (Section 4.3.2) is the mechanism: if the server sends one, the client must respond with its own X.509 certificate and prove it holds the matching private key before the TLS handshake completes. In a web server this is usually a single setting: nginx’s ssl_verify_client directive enables verification of client certificates, and its optional mode requests a client certificate but verifies it only if one is presented. This authenticates the connection itself, which is why mTLS shows up as a building block well beyond plain HTTPS — RFC 8705 defines an OAuth client authentication method built entirely on it, binding an access token to the certificate that requested it instead of a shared secret. The tradeoff is operational: every client needs a certificate issued, distributed, and rotated before expiry, more overhead than a password, but it ties access to a private key a device holds rather than a credential that can be copied or guessed, the same reasoning zero trust architectures lean on for service-to-service authentication.
Mutual TLS (mTLS) is part of AdminKit’s machine protocols cluster; the full AdminKit glossary lists other related terms.
Frequently asked questions
What does mTLS authenticate that ordinary TLS doesn't?
Ordinary TLS only proves the server's identity; mTLS also has the server request and verify a certificate from the client, authenticating both sides of the connection.
What message in the TLS handshake triggers mutual authentication?
RFC 8446's CertificateRequest message (Section 4.3.2) -- if the server sends one, the client must respond with its own certificate and prove it holds the matching private key.
Is mTLS used outside of plain HTTPS connections?
Yes -- RFC 8705 defines an OAuth client authentication method built entirely on mTLS, binding an access token to the certificate that requested it instead of a shared secret.
What's the main operational cost of adopting mTLS?
Every client needs a certificate issued, distributed and rotated before expiry -- more overhead than a password, though it ties access to a private key rather than a copyable credential.