OAuth2, token introspection and JWE authentication, scope rules, and a stricter rate limit caller identification.
Breaking
New authentication
OAuth2mode validates tokens against the identity provider's JWKS, with discovery and optional encrypted access tokensOAuth2Introspectionmode validates opaque tokens through the identity provider's introspection endpointJWEmode reads encrypted tokens from a header, with an optional signed JWT inside (NestedSigningMethod)RequiredScopesonGlobalConfig, servers and routes, so one auth method can be defined once and reused with different scopesBearerandRawHeaderacceptRS384,RS512,PS256,PS384,PS512,ES384andES512
Rate limit
BurstValuecontrols how many requests a caller can send at once- New
IfMissingUseIPflag on client id rules: the IP fallback is applied only when you ask for it - A request whose client id can't be collected is refused with
401and a missing identification value error, in all modes
Operations
nocleye checkreports every new OAuth2, scope, JWE and introspection rule, an invalid burst value, and a rate limit without a way to identify the callersnocleye checkopens the JWKS URL of every OAuth2 auth method and reports it if it is unreachable or has no usable keys. Use--offlineto skip it- New Prometheus metrics
gw_jwks_fetch_total,gw_jwks_unknown_kid_refetch_total,gw_jwks_keys_age_secondsandgw_introspection_total
Fixes
- Fix rate limit burst control
- Fix
CascadeandStrictrate limit modes, which now enforce id availability - The config parser rejects misconfigured rate limit rules, and client id rules without at least one mode
- Fix reading the
customandapiKeyquery string steps - Fix the CLI message and list of available signing methods, and remove misleading auth option texts
