vouch/vouch-proxy

an SSO and OAuth / OIDC login solution for Nginx using the auth_request module

View on GitHub ↗Jump to charts ↓Open shareable report →

Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 1 hour ago
Added to GitGenius on September 21st, 2026
Created on July 21st, 2017
Open Issues & Pull Requests: 65 (+0)
GitHub issues: Enabled
Number of forks: 337
Total Stargazers: 3,281 (+0)
Total Subscribers: 35 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 14.7 hours
Mean response time: 35.3 days
90th percentile: 70.1 days
Tracked items: 35

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 15
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 1,265 days
Stale 30+ days: 15
Stale 90+ days: 14

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

  • help wanted (11)
  • enhancement (10)
  • question (8)
  • documentation (3)
  • bug (2)
  • Mend: dependency security vulnerability (1)

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Vouch Proxy is an authentication gateway that integrates single sign-on and OAuth/OIDC login flows with Nginx using the auth_request module.

The tool solves the problem of adding centralized authentication to Nginx-proxied applications without modifying each application's code. It works by intercepting requests at the Nginx level through the auth_request module, validating user credentials against configured OAuth or OIDC providers, and allowing or denying access based on authentication state. Users log in once through the configured identity provider and receive a session token that Vouch Proxy validates on subsequent requests, enabling seamless single sign-on across multiple backend services.

Vouch Proxy suits organizations running Nginx as a reverse proxy that need to add authentication without rewriting their applications. It works well for protecting multiple services behind a single Nginx instance, where a centralized login point reduces friction for users. The tool is particularly valuable when you want to leverage existing OAuth or OIDC providers rather than managing credentials directly. Teams should evaluate whether their Nginx setup supports the auth_request module and whether their identity provider is compatible with the tool's OAuth/OIDC implementation.

The project shows consistent maintenance with regular commits addressing issues and improvements. Pull requests receive timely review and feedback from maintainers. The codebase demonstrates active refinement of core authentication logic and configuration handling. Issue discussions indicate the maintainers engage substantively with user problems and feature requests rather than closing conversations prematurely.