OAuth2 Proxy — screenshot of oauth2-proxy.github.io

OAuth2 Proxy

I use OAuth2 Proxy as a reverse proxy to secure internal services, authenticating users via common providers like Google or GitHub to restrict access by email, domain, or group.

Visit oauth2-proxy.github.io →

Questions & Answers

What is OAuth2 Proxy?
OAuth2 Proxy is a reverse proxy and static file server designed to provide authentication for web applications and internal services. It validates user accounts using various identity providers like Google or GitHub.
Who should use OAuth2 Proxy?
It is ideal for organizations or individuals who need to secure their intranet or internal web applications, requiring users to authenticate through existing identity providers without implementing full authentication logic in each application.
How does OAuth2 Proxy compare to other authentication solutions?
OAuth2 Proxy focuses specifically on externalizing authentication to a reverse proxy layer, integrating with popular OAuth2 providers. This simplifies application development by offloading authentication concerns, rather than acting as a full-fledged identity provider itself.
When is OAuth2 Proxy a good choice for securing applications?
It is a good choice when you want to put a consistent authentication layer in front of multiple applications or static sites, especially when leveraging common OAuth2 identity providers for user validation.
What kind of authentication providers does OAuth2 Proxy support?
OAuth2 Proxy supports a variety of common identity providers, including Google, GitHub, and others. It can validate accounts based on email, domain, or group affiliations provided by these services.