Better Auth Updates & Release Notes
166 updates curated from 1 source by the Releasebot Team. Last updated: Nov 20, 2026
- Nov 20, 2026
- Date parsed from source:Nov 20, 2026
- First seen by Releasebot:Nov 20, 2026
v1.7.27
Better Auth ships OAuth and OIDC improvements, including configurable cross-origin JWKS support, resilient key and metadata caching, and new provider options. The release also fixes token signing, request validation, session handling, and connection issues across core and plugins.
Important Action required If you have no key for jwks.keyPairConfig.alg and your newest key uses another jwks.keyPairConfigs algorithm, your ID tokens, /token JWTs, and cookie-cache JWTs change alg and kid on the next unpinned signature, so update verifiers that hard-code the old algorithm or never refetch the JWKS for an unknown kid. (#12655) If you want to keep rejecting a client_uri on a different origin than the client_id, add "client_uri" to originBoundFields, which now defaults to ["post_logout_redirect_uris"]. (#12822) better-auth Bug Fixes Fixed the phone number plugin returning a 500 instead of a 400 from /update-user when the request has no body (#12810) Fixed the username plugin returning a 500 on /sign-up/email and /update-user when the request has no body; it now returns the same 400 as without the plugin (#12810) Fixed /sign-in/anonymous to validate the request origin, returning a 403 for browser requests from origins outside trustedOrigins (#12809) Fixed unpinned tokens such as ID tokens and session JWTs to prefer a key for the primary jwks.keyPairConfig.alg algorithm (#12655) Fixed getTestInstance from better-auth/test to run every instance cleanup even when one fails, so databases and connections are not left open (#12553) Fixed POST requests without a body, such as /sign-out or /revoke-sessions, failing with a 415 on Deno, Next.js, Nuxt and other servers that pass an empty body stream (#12805) For detailed changes, see CHANGELOG @better-auth/oauth-provider Features Added the isCrossOriginJwksUriAllowed option to cimd() so you can accept Client ID Metadata Document clients whose jwks_uri is on a different origin than their client_id (#12823) Fixed administrator updates to discovered clients that publish keys at a jwks_uri, such as setting client_credentials_scopes through adminUpdateOAuthClient (#12823) Added the jwksStaleIfError option to keep verifying client assertions with cached jwks_uri keys while refetching fails transiently (#12824) Added the requireOpenId option to oauthProvider to reject /oauth2/authorize requests that lack the openid scope with invalid_scope (#12729) Added the resourceSeedScope option to oauthProvider so apps that build Better Auth on every request can stop re-reading oauthResource each time (#12733) Added advertisedMetadata.token_endpoint_auth_methods_supported so providers can advertise accepted token endpoint client authentication methods, including public clients (#12732) Bug Fixes Fixed Client ID Metadata Document and jwks_uri responses refused before their body is read, such as error statuses or non-JSON content types, holding connections open (#12819) Fixed the signed OAuth query failing with invalid_signature when a proxy, router, or login page URL-decodes it once (#12728) Fixed the end-session endpoint to accept issued ID token hints when the issuer ends with a trailing slash (#12713) Fixed signing keys and post-logout redirect URIs removed from a client's metadata document continuing to work after a refresh (#12821) Fixed concurrent first requests from the same Client ID Metadata Document client failing with a server error when the database wraps the unique-constraint error (#12820) Fixed refresh tokens without offline_access to stop working once their session expires or is deleted (#12812) Fixed a client losing its offline_access grants on other devices after using a session-bound refresh token following sign-out (#12812) Fixed oauthProviderClient to send form-encoded bodies as form fields and leave non-object JSON bodies such as arrays unchanged (#12726) Fixed oauthProviderClient to stop rewriting request bodies on pages whose query string is not a signed OAuth query (#12726) Fixed back-channel logout, jwks_uri client authentication, and Client ID Metadata Document fetches failing on Cloudflare Workers (#12817) Fixed OIDC SSO sign-in with signIn.sso to resume the OAuth authorization instead of leaving the user on the sign-in callbackURL (#12727) Fixed private_key_jwt clients losing their cached jwks_uri key set while still authenticating when more than 500 key sets are cached (#12721) Improved private_key_jwt authentication so concurrent assertions for the same jwks_uri share a single fetch of the client's key set (#12721) Fixed /oauth2/introspect to return the client ID as sub for JWT client_credentials tokens issued to pairwise clients (#12671) For detailed changes, see CHANGELOG @better-auth/cimd Features Added the isCrossOriginJwksUriAllowed option to cimd() so you can accept Client ID Metadata Document clients whose jwks_uri is on a different origin than their client_id (#12823) Added the opt-in metadataStaleIfError option to keep known clients working through brief metadata host outages (#12824) Bug Fixes Fixed Client ID Metadata Document and jwks_uri responses refused before their body is read, such as error statuses or non-JSON content types, holding connections open (#12819) Fixed @better-auth/cimd/node keeping connections open after bodyless responses such as 304 Not Modified to a metadata revalidation (#12819) Fixed client metadata and JWKS fetches through @better-auth/cimd/node hanging forever when the server answers with 101 Switching Protocols (#12819) Fixed requests hanging forever when they join a Client ID Metadata Document fetch that never settles (#12731) Fixed concurrent requests for the same Client ID Metadata Document sharing one request's database save instead of each saving the client in their own context (#12731) Fixed Client ID Metadata Document fetches that never settle permanently using up fetch slots and making other clients fail with temporarily_unavailable (#12731) Fixed Client ID Metadata Documents with a client_uri on a different origin than the client_id being rejected under the default options (#12822) Fixed client metadata and JWKS fetches in @better-auth/cimd/node staying stuck on DNS lookups after the request is aborted (#12818) Fixed back-channel logout, jwks_uri client authentication, and Client ID Metadata Document fetches failing on Cloudflare Workers (#12817) For detailed changes, see CHANGELOG @better-auth/core Bug Fixes Fixed valid access tokens being rejected when the JWKS refetch fails by falling back to a cached key set fetched less than 10 minutes ago (#12722) Fixed overlapping requests reading each other's request state in the edge and browser build by using the runtime's AsyncLocalStorage when available (#12807) For detailed changes, see CHANGELOG Contributors Thanks to everyone who contributed to this release: @bytaesu, @deepanshupal, @devsouhardo, @EhsanulHaqueSiam, @ghazy2001, @gustavovalverde, @hardikguptaofficialgit, @kaiizer777, @Neekoras, @NoiceHax, @officialasishkumar, @rendermani Full changelog: v1.7.26...v1.7.27
Original source - Nov 19, 2026
- Date parsed from source:Nov 19, 2026
- First seen by Releasebot:Nov 19, 2026
v1.6.35
Better Auth fixes refresh-token rotation so adapters that reject account IDs in update data can store rotated tokens.
better-auth Bug Fixes Fixed refreshToken failing to store rotated tokens with adapters that reject the account id in update data, such as Convex (#12063) For detailed changes, see CHANGELOG Contributors Thanks to everyone who contributed to this release: @jainamm-gala Full changelog: v1.6.34...v1.6.35
Original source All of your release notes in one feed
Join Releasebot and get updates from Better Auth and hundreds of other software products.
- Nov 18, 2026
- Date parsed from source:Nov 18, 2026
- First seen by Releasebot:Nov 19, 2026
v1.7.26
Better Auth releases updates across authentication, OAuth, and SCIM, adding social-provider account fields, Kakao ID-token sign-in, clock-tolerant client assertions, and paginated SCIM events. It also tightens token verification and fixes security, networking, and sign-in edge cases.
Important Action required If you use a custom JWT plugin adapter.getJwks and reads are expensive, add caching inside your key store, since it is now called on every verification. (#12624) better-auth Features Added a getAccountFields option to social providers for storing custom values on the provider account at sign-in (#12734) Bug Fixes Fixed expired verification values being returned to repeated lookups by deleting them when found (#12626) Fixed two-factor sign-in to reject an expired challenge before sending an OTP or counting a failed attempt (#12626) For detailed changes, see CHANGELOG @better-auth/core Features Added a getAccountFields option to social providers for storing custom values on the provider account at sign-in (#12734) Added ID token sign-in for Kakao, so ID tokens from Kakao's native SDKs can be passed to signIn.social (#12316) Bug Fixes Fixed DPoP proof replay reservations to last through the full accepted window, so a proof can no longer be reused in its final second (#12625) Fixed authorization URLs to keep empty segments in the authorization endpoint's query, such as a trailing or doubled & (#12620) Fixed the host classifier treating non-global IPv6 addresses outside 2000::/3 as public, so they are now rejected as reserved (#12692) Fixed outbound checks rejecting NAT64 addresses that embed a public IPv4 address, which broke SSO discovery and CIMD fetches on DNS64 networks (#12692) Fixed IPv6 addresses with a dotted IPv4 tail being misread as IPv4-mapped, so they are now rejected as reserved (#12692) Fixed Kakao sign-in to use PKCE by sending code_challenge and code_verifier (#12315) For detailed changes, see CHANGELOG @better-auth/oauth-provider Features Added an assertionClockTolerance option so private_key_jwt clients with slight clock drift no longer fail token exchange (#12720) Bug Fixes Added a WWW-Authenticate: Basic challenge to OAuth provider 401 invalid_client responses for introspection and revocation requests without client credentials and for private_key_jwt assertions with invalid signatures (#12622) Fixed the OAuth provider and requireMcpAuth to call a custom JWT plugin adapter.getJwks on every verification instead of caching its keys (#12624) Fixed a custom JWT plugin adapter.getJwks to receive the request again when the OAuth provider reads signing keys and when requireMcpAuth verifies a token (#12624) Fixed revoking another client's already revoked refresh token deleting the presenting client's own tokens (#12724) Fixed /userinfo returning a 500 error when the profile scope is requested for a user with no name (#11201) Fixed refreshed access and ID tokens carrying a sid for a session that has already ended (#12723) Fixed OAuth token introspection and revocation returning a 500 error when a custom refresh token decrypt rejects an unrecognized value (#12725) For detailed changes, see CHANGELOG @better-auth/cimd Bug Fixes Fixed client ID metadata fetches failing for client_id URLs whose host is a public IPv6 literal (#12694) Fixed CIMD metadata fetches on Node failing when the first DNS answer is unreachable, such as hosts without outbound IPv6 (#12730) For detailed changes, see CHANGELOG @better-auth/mcp Bug Fixes Fixed the OAuth provider and requireMcpAuth to call a custom JWT plugin adapter.getJwks on every verification instead of caching its keys (#12624) Fixed a custom JWT plugin adapter.getJwks to receive the request again when the OAuth provider reads signing keys and when requireMcpAuth verifies a token (#12624) For detailed changes, see CHANGELOG @better-auth/scim Features Added pagination to listSCIMManagedConnectionEvents with optional limit, offset, and sortDirection fields and a total count in the response (#10793) For detailed changes, see CHANGELOG Contributors Thanks to everyone who contributed to this release: @afn, @bytaesu, @claude, @gustavovalverde, @honuuk, @jonathansamines, @luchersou, @MagsMagnoli, @onmax, @pardeep-fs, @SibteProf, @umeraamir69, @wfcastaneda Full changelog: v1.7.25...v1.7.26
Original source - Nov 15, 2026
- Date parsed from source:Nov 15, 2026
- First seen by Releasebot:Nov 16, 2026
- Modified by Releasebot:Nov 16, 2026
v1.8.0-beta.10
Better Auth ships a major OAuth update with pushed authorization requests, broader DPoP support, JWT access-token revocation, pairwise subjects, and improved token verification. The release also includes breaking changes and migration steps for OAuth provider users.
Important
Action required
- If you use a read replica for your verification store, make sure it reads its own writes, because every setup now writes a verification row per revoked grant and a lagging replica can let in-flight requests keep their tokens. (#12581)
- If you want requireMcpAuth to keep verifying JWT signatures alone instead of checking the provider's records, set jwksUrl. (#12597)
- If you have a grant extension that passes act to issueTokens, set sub_profile: "service" on client actors, or pairwise clients will see those client IDs as pairwise values. (#12584)
- If you have a may_act that names a service by sub, add sub_profile: "service" so it keeps its client ID. (#12584)
- If you return undefined from customAccessTokenClaims or other claim sources to remove a claim set elsewhere, return a value such as null instead, because the lower-priority value now stays. (#12575)
- If you have a custom clientAuthentication strategy that compares aud with expectedAudience, move it to acceptedAudiences and pass that to consumeClientAssertion. (#12599)
- If you have clients that sign client assertions for an endpoint URL, update them to use the issuer as aud, or set assertionAudience: "issuer-or-endpoint" temporarily to keep accepting them. (#12599)
- If your authorization server accepts only its token endpoint URL as the assertion audience, set audience: "token_endpoint". (#12599)
- If you sign in to a Better Auth 1.8 authorization server with private_key_jwt, set oidcConfig.clientAssertionAudience: "issuer". (#12599)
- If you send UserInfo requests with an Authorization header that has no Bearer or DPoP scheme, send the token as Authorization: Bearer <token>. If you handle the old 400 invalid_scope response, handle 403 insufficient_scope instead. (#12605)
- If your provider publishes discovery at a non-well-known path or under another name for the same issuer, set issuer to the issuer identifier the provider documents. If its discovery document has no issuer, configure authorizationUrl, tokenUrl, and userInfoUrl instead of discoveryUrl. (#12585)
- If you set ba_sub in customAccessTokenClaims, an extension, or a resource's customClaims, rename your claim. (#12577)
- If you call requireActiveAccessToken and then enforceDpopBinding on an endpoint, replace both calls with provider.verifyResourceRequest(), which checks the DPoP proof. (#12606)
- If you pass authorization_details_types_supported to getProtectedResourceMetadata, wrap the value in an array. (#12513)
- If you match body.error === "invalid_token" to catch a missing or unsupported Authorization scheme, check for a 401 without body.error instead. (#12512)
- If you have exhaustive checks over DpopBindingErrorCode or DpopProofErrorCode, add a case for use_dpop_nonce so the code typechecks. (#12511)
- If you use CIBA, run npx auth@latest migrate, or npx auth@latest generate and apply the schema with your ORM, before you upgrade to add the acrValues and authorizationDetails columns to the cibaRequest model. (#12509)
- If you use the OAuth provider, add the requirePushedAuthorizationRequests column to the oauthClient table before deploying, even with PAR disabled, because requests fail until it exists: run npx auth@latest migrate with the built-in Kysely adapter, or npx auth@latest generate and apply the schema with your ORM. (#12518)
- If you use the OAuth provider, run npx auth@latest migrate before upgrading, or run npx auth@latest generate and apply the schema with your ORM's migration tool, to add the accessTokenClaims column to oauthAccessToken. (#12508)
- If you use oauthProvider(), before deploying run npx auth@latest migrate with the built-in Kysely adapter, or run npx auth@latest generate and apply the schema with your ORM, to add the grantId columns to oauthRefreshToken and oauthAccessToken. (#12520)
- If you have a custom OAuthProviderApi implementation, add the challengeDpopNonce() method. (#12522)
better-auth
❗ Breaking Changes
- Changed createPrivateKeyJwtClientAssertionGetter to sign client assertions for the authorization server's issuer by default when the issuer is known (#12599)
- Changed Generic OAuth to check the discovery document's issuer against discoveryUrl, skipping providers whose issuer does not match (#12585)
Features
- Added createDpopFetch in better-auth/oauth2/dpop-client for sending DPoP-bound requests with per-origin nonce handling and a single retry on use_dpop_nonce (#12506)
- Added endpointType to custom token endpoint authentication hooks, and issuer to hooks and client assertion getters when Better Auth knows it (#12580)
- Added a dpop: { keyPair } option so Generic OAuth providers can request DPoP-bound tokens (RFC 9449) (#12596)
- Added support for pushed authorization requests (RFC 9126) in Generic OAuth sign-in through the new pushedAuthorizationRequest option (#12519)
Bug Fixes
- Added deriveEncryptionKey(secret, purpose) to better-auth/crypto so plugins can derive a separate encryption key for each value they encrypt (#12577)
For detailed changes, see CHANGELOG
@better-auth/oauth-provider
❗ Breaking Changes
- Deprecated the expectedAudience strategy input and parameter in favor of acceptedAudiences for clientAuthentication strategies and consumeClientAssertion (#12599)
- Changed client assertions such as private_key_jwt to require the provider's issuer as their only aud value, rejecting endpoint URLs with invalid_client (#12599)
- Changed access-token claims set to undefined to be left out instead of removing a same-named claim from a lower-priority source (#12575)
- Changed UserInfo to return 403 insufficient_scope for access tokens without the openid scope and to reject Authorization headers without a Bearer or DPoP scheme (#12605)
- Changed requireActiveAccessToken to refuse DPoP-bound access tokens with a 401 invalid_token and a DPoP challenge instead of accepting them without checking a proof (#12606)
Features
- Changed token exchange to reject a subject token that carries authorization_details with invalid_request (#12509)
- Added opt-in token exchange for DPoP-bound public clients through oauthTokenExchange({ publicClients: "dpop-bound" }) (#12517)
- Added a pushed authorization request endpoint (POST /oauth2/par, RFC 9126) to the OAuth provider, with optional global or per-client enforcement (#12518)
- Added a clientId option to provider.authenticateClient() so plugin endpoints can authenticate follow-up requests that omit client_id (#12529)
- Added an expectedJkt option to provider.verifyDpopProof() so plugin endpoints can require a later request to use the same DPoP key as an earlier one (#12529)
- feat(oauth-provider): bring DPoP challenges in line with Bearer (#12579)
- Added the ability for adminUpdateOAuthClient to grant or revoke RP-initiated logout on any client, including ownerless ones, by sending only enable_end_session (#12588)
- Fixed updateOAuthClient to reject new post_logout_redirect_uris entries on another origin than the client's redirect_uris, for clients that may use RP-initiated logout (#12588)
- Changed OAuth provider discovery to publish combined, de-duplicated lists when multiple extensions advertise the same list, such as authorization_details_types_supported (#12564)
- Added issueAuthorizationCode to the OAuth provider API so plugin endpoints can issue authorization codes for a signed-in user without a redirect (#12565)
- Changed /oauth2/authorize and /oauth2/par to reject requests with authorization_details using invalid_authorization_details when discovery advertises supported types (#12591)
- Added support for extension grants to issue RFC 9396 authorization_details through issueTokens in token responses, JWT access tokens, and introspection (#12591)
- Added challengeDpopNonce() so plugin endpoints and before hooks can issue a nonce-only DPoP challenge before staging state (#12522)
- Improved OAuth provider extension conflict errors and warnings to name the extensions involved, with an optional name for extensions (#12646)
- Added opt-in revocation of JWT access tokens at /oauth2/revoke with revocableJwtAccessTokens: true (#12507)
- Added resolveSubject({ userId, client }) to the provider API so grant extensions and companion plugins can get the sub a client sees for a user (#12505)
- Added opt-in pairwise sub in JWT access tokens for pairwise clients with accessTokenSubject: "pairwise", so decoding a token no longer reveals the user ID (#12505)
- Added a clientRegistrationEnableEndSession option to allow RP-initiated logout at /oauth2/end-session for dynamically registered and other registered OAuth clients (#12510)
- Fixed introspection of delegated access tokens to show pairwise clients the pairwise sub of each user in act instead of user IDs (#12523)
- Added accessTokenClaims from issueTokens to opaque access token introspection, so custom grants now see those claims (#12508)
- Added sub_profile to each actor in a delegated token's act claim, marking clients as "service" and users as "user" (#12584)
- Changed token exchange to deny subject tokens whose may_act names no actor, with invalid_request, instead of allowing any actor (#12584)
- Fixed introspection and pairwise JWT access tokens exposing the real user ID in may_act.sub to pairwise clients (#12584)
- Added revocation of a grant's JWT access tokens when its refresh token is revoked or a code or rotated token is replayed, with revocableJwtAccessTokens (#12520)
- Changed refresh token revocation at /oauth2/revoke to delete every opaque access token of its grant, including those issued before earlier refreshes (#12520)
- Added verifyResourceRequest to verify JWT and opaque access token requests in-process on plugin endpoints served by the auth server (#12516)
- Added a warning when discovery ignores a metadata contribution from an OAuth provider extension or client discovery (#12574)
- Improved discovery metadata warnings to log once per server instead of on every request to the well-known endpoints (#12574)
Bug Fixes
- Fixed authorization_details_types_supported in protected resource metadata to be typed as string[], matching RFC 9728 (#12513)
- Changed the OAuth provider to reserve the ba_sub access token claim, dropping custom values for it with a warning (#12577)
- Fixed token requests with an already-used DPoP proof consuming an unused authorization code or device code, so clients can retry with a fresh proof (#12600)
- Fixed refresh token revocation and replay handling to retry refresh-token family teardown when a delete fails, such as after a MySQL deadlock (#12643)
- Fixed authorization code reuse to revoke issued tokens only when the request comes from the original client, including its code_verifier for PKCE codes (#12526)
- Fixed OAuth grant revocation to also stop token requests for that grant that are still issuing tokens (#12581)
For detailed changes, see CHANGELOG
@better-auth/core
❗ Breaking Changes
- Changed createPrivateKeyJwtClientAssertionGetter to sign client assertions for the authorization server's issuer by default when the issuer is known (#12599)
Features
- Added createDpopFetch in better-auth/oauth2/dpop-client for sending DPoP-bound requests with per-origin nonce handling and a single retry on use_dpop_nonce (#12506)
- Added an issuer option to validateAuthorizationCode, refreshAccessToken, clientCredentialsToken, and pushAuthorizationRequest for client assertion getters (#12580)
- Added endpointType to custom token endpoint authentication hooks, and issuer to hooks and client assertion getters when Better Auth knows it (#12580)
- Added a fetch option to validateAuthorizationCode, refreshAccessToken, clientCredentialsToken, and pushAuthorizationRequest so requests can send DPoP proofs (#12596)
- Added pushAuthorizationRequest to @better-auth/core/oauth2 for sending pushed authorization requests (RFC 9126) and getting the redirect URL (#12519)
Bug Fixes
- Added use_dpop_nonce to the DpopBindingErrorCode and DpopProofErrorCode types exported from @better-auth/core/oauth2 (#12511)
- Fixed verifyAccessTokenRequest to reject a missing or unsupported Authorization scheme without an invalid_token error, matching RFC 6750 (#12512)
For detailed changes, see CHANGELOG
@better-auth/mcp
❗ Breaking Changes
- Changed requireMcpAuth to check access tokens against the OAuth provider's records when it runs in the same process, accepting opaque tokens and rejecting revoked ones (#12597)
For detailed changes, see CHANGELOG
@better-auth/sso
❗ Breaking Changes
- Added oidcConfig.clientAssertionAudience so OIDC SSO providers using private_key_jwt can sign client assertions for the provider's registered issuer (#12599)
For detailed changes, see CHANGELOG
@better-auth/ciba
Features
- Added support for acr_values and authorization_details in CIBA requests to /oauth2/bc-authorize (#12509)
- Added authorization_details_types to client registration so CIBA rejects requests for unregistered authorization details types from clients that set the field (#12591)
- Improved OAuth provider extension conflict errors and warnings to name the extensions involved, with an optional name for extensions (#12646)
Bug Fixes
- Fixed CIBA approval links and the advertised backchannel_authentication_endpoint containing a double slash when baseURL ends in / (#12638)
For detailed changes, see CHANGELOG
@better-auth/cimd
Features
- Fixed cimd() startup failing with a duplicate client discovery error when its init() runs more than once for the same oauthProvider() instance (#12646)
- Improved OAuth provider extension conflict errors and warnings to name the extensions involved, with an optional name for extensions (#12646)
For detailed changes, see CHANGELOG
Contributors
Thanks to everyone who contributed to this release:
- @gustavovalverde
Full changelog: v1.8.0-beta.9...v1.8.0-beta.10
Original source - Nov 14, 2026
- Date parsed from source:Nov 14, 2026
- First seen by Releasebot:Nov 15, 2026
- Modified by Releasebot:Nov 15, 2026
v1.7.25
Better Auth releases fixes for OAuth and DPoP, including cross-origin header access, signing-key verification on restricted runtimes, and more reliable token checks. The update also improves authorization URL handling and DPoP replay-store performance.
Important
Action required
If you want
oauthProviderResourceClient(auth)to keep fetching signing keys over HTTP, setjwksUrl. (#12578)better-auth
Bug Fixes
- Fixed endpoint errors dropping
Access-Control-Expose-Headersnames set earlier by a hook or the endpoint, so cross-origin browser clients keep access to exposed headers (#12603)
For detailed changes, see CHANGELOG
@better-auth/oauth-provider
Bug Fixes
- Fixed OAuth provider 401 challenges to expose
WWW-Authenticateto cross-origin browser clients on every endpoint, including client registration and token endpoint authentication (#12603) - Fixed DPoP requests failing with a 500 error on deployments that keep verification values only in secondary storage (#12587)
- Fixed RP-initiated logout on runtimes that block requests to their own hostname by verifying
id_token_hintwith in-process signing keys (#12578) - Fixed introspection and revocation reporting valid JWT access tokens as inactive when two auth instances share one
jwt()plugin object (#12578) - Fixed
oauthProviderResourceClient(auth)token verification on runtimes that block requests to their own hostname by reading signing keys from the auth instance (#12578)
For detailed changes, see CHANGELOG
@better-auth/core
Bug Fixes
- Fixed authorization URLs re-encoding query parameters already present on the provider's authorization endpoint, such as
%20becoming+(#12572) - Fixed the default in-memory DPoP replay store slowing down as request volume grows (#12586)
- Fixed DPoP requests failing with a 500 error on deployments that keep verification values only in secondary storage (#12587)
For detailed changes, see CHANGELOG
@better-auth/mcp
Bug Fixes
- Fixed DPoP requests failing with a 500 error on deployments that keep verification values only in secondary storage (#12587)
For detailed changes, see CHANGELOG
Contributors
Thanks to everyone who contributed to this release:
@gustavovalverdeFull changelog: v1.7.24...v1.7.25
Original source Similar to Better Auth with recent updates:
- Claude Code updates494 release notes · Latest Nov 20, 2026
- ChatGPT updates255 release notes · Latest Nov 19, 2026
- OpenAI Models updates55 release notes · Latest Nov 18, 2026
- Gemini updates478 release notes · Latest Nov 19, 2026
- Gemini API updates160 release notes · Latest Nov 19, 2026
- Claude updates194 release notes · Latest Nov 17, 2026
- Nov 14, 2026
- Date parsed from source:Nov 14, 2026
- First seen by Releasebot:Nov 15, 2026
- Modified by Releasebot:Nov 15, 2026
v1.7.24
Better Auth releases fixes across its authentication and OAuth packages, improving expired-token cleanup, DPoP guidance, endpoint error handling, and OAuth discovery URLs while aligning package dependencies.
Important
Action required
If you accept DPoP-bound tokens, call
enforceDpopBindingfrombetter-auth/oauth2in your endpoint with the request and a shared replay store. (#12498)better-auth
Bug Fixes
- Improved verification lookups to delete expired rows at most once a minute per server instance instead of on every lookup (#12593)
For detailed changes, see CHANGELOG
@better-auth/oauth-provider
Bug Fixes
- Clarified that
requireActiveAccessTokenchecks only the token and does not enforce DPoP binding (#12498) - Fixed plugin hook and endpoint errors turning into generic 500 responses when an app installs more than one copy of
better-call(#12503) - Fixed official packages to accept any
better-call1.4 patch release from 1.4.5 as a peer, so plugins share one copy (#12502) - Fixed OAuth provider discovery to stop advertising endpoint URLs with a double slash when baseURL ends in / (#12598)
For detailed changes, see CHANGELOG
@better-auth/cimd
Bug Fixes
- Fixed plugin hook and endpoint errors turning into generic 500 responses when an app installs more than one copy of
better-call(#12503) - Fixed official packages to accept any
better-call1.4 patch release from 1.4.5 as a peer, so plugins share one copy (#12502)
For detailed changes, see CHANGELOG
@better-auth/passkey
Bug Fixes
- Fixed plugin hook and endpoint errors turning into generic 500 responses when an app installs more than one copy of
better-call(#12503) - Fixed official packages to accept any
better-call1.4 patch release from 1.4.5 as a peer, so plugins share one copy (#12502)
For detailed changes, see CHANGELOG
@better-auth/scim
Bug Fixes
- Fixed plugin hook and endpoint errors turning into generic 500 responses when an app installs more than one copy of
better-call(#12503) - Fixed official packages to accept any
better-call1.4 patch release from 1.4.5 as a peer, so plugins share one copy (#12502)
For detailed changes, see CHANGELOG
@better-auth/sso
Bug Fixes
- Fixed plugin hook and endpoint errors turning into generic 500 responses when an app installs more than one copy of
better-call(#12503) - Fixed official packages to accept any
better-call1.4 patch release from 1.4.5 as a peer, so plugins share one copy (#12502)
For detailed changes, see CHANGELOG
@better-auth/stripe
Bug Fixes
- Fixed plugin hook and endpoint errors turning into generic 500 responses when an app installs more than one copy of
better-call(#12503) - Fixed official packages to accept any
better-call1.4 patch release from 1.4.5 as a peer, so plugins share one copy (#12502)
For detailed changes, see CHANGELOG
@better-auth/api-key
Bug Fixes
- Fixed official packages to accept any
better-call1.4 patch release from 1.4.5 as a peer, so plugins share one copy (#12502)
For detailed changes, see CHANGELOG
@better-auth/core
Bug Fixes
- Fixed official packages to accept any
better-call1.4 patch release from 1.4.5 as a peer, so plugins share one copy (#12502)
For detailed changes, see CHANGELOG
@better-auth/electron
Bug Fixes
- Fixed official packages to accept any
better-call1.4 patch release from 1.4.5 as a peer, so plugins share one copy (#12502)
For detailed changes, see CHANGELOG
@better-auth/expo
Bug Fixes
- Fixed
@better-auth/expoto use the better-call copy installed by better-auth instead of adding a second copy to Expo apps (#12502)
For detailed changes, see CHANGELOG
@better-auth/mcp
Bug Fixes
- Fixed official packages to accept any
better-call1.4 patch release from 1.4.5 as a peer, so plugins share one copy (#12502)
For detailed changes, see CHANGELOG
Contributors
Thanks to everyone who contributed to this release:
- @gustavovalverde
Full changelog: v1.7.23...v1.7.24
Original source - Nov 13, 2026
- Date parsed from source:Nov 13, 2026
- First seen by Releasebot:Nov 14, 2026
v1.7.23
Better Auth ships fixes across MCP and OAuth authentication, including more reliable DPoP challenges and cross-origin access to authentication headers. The release also resolves issues in Electron sign-in, database adapters, and parallel tests, with clearer guidance for shared replay storage.
Important
Action required
- If you want requireMcpAuth to keep fetching signing keys over HTTP, set jwksUrl. (#12501)
- If your CORS layer sets its own Access-Control-Expose-Headers, include WWW-Authenticate in it. (#12521)
- If you run createMcpProtectedRequestHandler in a multi-instance or serverless deployment, set dpop.replayStore to a shared store such as createDpopReplayStore(internalAdapter). (#12504)
better-auth
Bug Fixes
- Fixed getTestInstance sharing one MongoDB database across test files, so parallel tests no longer delete each other's data (#12543)
For detailed changes, see CHANGELOG
@better-auth/mcp
Bug Fixes
- Improved the dpop.replayStore documentation on createMcpProtectedRequestHandler to explain the in-memory default and when to use a shared store (#12504)
- Fixed requireMcpAuth to accept tokens when the JWT plugin publishes its keys at jwks.remoteUrl (#12501)
- Fixed requireMcpAuth returning a 500 on runtimes that block requests to their own hostname, such as a single Cloudflare Worker (#12501)
- Fixed cross-origin browser clients being unable to read WWW-Authenticate challenges from OAuth resource servers and MCP helpers (#12521)
- Fixed OAuth resource servers to answer DPoP requests lacking a required scope with a DPoP insufficient_scope challenge instead of Bearer (#12525)
For detailed changes, see CHANGELOG
@better-auth/oauth-provider
Bug Fixes
- Fixed cross-origin browser clients being unable to read WWW-Authenticate challenges from OAuth resource servers and MCP helpers (#12521)
- Fixed protected resource requests using an unsupported authorization scheme or no scheme to receive a Bearer challenge with resource_metadata (#12515)
- Fixed OAuth resource servers to answer DPoP requests lacking a required scope with a DPoP insufficient_scope challenge instead of Bearer (#12525)
- Fixed OAuth token requests that fail PKCE, redirect_uri, resource, or DPoP validation consuming the authorization or device code (#12499)
- Added a warning in the OAuth provider when two extensions contribute the same discovery metadata key (#12500)
For detailed changes, see CHANGELOG
@better-auth/core
Bug Fixes
- Improved the advanced.database.validateSchema documentation to explain when validation runs and which adapters skip it (#12480)
- Fixed requireMcpAuth returning a 500 on runtimes that block requests to their own hostname, such as a single Cloudflare Worker (#12501)
For detailed changes, see CHANGELOG
@better-auth/electron
Bug Fixes
- Fixed Electron sign-in callbacks being missed on Windows and Linux when Chromium reorders or appends launch arguments (#12490)
For detailed changes, see CHANGELOG
@better-auth/kysely-adapter
Bug Fixes
- Fixed the Kysely adapter on PostgreSQL failing to save json fields whose value is an array (#12530)
For detailed changes, see CHANGELOG
@better-auth/memory-adapter
Bug Fixes
- Fixed the memory adapter reusing the ids of stored rows when generateId is "serial" after a delete (#12544)
For detailed changes, see CHANGELOG
Contributors
Thanks to everyone who contributed to this release:
@bytaesu, @grant0417, @gustavovalverde
Full changelog: v1.7.22...v1.7.23
Original source - Nov 12, 2026
- Date parsed from source:Nov 12, 2026
- First seen by Releasebot:Nov 13, 2026
v1.8.0-beta.9
Better Auth ships beta updates for OAuth token exchange, DPoP and sender-constrained tokens, plus SSO sign-in fixes for providers that omit email attributes. The release also includes migration steps and breaking changes for OAuth provider integrations.
Important
Action required
- If your SAML IdP sends no email attribute and a NameID in another Format or with no Format, send an email attribute or the emailAddress NameID Format, set samlConfig.mapping.email to the attribute it sends, or return the NameID from mapProfileToUser. (#12484)
- If you use the OAuth provider, run npx auth@latest migrate or npx auth@latest generate before upgrading to add the new optional act column on oauthAccessToken; if you set act via customAccessTokenClaims, an extension claims.accessToken contributor, or a resource's customClaims, it is now stripped, so pass act to issueTokens in custom grants instead. (#12439)
- If your clientAuthentication strategy returns a DPoP key (jkt), the token type is now DPoP, so make your clients send a DPoP proof with each request to a protected resource. (#12440)
- If you have a custom OAuthProviderApi implementation, add the verifyDpopProof() and issueDpopNonce() methods. (#12437)
- If your clients exchange their own access tokens bound by a mechanism other than DPoP, such as an mTLS certificate in cnf["x5t#S256"], have your clientAuthentication strategy return the same confirmation. (#12438)
@better-auth/oauth-provider
❗ Breaking Changes
- Added RFC 8693 delegation to oauthTokenExchange(), so a service can exchange tokens with an actor_token and get an act claim (#12439)
Features
- Added an expectedJkt option to provider.resolveConfirmation() so extension grants can keep a DPoP-bound token bound to the same key (#12436)
- Added verifyDpopProof() and issueDpopNonce() to getOAuthProviderApi so plugin endpoints can verify DPoP proofs and nonces (#12437)
Bug Fixes
- Fixed client_credentials tokens to be bound to the confirmation returned by a clientAuthentication strategy, such as an mTLS certificate thumbprint (#12440)
- Fixed the OAuth provider to reject a malformed sender-constraint confirmation with server_error instead of issuing a token (#12443)
- Fixed oauthTokenExchange() to require a matching confirmation when a client exchanges its own access token bound by a mechanism other than DPoP (#12438)
For detailed changes, see CHANGELOG
@better-auth/sso
Bug Fixes
- Added a mapProfileToUser option so OIDC and SAML SSO providers that send no email can still sign users in (#12484)
- Changed SAML sign-in to use the NameID as the user's email only when its Format is the emailAddress format (#12484)
- Fixed SAML users who sign in without a name attribute to get their email as their name instead of an opaque NameID (#12484)
For detailed changes, see CHANGELOG
Contributors
Thanks to everyone who contributed to this release:
- @gustavovalverde
Full changelog: v1.8.0-beta.8...v1.8.0-beta.9
Original source - Nov 12, 2026
- Date parsed from source:Nov 12, 2026
- First seen by Releasebot:Nov 13, 2026
v1.7.22
Better Auth ships a bug-fix release that improves session handling, OAuth and resource-server error responses, and reliability across Cloudflare Workers, SSR, and database adapters. It also clarifies Stripe webhook failures when no local subscription exists.
better-auth
Bug Fixes
- Fixed verification value consumption hanging on Cloudflare Workers when an earlier request for the same identifier ended mid-query (#12451)
- Fixed module-scope auth instances on Cloudflare Workers logging a schema validation error on every cold start by validating on first use (#12448)
- Fixed deferSessionRefresh refresh requests failing with a 415 error in Next.js and Nuxt (#12330)
- Fixed ReferenceError: window is not defined when a client session subscription is cleaned up after a test environment tears down its globals (#12324)
- Fixed client session refresh listeners piling up on the server during SSR (#12324)
- Fixed session polling never firing when the runtime's navigator does not report connectivity (#12462)
- Fixed OAuth sign-up rejected by a user.create.before hook returning false logging a TypeError (#12331)
- Fixed deleteOrganization clearing the session's active organization when a beforeDeleteOrganization hook rejected the delete (#12334)
- Fixed revokeSession, revokeSessions, and deleteUser({ token }) to expire session cookies when revoking the current session or deleting the user (#12321)
- Fixed getSession to no longer leave an expired session in the request context after returning null (#12459)
For detailed changes, see CHANGELOG
@better-auth/core
Bug Fixes
- Fixed introspected access tokens that fail aud, iss, exp, or nbf claim checks to return a 401 instead of a 500 (#12432)
- Fixed getSession failing with "Failed to get session" when a user.additionalFields entry references a table outside the Better Auth schema (#12333)
- Fixed resource-server challenges turning rejected requests into 500 errors, and added invalid_token error details when a presented token fails verification (#12445)
For detailed changes, see CHANGELOG
@better-auth/oauth-provider
Bug Fixes
- Fixed failed requests using the DPoP authorization scheme to receive a DPoP challenge instead of a Bearer challenge (#12447)
- Fixed resource-server challenges turning rejected requests into 500 errors, and added invalid_token error details when a presented token fails verification (#12445)
- Fixed /oauth2/userinfo to send a WWW-Authenticate challenge on every 401 response, including DPoP failures and requests with no token (#12446)
For detailed changes, see CHANGELOG
@better-auth/drizzle-adapter
Bug Fixes
- Fixed getSession failing with "Failed to get session" when a user.additionalFields entry references a table outside the Better Auth schema (#12333)
For detailed changes, see CHANGELOG
@better-auth/mcp
Bug Fixes
- Fixed failed requests using the DPoP authorization scheme to receive a DPoP challenge instead of a Bearer challenge (#12447)
For detailed changes, see CHANGELOG
@better-auth/prisma-adapter
Bug Fixes
- Fixed getSession failing with "Failed to get session" when a user.additionalFields entry references a table outside the Better Auth schema (#12333)
For detailed changes, see CHANGELOG
@better-auth/stripe
Bug Fixes
- Fixed Stripe customer.subscription.updated webhooks for customers with no local subscription to log a clear warning instead of failing with a TypeError (#12473)
For detailed changes, see CHANGELOG
@better-auth/telemetry
Bug Fixes
- Fixed requests failing on Cloudflare Workers for module-scope auth instances when telemetry is enabled without a static baseURL (#12448)
For detailed changes, see CHANGELOG
Contributors
Thanks to everyone who contributed to this release:
@AmalkrishnaAS, @Bekacru, @bytaesu, @choksi2212, @flcrom, @ghazy2001, @gustavovalverde, @mrpmohiburrahman, @umeraamir69
Full changelog: v1.7.21...v1.7.22
Original source - Nov 12, 2026
- Date parsed from source:Nov 12, 2026
- First seen by Releasebot:Nov 13, 2026
v1.7.21
Better Auth ships a bug-fix release that improves OAuth and SAML flows, SCIM synchronization, and database adapter reliability. It also addresses sign-in failures, Cloudflare Workers hangs, and passkey configuration issues across its ecosystem.
Important
Action required
- If you use SCIM with an adapter that has no native transactions, switch to an adapter with native transactions to provision users and groups. (#12413)
- If you use the MongoDB adapter and an index build fails because of duplicate values, missing createIndex permission, or a conflicting index on the same field, fix the cause and restart. (#12299)
- If you rely on update changing every row that matches a non-unique filter, use updateMany instead. (#12390)
- If you set discoveryHeaders and your discoveryUrl redirects to another origin, set discoveryUrl to the final URL, because discovery now fails on cross-origin redirects. (#12179)
- If your clients match on the invalid_client_metadata error code for rejected post_logout_redirect_uris, update them to check for invalid_redirect_uri. (#12391)
- If you throw from sendVerificationEmail to reject a sign-up, use a databaseHooks.user.create.before hook instead, because a thrown error is now logged and the sign-up still succeeds. (#12052)
- If a wildcard in baseURL.allowedHosts covers your passkey rpID, you don't set origin, and you add tenants at runtime, return their origins from a trustedOrigins function that checks your tenant records. (#12388)
better-auth
Bug Fixes
- Fixed plugin packages importing from the better-auth root, so bundlers no longer emit unused Kysely chunks when used with better-auth/minimal (#12404)
- Fixed magic link and email OTP sign-in failing with a 500 for users with an unverified email on Prisma with MongoDB when id columns use @db.ObjectId (#12126)
- Fixed the device approval page showing a valid code as invalid when the same signed-in user looked it up twice at once, such as under React Strict Mode (#12392)
- Fixed sign-ins with a genericOAuth provider using discoveryUrl and OAuth provider requests using resources hanging on Cloudflare Workers (#12395)
- Fixed Generic OAuth to send authorizationHeaders on access token refresh, added an optional headers input to refreshAccessToken and refreshAccessTokenRequest, and prevented invalid combined headers with differently cased client authentication headers (#12401)
- Fixed generic OAuth to send discoveryHeaders when fetching same-origin jwks_uri keys, and to follow discovery redirects only within the discoveryUrl origin (#12179)
- Fixed intermittent schema does not exist and relation does not exist errors on PostgreSQL during the startup schema check and npx auth@latest migrate when other schemas are dropped concurrently (#11912)
- Fixed email sign-up to keep database writes made while sending verification emails or running onExistingUserSignUp when using a background task handler with a transactional adapter (#12052)
- Fixed SIWE verification to stop exposing internal error messages in its 401 response and log them on the server instead (#12403)
For detailed changes, see CHANGELOG
@better-auth/oauth-provider
Bug Fixes
- Fixed the OAuth provider returning [object Promise] instead of the refresh token when formatRefreshToken.encrypt is async (#12409)
- Fixed magic link and email OTP sign-in failing with a 500 for users with an unverified email on Prisma with MongoDB when id columns use @db.ObjectId (#12126)
- Fixed sign-ins with a genericOAuth provider using discoveryUrl and OAuth provider requests using resources hanging on Cloudflare Workers (#12395)
- Changed OAuth provider client registration and updates to return invalid_redirect_uri instead of invalid_client_metadata for rejected post_logout_redirect_uris entries (#12391)
- Fixed OAuth provider returning a 500 on near-simultaneous refresh token reuse for opaque access tokens on databases that enforce foreign keys (#11911)
- Fixed OAuth provider consent denial to redirect to the client only while the client is enabled and its redirect_uri is still valid (#12385)
- Fixed OAuth provider to revoke in-flight opaque access tokens after refresh token reuse or a replayed authorization code on databases without foreign keys (#12389)
For detailed changes, see CHANGELOG
@better-auth/core
Bug Fixes
- Fixed null filters on id and reference fields being coerced to 0 when advanced.database.generateId is "serial" (#12402)
- Fixed authentication requests hanging on Cloudflare Workers when the request that started schema validation ended before validation finished (#11716)
- Fixed magic link and email OTP sign-in failing with a 500 for users with an unverified email on Prisma with MongoDB when id columns use @db.ObjectId (#12126)
- Fixed Generic OAuth to send authorizationHeaders on access token refresh, added an optional headers input to refreshAccessToken and refreshAccessTokenRequest, and prevented invalid combined headers with differently cased client authentication headers (#12401)
- Fixed telemetry to report Cloudflare Workers as workerd instead of node when nodejs_compat is enabled, and exported the runtime detection from @better-auth/core/env (#12425)
For detailed changes, see CHANGELOG
@better-auth/sso
Bug Fixes
- Fixed plugin packages importing from the better-auth root, so bundlers no longer emit unused Kysely chunks when used with better-auth/minimal (#12404)
- Fixed SAML Single Logout so refreshing a session extends that session's own logout record, for users signed in more than once with the same NameID on the Prisma or MongoDB adapter (#12424)
- Fixed SAML Single Logout (saml.enableSingleLogout) for users who stay signed in past their session's first expiry, for both IdP-initiated and SP-initiated logout (#12417)
- Fixed SAML replay protection to reject a signed response resubmitted with its assertion ID written as XML character references when allowIdpInitiated: true or enableInResponseToValidation: false is set (#12421)
For detailed changes, see CHANGELOG
@better-auth/prisma-adapter
Bug Fixes
- Fixed magic link and email OTP sign-in failing with a 500 for users with an unverified email on Prisma with MongoDB when id columns use @db.ObjectId (#12126)
- Fixed Prisma adapter updates comparing a unique field with null failing with a validation error, and update now changes only one matching row (#12390)
- Fixed the Prisma adapter with provider: "mongodb" to match contains, starts_with, ends_with, and case-insensitive filters as literal text instead of regex patterns (#11807)
For detailed changes, see CHANGELOG
@better-auth/scim
Bug Fixes
- Fixed plugin packages importing from the better-auth root, so bundlers no longer emit unused Kysely chunks when used with better-auth/minimal (#12404)
- Fixed SCIM Groups with more than 100 members to sync in full, including Group creation, updates, deletion, role mapping, and managed connection listings (#12070)
- Fixed apps using the SCIM plugin on adapters without native transactions, such as Cloudflare D1, failing at startup; /scim/v2 requests now return 501 Not Implemented on those adapters (#12413)
For detailed changes, see CHANGELOG
@better-auth/electron
Bug Fixes
- Fixed failed deep link authentication in Electron to be logged instead of causing an unhandled promise rejection in the main process (#12409)
- Fixed plugin packages importing from the better-auth root, so bundlers no longer emit unused Kysely chunks when used with better-auth/minimal (#12404)
For detailed changes, see CHANGELOG
@better-auth/api-key
Bug Fixes
- Fixed plugin packages importing from the better-auth root, so bundlers no longer emit unused Kysely chunks when used with better-auth/minimal (#12404)
For detailed changes, see CHANGELOG
@better-auth/expo
Bug Fixes
- Fixed plugin packages importing from the better-auth root, so bundlers no longer emit unused Kysely chunks when used with better-auth/minimal (#12404)
For detailed changes, see CHANGELOG
@better-auth/kysely-adapter
Bug Fixes
- Fixed intermittent schema does not exist and relation does not exist errors on PostgreSQL during the startup schema check and npx auth@latest migrate when other schemas are dropped concurrently (#11912)
For detailed changes, see CHANGELOG
@better-auth/mongo-adapter
Bug Fixes
- Added indexes in the MongoDB adapter for schema fields marked unique or index, preventing duplicate users from concurrent sign-ups with the same email (#12299)
For detailed changes, see CHANGELOG
@better-auth/passkey
Bug Fixes
- Fixed passkey startup to no longer require origin when a wildcard in baseURL.allowedHosts covers your rpID, accepting exact trusted origins instead (#12388)
For detailed changes, see CHANGELOG
@better-auth/stripe
Bug Fixes
- Fixed plugin packages importing from the better-auth root, so bundlers no longer emit unused Kysely chunks when used with better-auth/minimal (#12404)
For detailed changes, see CHANGELOG
@better-auth/telemetry
Bug Fixes
- Fixed telemetry to report Cloudflare Workers as workerd instead of node when nodejs_compat is enabled, and exported the runtime detection from @better-auth/core/env (#12425)
For detailed changes, see CHANGELOG
@better-auth/test-utils
Bug Fixes
- Fixed the adapter test for findMany with multiple operators to create users from generated data like other adapter tests (#12409)
For detailed changes, see CHANGELOG
Contributors
Thanks to everyone who contributed to this release:
@ArjunCodess, @bytaesu, @ghazy2001, @gustavovalverde, @hardikguptaofficialgit, @ItzSudhan, @lakshya-dhariwal, @mallachari, @umeraamir69
Full changelog: v1.7.20...v1.7.21
Original source - Nov 12, 2026
- Date parsed from source:Nov 12, 2026
- First seen by Releasebot:Nov 11, 2026
- Modified by Releasebot:Nov 13, 2026
v1.7.20
Better Auth releases fixes across OAuth, database adapters, and SSO, including safer public-client prelogin checks, improved redirect URI and issuer handling, more consistent database queries, and corrected SAML clock-skew validation.
Important
Action required
If your issuer (baseURL, or jwt.issuer when set) uses http on a non-loopback host behind a TLS-terminating proxy, set baseURL to the public https URL, since discovery and the iss parameter no longer rewrite it to https. (#11904)
@better-auth/oauth-provider
Bug Fixes
- Fixed POST /oauth2/public-client-prelogin with allowPublicClientPrelogin to return a client only when its client_id matches the signed oauth_query, otherwise responding with 401 invalid_client (#12237)
- Fixed oauthProviderResourceClient(auth) defaults to accept issued access tokens when baseURL is only an origin, by including the auth path in the default issuer, JWKS, and introspection URLs (#12234)
- Added an allowInsecureRedirectUri option so OAuth provider deployments served over HTTP on private networks can accept http redirect URIs (#11904)
For detailed changes, see CHANGELOG
@better-auth/prisma-adapter
Bug Fixes
- Fixed Prisma adapter incrementOne and update calls using mode: "insensitive" filters to match case-insensitively on PostgreSQL and MongoDB (#11809)
- Fixed Prisma adapter queries with eq null on MongoDB to also match records where the optional field was never set (#11806)
For detailed changes, see CHANGELOG
@better-auth/core
Bug Fixes
- Added an allowInsecureRedirectUri option so OAuth provider deployments served over HTTP on private networks can accept http redirect URIs (#11904)
For detailed changes, see CHANGELOG
@better-auth/memory-adapter
Bug Fixes
- Fixed ne null where clauses in the memory adapter to no longer match records where the field was never set (#11806)
For detailed changes, see CHANGELOG
@better-auth/sso
Bug Fixes
- Fixed SAML assertion validation to apply the default 5-minute saml.clockSkew to the NotBefore and NotOnOrAfter checks in samlify (#12309)
For detailed changes, see CHANGELOG
Contributors
Thanks to everyone who contributed to this release:
@ArjunCodess, @gustavovalverde
Full changelog: v1.7.19...v1.7.20
Original source - Nov 12, 2026
- Date parsed from source:Nov 12, 2026
- First seen by Releasebot:Nov 5, 2026
- Modified by Releasebot:Nov 13, 2026
v1.8.0-beta.6
Better Auth strengthens OAuth provider security with DPoP key binding for token exchanges and rejects repeated standard parameters in form-encoded authorization requests, aligning their behavior with GET requests.
Important
Action required
- If your clients exchange their own DPoP-bound access tokens with oauthTokenExchange(), send a DPoP proof signed by the token's key, or have your clientAuthentication strategy return that key as confirmation. (#12262)
- If your clients send a standard parameter more than once in form-encoded POST requests to /oauth2/authorize, such as state=a&state=b, change them to send each standard parameter only once. (#12261)
@better-auth/oauth-provider
❗ Breaking Changes
- Fixed form POST requests to /oauth2/authorize to reject repeated standard parameters with invalid_request, matching GET behavior (#12261)
Features
- Added DPoP key binding to oauthTokenExchange() so a client exchanging its own DPoP-bound access token must prove the same key (#12262)
For detailed changes, see CHANGELOG
Contributors
Thanks to everyone who contributed to this release:
- @gustavovalverde
Full changelog: v1.8.0-beta.5...v1.8.0-beta.6
Original source - Nov 12, 2026
- Date parsed from source:Nov 12, 2026
- First seen by Releasebot:Nov 5, 2026
- Modified by Releasebot:Nov 13, 2026
v1.7.18
Better Auth fixes session revocation with secondary storage, improves test-instance cleanup and MySQL test reliability, and resolves resource-server rejection of introspected tokens with remote verification enabled.
Important
Action required
If you use getTestInstance with testWith: "mysql", run a MySQL server at 127.0.0.1:3306 with the root password set to root_password. (#12244)
better-auth
Bug Fixes
- Fixed "revoke all sessions" with secondaryStorage and storeSessionInDatabase to also revoke sessions created while the revocation is running, except sessions created by a session.delete.after hook, which stay active (#12259)
- Fixed getTestInstance from better-auth/test to close its own Postgres connection pool and SQLite database when the test file finishes, while with Vitest's default sequence.hooks: "stack" your afterAll hooks still run first and can keep using the instance (#12250)
- Fixed getTestInstance with testWith: "mysql" hanging, and added a separate database per instance so several instances can run in one test file (#12244)
For detailed changes, see CHANGELOG
@better-auth/core
Bug Fixes
- Fixed resource servers rejecting all introspected tokens when verifyOptions.typ is set together with remoteVerify (#12249)
For detailed changes, see CHANGELOG
Contributors
Thanks to everyone who contributed to this release:
- @gustavovalverde
Full changelog: v1.7.17...v1.7.18
Original source - Nov 12, 2026
- Date parsed from source:Nov 12, 2026
- First seen by Releasebot:Oct 16, 2026
- Modified by Releasebot:Nov 13, 2026
v1.8.0-beta.8
Better Auth releases v1.8.0-beta.8 with server-provided DPoP nonce support, stronger single-use nonce checks for social and Google One Tap sign-ins, and OAuth client secret expiry fixes. The update also changes OAuth authorization header handling and requires migration steps for some database adapters.
Important
Action required
- If you set an Authorization entry in authorizationHeaders or pass authorization in headers to the @better-auth/core/oauth2 token request functions, remove it and set the header from customizeRequest with tokenEndpointAuth method custom, which must also set every credential the provider requires. (#12416)
- If you use the built-in Kysely adapter, run npx auth@latest migrate; if you use Prisma or Drizzle, run npx auth@latest generate and apply the migration before deploying, to add the expiresAt column to oauthClient. MongoDB needs no migration. (#11802)
- If you use built-in ID token verification and clients send an opaque (non-JWT) token such as a Facebook Graph access token together with a nonce, stop sending the nonce, because those requests are now rejected. If you use a custom verifyIdToken, compare the nonce to the token's claim yourself. (#11823)
- If you call /one-tap/callback or auth.api.oneTapCallback yourself, first call POST /one-tap/nonce, pass the returned nonce to google.accounts.id.initialize({ nonce }), and send it as nonce in the callback body. If you set the client's nonce option or a nonce in additionalOptions, remove it. (#11823)
better-auth
❗ Breaking Changes
- Changed generic OAuth to fail at startup when authorizationHeaders contains an Authorization entry, and made validateAuthorizationCode, authorizationCodeRequest, refreshAccessToken, and refreshAccessTokenRequest throw when passed authorization in headers (#12416)
- Added requireIssuedIdTokenNonce for social providers to bind client-submitted ID tokens to a single-use server-issued nonce (#11823)
- Changed /one-tap/callback to require a single-use nonce from the new POST /one-tap/nonce endpoint so each Google ID token signs in only once (#11823)
For detailed changes, see CHANGELOG
@better-auth/core
❗ Breaking Changes
- Changed generic OAuth to fail at startup when authorizationHeaders contains an Authorization entry, and made validateAuthorizationCode, authorizationCodeRequest, refreshAccessToken, and refreshAccessTokenRequest throw when passed authorization in headers (#12416)
- Added requireIssuedIdTokenNonce for social providers to bind client-submitted ID tokens to a single-use server-issued nonce (#11823)
Features
- Added support for server-provided DPoP nonces in the OAuth provider through dpop: { nonce: { required: true } }, plus resource server support with verifyAccessTokenRequest, createResourceServerChallenge, and createDpopNonce (#12376)
For detailed changes, see CHANGELOG
@better-auth/oauth-provider
Features
- Added support for server-provided DPoP nonces in the OAuth provider through dpop: { nonce: { required: true } }, plus resource server support with verifyAccessTokenRequest, createResourceServerChallenge, and createDpopNonce (#12376)
Bug Fixes
- Fixed OAuth provider client secret expiry so it is saved, returned as client_secret_expires_at, and enforced with invalid_client at the token, introspection, and revocation endpoints (#11802)
For detailed changes, see CHANGELOG
@better-auth/mcp
Features
- Added support for server-provided DPoP nonces in the OAuth provider through dpop: { nonce: { required: true } }, plus resource server support with verifyAccessTokenRequest, createResourceServerChallenge, and createDpopNonce (#12376)
For detailed changes, see CHANGELOG
Contributors
Thanks to everyone who contributed to this release:
- @gustavovalverde
Full changelog: v1.8.0-beta.7...v1.8.0-beta.8
Original source - Nov 10, 2026
- Date parsed from source:Nov 10, 2026
- First seen by Releasebot:Nov 11, 2026
v1.8.0-beta.7
Better Auth releases a beta update carrying forward all fixes from v1.7.19.
Bug Fixes
This beta includes all fixes from v1.7.19.
Contributors
Thanks to everyone who contributed to this release:
@Adnan-Husayn, @AryaKesharwani, @binaryshrey, @bytaesu, @Faiziimam, @Gourav224, @jashkarangiya, @NoiceHax, @PhillJK, @Tushar-Khandelwal-2004, @Tyagiquamar, @umeraamir69, @unjica, @YIOYIOIOI
Full changelog: v1.8.0-beta.6...v1.8.0-beta.7
Original source
Curated by the Releasebot team
Releasebot is an aggregator of official product update announcements from hundreds of software vendors and thousands of sources.
Our editorial process involves the manual review and audit of release notes procured with the help of automated systems.