Glossary

Mutual TLS (mTLS)

Ordinary TLS proves the server to the client. Mutual TLS proves the client to the server as well, using a certificate instead of a password or API key.

General definition

Mutual TLS (mTLS) extends the standard TLS handshake with client authentication. After the server sends its certificate it issues a CertificateRequest; the client responds with its own certificate and a signature over the handshake (CertificateVerify) proving it holds the matching private key, and the server validates the chain against the certificate authorities it trusts. TLS 1.3 (RFC 8446) encrypts this exchange, so the client identity is not visible on the wire. The result is an authenticated channel in both directions, with the identity bound to the connection itself rather than to a token carried inside it.

Where it is used:

  • Service-to-service authentication inside a platform: service meshes such as Istio and Linkerd issue a short-lived certificate to every workload (often as SPIFFE identities) and enforce mTLS on all internal traffic, so a stolen network position yields nothing
  • Zero-trust networks (NIST SP 800-207), where no request is trusted because of the network it came from; the workload certificate is the identity
  • Webhook and API hardening: a receiver demands a client certificate so only the real sender can call the endpoint, and a sender verifies the receiver so it never posts data to an impostor
  • Device and partner access: IoT devices, payment terminals and B2B integrations where each party is issued a certificate and revocation is managed centrally
  • OAuth client authentication: RFC 8705 binds access tokens to the client certificate, so a leaked token is useless without the key

The cost is a private PKI: issuing, distributing, rotating and revoking client certificates for every caller. That is cheap for machines managed by automation and expensive for humans, which is why mTLS rarely replaces user login and usually sits in front of administrative and internal interfaces alongside an API gateway or reverse proxy that terminates it. It is a complement to encryption in transit: the channel was already encrypted, and mTLS adds a verified answer to the question of who is on the other end. It works with network isolation such as a virtual private cloud rather than instead of it.

In the Ethora ecosystem

A self-hosted or dedicated Ethora deployment is a set of services, the Node.js API, the ejabberd XMPP server, MongoDB, object storage and the WebRTC media server, running behind a reverse proxy inside your own cloud account or data centre. Because you own that proxy, you can enforce mutual TLS on the interfaces that only machines should reach: the admin API that your backend calls with its app-level API token, and the webhook and message-bus endpoints to which Trust and Safety reports and events are delivered. This is an architecture choice made at the proxy and network layer rather than a switch inside Ethora, and it layers on the platform’s existing TLS, short-lived JWT chat tokens and access controls.

End-user clients, browsers and mobile apps, keep using ordinary TLS with server authentication plus their chat tokens; issuing personal certificates to every end user is rarely practical. Where the deployment uses API-provisioned end users, the single server-to-server path between your backend and the Ethora API is the natural place for mTLS, since it is one machine identity, automated and auditable.

Get started

Chat and AI built for regulated industries

Ethora gives you audit trails, retention controls, a Trust & Safety layer and dedicated deployments in your own cloud. Talk to our team.

Start Free
Free tier available Enterprise SLA No vendor lock-in