-
Notifications
You must be signed in to change notification settings - Fork 824
Add ClientSecretField field to use Django password hashing algorithms #1020
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Conversation
for more information, see https://pre-commit.ci
…oauth-toolkit into pek-scrypt-client-secret
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #1020 +/- ##
==========================================
+ Coverage 96.67% 96.70% +0.02%
==========================================
Files 31 31
Lines 1775 1791 +16
==========================================
+ Hits 1716 1732 +16
Misses 59 59 ☔ View full report in Codecov by Sentry. |
|
@pkarman sorry for the review delay. I'm targeting this change for the next minor release. Can you rebase and respond to my review questions? This looks like good stuff. Thanks. |
for more information, see https://pre-commit.ci
…oauth-toolkit into pek-scrypt-client-secret
|
@n2ygk -- no problem. I don't see any review comments? This branch has been merged with upstream. |
n2ygk
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Ah my review comments were pending. I thought I had submitted them.
Please rebase with current master branch as well
|
@n2ygk thanks for the review. I think I've addressed all your comments and rebased with current master. |
n2ygk
left a comment
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Looks good. Thanks for this!
I believe these changes were made but to marked resolved.
…django-oauth#1020) Co-authored-by: Asif Saif Uddin <[email protected]> Co-authored-by: Alan Crosswell <[email protected]>
…django-oauth#1020) Co-authored-by: Alan Crosswell <[email protected]>
* Add ClientSecretField field to use Django password hashing algorithms (#1020) Co-authored-by: Andrew Chen Wang <[email protected]> Co-authored-by: Peter Karman <[email protected]> Co-authored-by: Andrew Chen Wang <[email protected]>
…-oauth#1093) * Add ClientSecretField field to use Django password hashing algorithms (django-oauth#1020) Co-authored-by: Andrew Chen Wang <[email protected]> Co-authored-by: Peter Karman <[email protected]> Co-authored-by: Andrew Chen Wang <[email protected]>
Fixes #729
Description of the Change
The
client_secretis effectively not a secret if stored as plaintext. This becomes a security risk if a database is compromised, especially for 2-legged OAuth2 (client credentials flow) where there is no other mitigating credential to be used in authentication.NOTE that this preserves the existing behavior of not hashing
client_secretby default. To enable it, it must be explicitly set. In theory this should provide backwards compatibility with existing installations.Checklist
CHANGELOG.mdupdated (only for user relevant changes)AUTHORS