Release Notes¶

Version 1.2.3¶

Released: January 25, 2026

Projects generated via jwt-allauth startproject now configure Django’s MIGRATION_MODULES so that jwt_allauth migrations are stored inside the project codebase (under <project_module>/migrations_external/jwt_allauth). This improves reliability in Docker/containerized deployments where site-packages is ephemeral.

Updated installation documentation to explain how to configure MIGRATION_MODULES manually in existing projects to persist jwt_allauth migrations in version control.

Released: December 24, 2025

Admin-Managed Registration: The email confirmation link in the admin-managed registration flow is no longer single-use. It remains valid until the user successfully sets their password. This prevents issues with email security scanners (like Outlook Safe Links) consuming the token before the user can access it. The token is now automatically deleted upon successful password completion.
Configurable Verification Error Page: When an invalid or expired email verification link is accessed in the admin-managed flow, a user-friendly HTML error page is now shown instead of a 400/401 API error. This template can be customized via the EMAIL_VERIFICATION_FAILED_TEMPLATE key in JWT_ALLAUTH_TEMPLATES setting.

Released: November 29, 2025

Minor fix: resolved MFA TOTP failures in production deployments with multiple workers or threads by removing dependency on default cache backend.

MFA TOTP challenges and setup secrets are now stored server-side in the existing GenericTokenModel database table instead of Django’s default cache backend. This improves reliability in multi-worker environments without changing the public API or required settings.

Updated supported Python versions to 3.10+ (dropped 3.8 and 3.9).
Extended the mfa extra to include fido2<2.0.0 for broader hardware key support.
Fixed Quick Start documentation and CI smoke test to run python manage.py makemigrations jwt_allauth before migrate in projects generated via jwt-allauth startproject, avoiding migration errors involving the JAUser model.

Released: November 17, 2025

MFA TOTP: Added REST endpoints for TOTP-based multi-factor authentication using django-allauth MFA:
- POST /mfa/setup/: returns provisioning URI (otpauth), secret, and QR code (SVG)
- POST /mfa/activate/: activates TOTP and returns recovery codes
- POST /mfa/verify/: completes login when MFA is required
- POST /mfa/verify-recovery/: completes login using one-time recovery codes
- POST /mfa/deactivate/: disables TOTP for the current user
- GET /mfa/authenticators/: lists user authenticators
Requires enabling allauth.mfa in your project INSTALLED_APPS and running migrations. Configurable via JWT_ALLAUTH_MFA_TOTP_MODE setting with three modes:
'disabled' (default): MFA TOTP is disabled

'optional': Users can enable MFA TOTP but it’s not required for login

'required': Users must enable MFA TOTP and provide TOTP code during login
Admin-Managed User Registration: New registration flow controlled via JWT_ALLAUTH_ADMIN_MANAGED_REGISTRATION setting. When enabled:
- Self-registration endpoint is disabled
- Only users with allowed roles (configurable via JWT_ALLAUTH_REGISTRATION_ALLOWED_ROLES) can register new users
- New /user-register/ endpoint for admin registration
- Invited users set their own password via email verification link before gaining access
- No authentication tokens issued during registration; one-time password setup token issued after email verification

Released: October 11, 2025

JWT_ALLAUTH_USER_ATTRIBUTES now expects a dictionary mapping output claim names to user attribute paths (e.g., {"organization_id": "organization.id"}) instead of a list of paths. This change prevents duplicate final attribute names (e.g., multiple id keys) in JWT payloads. The previous list format is still accepted for backward compatibility, but it is deprecated and may be removed in a future release.

Released: October 7, 2025

Added support for including additional user attributes in refresh tokens via the JWT_ALLAUTH_USER_ATTRIBUTES setting, allowing flexible configuration of user data included in JWT payloads while maintaining the existing role assignment logic.

Fixed API endpoints that incorrectly required refresh token in request payload when JWT_ALLAUTH_REFRESH_TOKEN_AS_COOKIE was enabled, now properly extracting refresh tokens from cookies when configured.
Fixed a bug that caused migrations not to run correctly in some situations.

Released: August 5, 2025

New load_user() decorator that loads the complete user object from the database for stateless JWT authentication.
Added JWT_ALLAUTH_COLLECT_USER_AGENT setting to control user agent data collection during token refresh.
Added support for refresh tokens via HTTP cookies with the new JWT_ALLAUTH_REFRESH_TOKEN_AS_COOKIE setting.
Enhanced token refresh security by moving user agent data collection from request payload to server-side context.
Compatibility with django-allauth 65.10.0, djangorestframework-simplejwt 5.5.1, and djangorestframework 3.16.0.

Released: April 16, 2025

This release introduces significant improvements to the role management system and authentication configuration.

Added automatic role assignment in UserManager:
- create_superuser now automatically sets the role to STAFF_CODE
- create_user automatically assigns roles based on user flags:
  
  STAFF_CODE for staff users
  
  SUPER_USER_CODE for superusers
Added database constraints to ensure role consistency:
- Staff users must have STAFF_CODE role
- Superusers must have SUPER_USER_CODE role

Automatic configuration of DEFAULT_AUTHENTICATION_CLASSES was not working when using addiotional REST_FRAMEWORK settings.