Engine API and TURN credentials with mTLS


Devices using a client certificate can now access the Engine HTTP API and request short-lived TURN credentials without a separate token or application secret.

The Go and Node SDKs discover the dedicated mTLS API automatically and cache its address for the lifetime of the client. Existing device setup flows remain unchanged, and ordinary browser connections do not trigger a certificate prompt.

Certificate credentials expose Engine and TURN permissions in the dashboard. Existing certificates retain their previous rights; TURN issuance must be granted explicitly. The Control plane remains token or session authenticated.

With the appropriate Engine permissions, certificate contexts also support CLI inventory, watch, and ui. doctor understands mTLS API access, and Go supports HTTP/3 over QUIC alongside HTTPS over TCP.

See mTLS, STUN and TURN, and the CLI command reference for configuration and permissions.