docs: Update Token Authentication sections to explain how to properly… #648
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.
… disable it
Background (can be skipped)
Just as an FYI for anyone who might be looking for this exact issue.
I was using
drf-spectacular
together withdj-rest-auth
and was getting a constant error:The problem was that I was not using Token Authentication but rather Session Authentication, and thus, following the docs, I set
TOKEN_MODEL
toNone
.The problem comes when the
TokenSerializer
is still active, and tries to get theToken
model, which is overridden by theTOKEN_MODEL
setting. This causes the error above.Fix
To properly disable Token Authentication, the
TOKEN_SERIALIZER
setting should also be set toNone
, together withTOKEN_MODEL
.I've added a couple of notes under
TOKEN_SERIALIZER
andTOKEN_MODEL
specifying that both need to be set toNone
in order to fully disable the Token Authentication functionality.