oauth2-proxy supports only one provider at a time with no multi-provider routing

oauth2-proxy enforces a single upstream IdP per deployment. The alpha-config Providers array is documented as INCOMPLETE in the official docs (2025 comment confirms ongoing breakage). Organizations running multiple IdPs (corporate LDAP + GitHub for contractors + Google Workspace for a subteam) must deploy separate oauth2-proxy instances with no unified session layer. No working third-party tool ships multi-provider routing with shared session management for oauth2-proxy.

Score Breakdown

GitHub

161

Social Proof 1 sources

Support multiple providers / upstreams

nicholasgasior · 11/21/2020

161

Gap Assessment

Wide OpenNo dedicated solution exists

Vendor alpha feature explicitly documented as INCOMPLETE; open since 2020; no third-party routing layer exists that handles provider dispatch + unified session management on top of oauth2-proxy

Virality Score

161

across 0 platforms

Details

Signalissue

Ecosystemdev_tool_cli

Sources1

Platforms0

Updatedunknown

Trend→ stable

Top ideas

All ideas →

0A web app and Figma plugin that binds relative line-height values to type-scale variables and keeps them in sync across a design system 0A web app that pulls ClickUp logged time entries and renders a real capacity and overload view per person 0A web app and API service that computes Jira agile metrics from the issue API and exposes velocity, burndown, and sprint report data via stable developer-facing endpoints

Related signals

All signals →

101oauth2-proxy has no backchannel logout endpoint making SSO sign-out unreliable across browsers