Support for specifying client secret hasher #1498
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
matejsp
force-pushed
the
settings-for-password-hasher
branch
from
033e56d to
e6b5779
Compare
n2ygk
force-pushed
the
settings-for-password-hasher
branch
from
e6b5779 to
633da22
Compare
n2ygk
requested changes
Sep 20, 2024
matejsp
force-pushed
the
settings-for-password-hasher
branch
from
9436528 to
f02342b
Compare
n2ygk
approved these changes
Sep 22, 2024
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 every Django version PBKDF2 password hasher gets iterations increased and the next one will be set to 1 mio.
This poses a problem in our case because it affects the performance of /token endpoint. We whitelist to the IPs from which endpoint is accessible so we want to use weaker algorithm. For normal UI login we still want to retain default one.
Description of the Change
Added a setting for specifying client server hasher using CLIENT_SECRET_HASHER.
Checklist
CHANGELOG.mdupdated (only for user relevant changes)AUTHORS