django-allauth 65.22.0 released
Posted by Raymond Penners on 2026-11-11
Note worthy changes
- Reauthentication is now possible using a login code sent to a verified email address or phone number.
- The available reauthentication methods can now be configured using ACCOUNT_REAUTHENTICATION_METHODS.
- There is a new setting ACCOUNT_SIGNUP_ENABLED (default: True) to enable or disable signup.
- New provider: Recharge.
- IdP: Authorization codes are now stored in the database instead of the cache.
- Headless: Honor USERSESSIONS_TRACK_ACTIVITY for authenticated app requests, the Django REST framework and Django Ninja integrations, and JWT refreshes. Stateless JWT access token validation continues to skip activity tracking.
- Headless: The Django REST framework and Django Ninja authentication classes can now be configured to allow or reject anonymous users and invalid session tokens.
- Headless: Custom response metadata can now be added using the new populate_response_meta() adapter method.
- Headless: The OpenAPI specification now reflects the authentication schemes of the configured token strategy.
Security notice
- Apple: Identity data from the unsigned callback payload is no longer trusted, preventing forged verified email addresses and account takeover. Thanks to Irregular (@Tomer-PL) for reporting.
- MFA: The recovery code view now prevents HTTP caching of recovery codes.
- IdP: Authorization codes are now redeemed atomically. As per RFC 6749, Section 10.5, reusing a code also revokes access and refresh tokens issued from the same authorization grant.
- IdP: Silent authorization now only considers consent granted to the requesting client.
- IdP: Token revocation is now restricted to tokens issued to the authenticated client. Revoking a refresh token also revokes access tokens issued from the same authorization grant.
- IdP: PKCE now only accepts the advertised S256 challenge method.
- Previously, reauthentication checks were skipped when no reauthentication method was available, for example for social-only accounts without a password. Access is now denied instead.
- Setting a password (e.g. using a social-only account that has no usable password) now requires reauthentication when ACCOUNT_REAUTHENTICATION_REQUIRED is enabled.
- MFA: Fixed a remaining passwordless WebAuthn login path that did not enforce user verification.
- MFA: With a nonzero MFA_TOTP_TOLERANCE, a used TOTP code could briefly be reused within its tolerance window. Thanks to Zachary Satterly for reporting.
Next: django-allauth 65.22.1 released Previous: django-allauth 65.21.1 released