This repository was archived by the owner on May 26, 2020. It is now read-only.
Use get_by_natural_key in jwt_get_secret_key #418
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.
As stated in commit
a3b4d44d2fc34d7752793ccbade2684707bf41da, the fielduser_idin payload will be deprecated.Instead of explicitly using
user_idfield to retrieve user inutils.jwt_get_secret_keyfunction, we should useUser.objects.get_by_natural_keywith the value in the payload dictionary atusername_fieldkey.