Adding auth to applications seems easy at the surface, but it can quickly become a source of frustration once you need to deliver a production-grade solution with features for end-users — i.e. self-service sign-ups, account recovery, and social auth for multiple platforms — and for security — i.e. audit trail, live session management, and authorization policies. In this post, I'll integrate ngrok to Auth0 and solve for these challenges.
The last month has been busy at ngrok! We’re tremendously proud to announce we’ve raised $50M in funding to grow ngrok’s API-first ingress as a service platform for developers. We’ve also focused on improving security with Dashboard SSO and Identity-Aware Ingress, developer experience with new documentation, and contribute to the community with webhook security and an open source firewall toolset for go
Webhooks are the foundation of modern API development. They enable us to react to changes in our systems, an incoming text message, a successful payment, or that latest pull request no matter our stack. While webhooks are universal in concept, they are unstandardized API contracts with few organizations paying attention to their design, security controls, and overall operational experience.
This month, we focused in two areas you asked for (a lot) and filled in some other bits and bytes to give you a hand: productivity features to launch your tunnels quickly with style and security features so you use ngrok in your org with IT and security approval.
Learn how to use ngrok Cloud Edge middleware to address app requirements – such as observability, load balancing, compression, and security – fast and without the burden of running and maintaining a middleware infrastructure.
ngrok Secure Tunnels provides a simple to enable remote access to systems. With one command— i.e. `ngrok http 80` — you can share your apps, APIs, and systems with the world, without complex network configuration, reliability issues, and NAT. However, with power comes great responsibility so let's add OAuth 2.0