v0.2.3
Patch Changes
-
#117
b2c5877Thanks @DeanMauro! - AddgetOAuthApihelper function to access OAuthHelpers outside of thefetchmethod. This enables OAuth functionality in worker RPC methods and other entry points. -
#109
9f118f3Thanks @bokhi! - fix: path-aware audience validation for RFC 8707 resource indicators. Include request pathname inresourceServercomputation for both internal and external token validation. Replace strict equality inaudienceMatches()with origin + path-prefix matching on path boundaries. Origin-only audiences (e.g.https://example.com) still match any path (backward compatible). Path-aware audiences (e.g.https://example.com/api) match the exact path and sub-paths (/api/users) but not partial matches (/api-v2). -
#120
155c410Thanks @DeanMauro! - Add OAuth 2.0 Token Exchange (RFC 8693) support. Clients can exchange an existing access token for a new one with narrowed scopes, a different audience, or a shorter TTL — without requiring the user to re-authorize. Gated behind theallowTokenExchangeGrantoption (defaultfalse). Also adds scope downscoping (RFC 6749 Section 3.3) to authorization code and refresh token flows.