Terminate TLS however (and wherever) you want with Traffic Policy

Ngrok offers a simplified setup for mutual TLS (mTLS) through its terminate-tls Traffic Policy action, allowing users to control where and how TLS traffic is decrypted and client certificates are validated. This innovation centralizes TLS requirements into a single configuration engine, previously managed through a combination of agent configurations and edge modules. By default, ngrok handles TLS termination differently based on endpoint types, with the option to terminate at ngrok's cloud service, at the user's agent for end-to-end encryption, or at the upstream service. The system supports both the latest secure version of TLS, 1.3, and provides fallback for TLS 1.2, ensuring broader client compatibility and reduced latency. Users can also customize their setup with their own certificates, enhancing flexibility and security. Furthermore, ngrok simplifies mTLS setup, allowing users to enforce client certificate validation with minimal configuration and offering comprehensive documentation and support to guide users through the process.

No tracked trend matches for this post yet.

Use this post, company, and trend context to find content marketing opportunities, perform competitive analysis, or address product feature gaps via the Plushcap MCP server or the Plushcap API.