TiloBox
Back to directory
OAuth2 Proxy project preview

OAuth2 Proxy

Reverse proxy providing authentication with OpenID Connect and major OAuth providers.

LicenseMIT
GitHub stars8.5k
Last commit1 weeks ago
Tags5 topics
Oidc AuthenticationGolang SecurityOauth2 ProxyReverse Proxy SsoSecurity
Overview

Why consider OAuth2 Proxy?

OAuth2 Proxy is an open-source reverse proxy written in Go. It intercepts inbound web traffic and authenticates users against Identity Providers (Google, GitHub, Keycloak, Azure AD, Okta) before passing authenticated HTTP headers to backend microservices.

Guided learning

Learn OAuth2 Proxy by building

Practical setup notes, real use cases, and copy-ready examples in one focused guide.

1 min read 2 sections
In this guide2 sections

Overview of OAuth2 Proxy

OAuth2 Proxy adds OAuth2 and OpenID Connect protection in front of internal web apps without code changes.

Docker Quickstart

bash
1docker run -p 4180:4180 quay.io/oauth2-proxy/oauth2-proxy:latest --provider=github --client-id=... --client-secret=...

OAuth2 Proxy is licensed under the permissive MIT License.

Related tools

More options with a similar category or technology profile.

OAuth2 Proxy FAQs

OAuth2 Proxy is listed as a Security tool on TiloBox. Review the overview, features, and official documentation on this page to decide whether it solves your specific workflow.

Start with the project's GitHub repository and official website for supported installation and deployment instructions. Test the setup with representative data or a small project before rolling it out more widely.

OAuth2 Proxy is listed under the MIT license. Read the complete license text and the project's notices before using, modifying, or distributing the software.

Production readiness depends on your requirements. Review maintenance activity, security practices, documentation, backup and upgrade procedures, and compatibility with your stack; then validate it in a non-production environment.

OAuth2 Proxy is listed as an alternative to Cloudflare Access. Compare the core workflow, deployment model, integrations, and licensing against your must-have requirements before switching.