Skip to content

Release v2.59.0

Choose a tag to compare

@github-actions github-actions released this 10 Nov 10:51
158355f

Summary

Bearer routes can now accept DPoP-bound OAuth access tokens (RFC 9449). When enabled on a route, AuthProxy verifies the DPoP proof before any authorization work and refuses everything it cannot verify. Routes that do not enable DPoP behave as before.

Added

  • Opt-in DPoP proof verification on OAuth bearer routes: DPoP authorization scheme, ES256 proofs only, htm, htu (from the configured public origin only), iat window, ath access-token binding and cnf.jkt key binding, with WWW-Authenticate challenges (part of #258).
  • A shared Redis replay store so a proof jti cannot be reused on another replica, with fail-closed handling when the store is unavailable, its clock is off or it was just provisioned (part of #258).
  • Optional server-issued DPoP nonces, bound to the key and origin (part of #258).
  • DPoP configuration documentation covering the public origin, the replay store and deployment requirements (part of #258).

Changed

  • A DPoP-bound token sent as a plain Bearer credential, a DPoP proof on a token that is not bound, and DPoP proofs combined with cookies or other credentials are refused with invalid_token.
  • Introspection answers must carry a cnf that matches the access token's own binding on DPoP routes.
  • The verified sender binding is carried into the forwarded identity.