Drop django-two-factor-auth and migrate 2FA pages to new frontend #3520
No reviewers
Labels
No labels
Security
TeX
auto-update
board
done
board
ready
board
todo
check
delete-eslint-rc-js
check
update-builddeps-package-json
check
update-eslint-rc-js
check
update-gitignore
check
update-merge-request-template
check
update-prettier-ignore
check
update-pyproject-toml
check
update-renovate-json
check
update-tox-ini
part
backend
part
ci
part
docs
part
frontend
part
i18n
part
non-technical
part
packaging
prio
1
prio
2
prio
3
release-mr-5.x
size
large
size
medium
size
small
source
customer
source
customer::fsmw
source
customer::fss
source
customer::teckids
source
downstream
type
breaking
type
bug
type
feature
type
refactoring
workflow
blocked
workflow
confirmed
workflow
current-todo
workflow
discussing
workflow
new-app
workflow
wontfix
No milestone
No project
No assignees
4 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
aleksis/AlekSIS-Core!3520
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
Delete branch "drop-django-two-factor-auth"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
added 1 commit
Compare with previous version
mentioned in issue #565
mentioned in issue #1160
mentioned in issue #1207
mentioned in issue #438
changed the description
added 1 commit
Compare with previous version
added 1 commit
Compare with previous version
requested review from @ZugBahnHof
added 2 commits
Compare with previous version
marked this merge request as ready
Migration path?
No need to instantiate two dicts.
I don't think this helps.
I agree ;-)
I thought we actually use named routes instead of hardcoding paths so the route can change without needing to update all code locations?
undeclared event
undeclared event
why does a dialog action trigger a redirect?
why change this?
what are all of these django templates for?
requested changes
Yeah, that's a named route. I just changed the name for consistency with the other names.
Ah, should be probably
this.dialog = falseinstead.Because that's django-two-factor-auth's URL scheme and not django-allauth's URL scheme.
To make django-allauth showing things in Materialize ...
Reminds me: Drop old login templates
Recovery code status is shown as "(not) activated", should probably instead be "(not) generated". Also, the regeneration is a destructive (→ dangerous) action, button should be red.
don't like this icon here
Due to only one 2fa authenticator app at a time being supported (afaik), the button to add/remove it implicitly tells the status, so the chip is unnecessary.
Maybe this can be combined with the button? Idea: clicking the chip does the same as clicking the button
I like a clear, visible, and consistent indicator for each method, so I don't think the chip is unnecessary.
Do you have a better idea?
Same argument with the consistency → recovery codes are a 2fa method and it can be activated or not
Security keys cannot be deactivated/disabled but only added/removed, so the chip should either say "{None|One|n} keys added" or maybe even contain a button like this:
hm, ok i guess
maybe a store update is required as well
but can't our frontend be backend-2fa-lib-agnostic?
they cannot be not activated tho? If they exist they are automatically active, right?
May just the trashcan or something like cellphone-remove?
I like the idea of a clear indicator per method, but I think right now they
No, the URL scheme is not a frontend decision. This URL had to change anyway because the
accountscheme is not used.Yeah, so they are activated.
change this icon
@hansegucker an idea for this page, what do you think?
It's missing all the consistency I liked ...
I see your point, maybe we can discuss/find a compromise? (maybe in the devmeeting or a call or sth?)
yes, but they will never be "not activated". either they exist or they don't. Simplify change the wording…
added 1 commit
Compare with previous version
changed this line in version 7 of the diff
changed this line in version 7 of the diff
changed this line in version 7 of the diff
changed this line in version 7 of the diff
added 1 commit
Compare with previous version
@ZugBahnHof
added 1 commit
Compare with previous version
For the codes please add smth like "codes are created in batches of 10", and maybe change the chip text to "... codes remaining"?
changed this line in version 9 of the diff
added 4 commits
Compare with previous version
marked this merge request as draft from 9acf90f96a9505e19ce93a5692f1c7670ef5eeda
added 55 commits
masterf0eb529d- Add support for allauth webauthn to frontend529d5354- Drop old 2fa frontendaaaad844- Refactor new 2fa page37a3471f- Update docs for 2fa0525ca40- Drop old templates01fddce4- Fix things from review17fe06f0- Optimize frontend for 2FAfa602e22- Fix messages for 2FAa9e9b8db- Update changelogCompare with previous version
resolved all threads
marked this merge request as ready
@hansegucker please add a new screenshot
There is no need for a new screenshot, only some texts were updated.
added 1 commit
Compare with previous version
added 1 commit
Compare with previous version
added 1 commit
4d07e0d3- Finally drop 2FACompare with previous version
resolved all threads
mentioned in commit
748bf6438d