Reset CSRF token to null when logging out from a server #4
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.
With the current state of the extension, the CRSF token acquired on the first invocation to authenticate is not cleared on logout and thus is getting reused by follow-up authentication calls resulting in CSRF errors.
To reproduce the issue
django.security.csrf
WARNING of typelog_response():241 Forbidden (CSRF cookie not set.): /api/v0/login/
With these changes included in the extension, the workflow above should be sueccessful
/cc @stick @muhanadz