Better Auth v1.8.0-beta.9
This prerelease adds OAuth token-exchange delegation with RFC 8693 actor tokens, expands DPoP support, and corrects sender-constrained token handling. SSO changes allow users to sign in when their OIDC or SAML provider does not send an email, while tightening how SAML NameID is interpreted. The release includes upgrade actions for OAuth provider and custom API users, as well as SAML configurations affected by the updated email mapping behavior.
OAuth provider integrators, clients using DPoP or other sender-constrained tokens, custom OAuth provider API implementations, and SAML/OIDC deployments with providers that omit email may need to adjust configuration or code.
Before upgrading, complete the applicable OAuth schema migration and review the listed DPoP, token-exchange, and SAML email changes for your integrations.
- 01OAuth provider users: run `npx auth@latest migrate` or `npx auth@latest generate` before upgrading to add the optional `act` column on `oauthAccessToken`.
- 02If a SAML IdP sends no email attribute and uses a non-`emailAddress` or unspecified NameID Format, send an `email` attribute or use the `emailAddress` NameID Format, set `samlConfig.mapping.email` to the supplied attribute, or return the NameID from `mapProfileToUser`.
- 03If `clientAuthentication` returns a DPoP key (`jkt`), ensure clients send a DPoP proof with every request to a protected resource.
- 04Update custom `OAuthProviderApi` implementations to provide `verifyDpopProof()` and `issueDpopNonce()`.
- 05For client token exchanges bound by a mechanism other than DPoP, such as mTLS, have `clientAuthentication` return the same `confirmation`.
# community_signal
How useful is this release to your stack?
Sign in with GitHub to cast your vote.
You’ll return to this release, then choose your vote.