[bug] Authentication endpoint may return expired token #10233
Merged
+26
−26
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR fixes issue #10228.
PUI login via the
/api/auth/login
endpoint is handeled by a (modified) dj_rest_authLoginView
, which uses the TOKEN_CREATOR to get the token to return. The configured token creatorusers.models.create_token_expiry()
doesn't account for expired tokens and returns the first matching token for the user, even if it may be expired.In contrast, the
users.api.GetAuthToken()
view handles this correctly and creates a new token for authenticated users if no vaild token exists.This is fixed by consolidating the logic for retrieving or creating an
ApiToken
into a single classmethod.