-
Notifications
You must be signed in to change notification settings - Fork 26
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
Replace 2fa solution #3844
Replace 2fa solution #3844
Conversation
Codecov ReportAll modified and coverable lines are covered by tests ✅
Additional details and impacted files@@ Coverage Diff @@
## master #3844 +/- ##
==========================================
+ Coverage 96.31% 96.33% +0.01%
==========================================
Files 707 707
Lines 22172 22162 -10
Branches 2542 2540 -2
==========================================
- Hits 21356 21349 -7
+ Misses 569 567 -2
+ Partials 247 246 -1 ☔ View full report in Codecov by Sentry. |
fe0b03b
to
9145c8a
Compare
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.
Tested locally as well and works as expected.
Only one question below and I searched for TWO_FACTOR_PATCH_ADMIN
which is/was used in a lot of places and I am wondering if it's everywhere properly documented (for example in config.rst
and in the docker-compose.yml
)
""" | ||
1. Remove any dummy OTP devices for the hijacked user. | ||
2. Restore the original OTP device for the hijacker. | ||
Add an audit trail entry for the hijack action. |
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.
This is done on purpose right?I mean we want to have the same text in both functions
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.
Yep!
maykin_2fa has the signal handling to manage the TOTP device now, so all OF needs to do is add the audit logging.
Also addresses part of #3695 * Drop the maykin-django-two-factor-auth dependency - it is replaced with the upstream package through maykin-2fa * Drop phonenumbers, instead phonenumberslite is enforced by maykin-2fa
The signals to manage devices are implemented in maykin-2fa directly, we only need to take care of the audit logging here.
Added the new webauthndevice model.
d664413
to
dff6ddb
Compare
There were some more references left, so I've updated those files and the docs. Thanks for spotting this! |
* dev-settings coverage is not relevant * admin-index menu check is obsolete due to the hidden navbar at the template level
Partly closes #3049
Partly closes #3695
TODO: