Skip to main content
Applies to: authentication changes in the 5.4 release line, including fixes first shipped in 5.4.1. Back to the 5.4 checklist. These actions apply to configured SSO/MCP integrations. Use the latest 5.4 patch, including the Microsoft authority fixes first shipped in 5.4.1.

Before

Better Auth 1.7 updates account identity and OAuth resource handling, including GHSA-p2fr-6hmx-4528. Backfills run automatically. Set WEBAPP_URL for existing MCP OAuth clients and preserve auth/encryption secrets and signing keys. The nullable jwks.alg / jwks.crv additions preserve existing keys; migrations must finish before new keys are minted.

Microsoft Entra tenants

organizations still restricts sign-in to work/school accounts. For a Microsoft authority configured through generic OIDC, prefer the dedicated Azure AD provider, but rehearse existing-account linking before changing providers.

Keep the existing callback

Callbacks introduced in 5.2 remain pinned; the authentication-library update does not move them. When crossing from 5.1 or earlier, first apply the 5.2 callback change. In 5.4, prefix the path with your configured auth origin: BETTER_AUTH_URL, otherwise NEXTAUTH_URL, otherwise WEBAPP_URL. That last fallback is historical: 6.1 requires an explicit auth URL. If an extra callback was registered in anticipation of a change, Formbricks does not use it; keeping it registered does not require changing the app.

Generic OIDC and issuer_missing

The older unconditional requirement for an RFC 9207 iss response parameter is removed. The issuer is still checked when returned. OIDC_EMAIL_CLAIM is not a supported override and does not resolve this error. Test your actual provider’s existing-user sign-in. See the 5.4.7 provider configuration.

MCP token lifetime

  • Access tokens become inactive when their authorizing session ends or is revoked, even before token expiry.
  • Custom clients that cache tokens across sessions must obtain a fresh token after rejection. /introspect reports active: false; /api/auth/oauth2/userinfo rejects the expired session’s token.
  • Refresh tokens granted offline_access can survive sign-out. Signing out alone does not permanently revoke a client.

During

Follow the 5.4 maintenance checklist. Let account-identity and OAuth-resource migrations finish before starting the target application.

After

Test existing password users, each SSO provider, 2FA and an existing MCP client. Verify account linking and that a client recovers after an access token becomes inactive. Do not accept only a successful new-user sign-up.

Recovery

The application additions are compatible with 5.3’s schema usage, but this does not prove Hub/dependency rollback safety. Callbacks stay the same between 5.3 and 5.4. Accounts created after rolling back to 5.3 can lack Account.issuer; complete the issuer repair before rolling forward again. Keep coordinated backups and matching images.