10 OAuth Providers, Real Endpoint URLs, Zero Markup
Every OAuth provider Aeion Auth can route to today. Configure once via env-vars; switch on per-deployment without code changes. Connect Okta / Auth0 / Ping / OneLogin / JumpCloud / any OIDC-compatible IdP through the generic `oidc` provider — no per-IdP code paths.
Provider List
Every provider Aeion Auth supports out of the box, with its default scopes and PKCE support.
Real Endpoint URLs
Aeion's OAuth router uses these real published endpoints. Nothing proxied through Aeion infrastructure — the user's browser talks directly to the provider's authorization endpoint, the token exchange happens server-to-server from your Aeion deployment to the provider.
Per-Provider Configuration
Each provider needs three env-var pairs to come online. The generic OIDC provider needs four extra (the endpoint URLs).
Per-Provider Notes & Gotchas
Provider quirks worth knowing before you wire one up.
Adding a Custom OIDC Provider (the Federation Path)
Many enterprise customers want to federate from their existing IdP (Okta is the most common — they use Okta for their workforce, want Aeion to delegate authentication there). The generic OIDC provider handles this without a code change.