Version history for every DjangoPlay app — pick one to see what changed and when. Looking for what’s coming next? Explore the latest roadmap and upcoming releases?
A complete authentication flow and persistent identity layer — with credential login, refresh-token rotation, authenticated UserInfo, and a production database schema — now shipped with reliable, package-included migrations.
AuthXClient can now authenticate users with email/password credentials, refresh access tokens, and retrieve authenticated identity information.
refresh tokens are managed through a dedicated /token/refresh flow, with explicit handling for invalid or revoked credentials.
TokenData provides a consistent representation of access and refresh token responses for consuming applications.
invalid credentials and invalid or revoked refresh tokens are represented through AuthXInvalidCredentialsError, giving applications a clear failure boundary.
introduces the user_identity and refresh_token tables, with UUID identity, credentials, SSO relationships, lifecycle state, verification status, login tracking, token expiration, and revocation state.
identity, email, username, SSO identity, and refresh-token lookup paths receive appropriate indexes and uniqueness constraints.
supports both bcrypt_sha256 and bcrypt, retaining compatibility while enabling stronger password hashing for new credentials.
service authentication is explicitly configured through AUTHX_SERVICE_TOKEN, while JWT issuer and audience values are deployment-specific rather than silently inherited from DjangoPlay.
PEM key normalization handles environment-provided values more reliably, including escaped newline sequences.
authentication failures and inactive identities receive explicit, predictable responses across the service and client layers.
Alembic migrations now live inside authx/migrations/, ensuring the schema definitions are included in the published PyPI distribution.
the new authx-migrate command provides upgrade, current, and history operations without requiring consumers to clone the AuthX source repository.
local development and published deployments now use the same migration files, reducing the risk of schema drift between development and installed packages.
consuming applications can apply the AuthX identity and refresh-token schema directly from the installed package.
database migration becomes part of the normal package installation and deployment workflow rather than depending on repository-level Alembic files.