Jeremiah Lowin 15dbe7ecf0 Add custom token verifier support to OIDCProxy (#2279) ... * Add custom token verifier support to OIDCProxy OIDCProxy now accepts an optional token_verifier parameter to support non-JWT token formats like opaque tokens from providers such as Clerk. When provided, the custom verifier is used instead of creating a default JWTVerifier. Parameters that only apply to JWTVerifier creation (algorithm, required_scopes) raise clear errors when specified alongside a custom verifier. Parameters with other purposes (audience for OAuth flow, timeout_seconds for config fetch) remain allowed. The custom verifier's required_scopes are automatically loaded and advertised through OAuth discovery endpoints. * Document custom token verifier support in OIDC proxy		2025-10-27 13:38:20 -04:00
..
authentication.mdx	Add storage backend documentation (#2137)	2025-10-19 19:24:13 -04:00
full-oauth-server.mdx	Add storage backend documentation (#2137)	2025-10-19 19:24:13 -04:00
oauth-proxy.mdx	Derive jwt_signing_key from Client Secret, default to Encrypted Disk Store (#2223)	2025-10-24 19:08:58 -04:00
oidc-proxy.mdx	Add custom token verifier support to OIDCProxy (#2279)	2025-10-27 13:38:20 -04:00
remote-oauth.mdx	Add RFC 7662 token introspection provider (#2074)	2025-10-16 10:57:06 -04:00
token-verification.mdx	Add storage backend documentation (#2137)	2025-10-19 19:24:13 -04:00