-
Notifications
You must be signed in to change notification settings - Fork 0
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
Classic UI and tests #5
Comments
hi @jensens I have been working on the classicui plugin. I am currently committing plone tune up days to work on it. I think #3 is ready to merge. Any reviews/comments on that PR would be welcome. I updated the description with more information and I'm happy to discuss further if anything doesn't make sense. I also created other issues that I think need resolving before it could be considered production ready. |
@jensens @instification |
i think we need a discussion about the workflow. i agree with the issue #6 . the user should set up all the stuff in a controlpanel. more control over the secret and qr-code generation is needed. |
@jensens @instification @mamico
unclear for me is the workflow, if 2FA enabled globally by admin. if the user didn't scan the qr-code on the first access in the "2fa add form" the he lost the possibility to authenticate on the portal any opinions or hints? |
@1letter +1 for me. After the implementation in Classic UI,I will check the transition of the functionality to the volto counterpart product. If it can be helpful, here keycloak/keycloak#8518 there is a very detailed and discussed use case for handling OTP recovery codes on keycloak. For the last part, if I remember correctly, the user has the qrcode after login and has to use it before he can be authenticated. But I would have to do a test to be sure |
I am actually offering a customer this plugin for ClassicUI usage. This includes making this production ready.
I would also add tests.
If anyone has similar goals please let me now.
I saw there is already an unfinished branch with PR #3.
The text was updated successfully, but these errors were encountered: