-
-
Notifications
You must be signed in to change notification settings - Fork 794
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
Run hasher migration on swapped models #1147
Conversation
Codecov Report
@@ Coverage Diff @@
## master #1147 +/- ##
=======================================
Coverage 96.90% 96.90%
=======================================
Files 31 31
Lines 1812 1812
=======================================
Hits 1756 1756
Misses 56 56 Continue to review full report at Codecov.
|
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.
What do you think about making the migration work correctly for swapped models?
oauth2_provider/migrations/0006_alter_application_client_secret.py
Outdated
Show resolved
Hide resolved
@n2ygk Updated per #1146 (comment). Additionally used |
@josephabrahams sorry I went and rebased while you were working on it. I'll step away until you mark this as ready for review. |
e6da5e6
to
f1210ef
Compare
@n2ygk No worries! I rebased and took a stab at a test. Please let me know what you think. |
f1210ef
to
f1f8293
Compare
* Add ClientSecretField field to use Django password hashing algorithms (#1020) Co-authored-by: Andrew Chen Wang <60190294+Andrew-Chen-Wang@users.noreply.github.com> Co-authored-by: Peter Karman <pkarman@users.noreply.github.com> Co-authored-by: Andrew Chen Wang <60190294+Andrew-Chen-Wang@users.noreply.github.com>
Fixes #1146
Description of the Change
Run client secret hasher migration on custom application model.
Checklist
CHANGELOG.md
updated (only for user relevant changes)AUTHORS