Skip to content
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

Open
jensens opened this issue Feb 12, 2024 · 5 comments
Open

Classic UI and tests #5

jensens opened this issue Feb 12, 2024 · 5 comments
Labels
enhancement New feature or request

Comments

@jensens
Copy link
Member

jensens commented Feb 12, 2024

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.

@jensens jensens added the enhancement New feature or request label Feb 12, 2024
@instification
Copy link
Member

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.

@1letter
Copy link
Contributor

1letter commented May 5, 2024

@jensens @instification
i work currently on a refactoring for Plone 6. See my PR Draft. I replace the qr-code with an inline base64 image, it's not created by googlechart. i will work on tests for better test coverage. i have also refactor the package with plone/meta and use pip based installation with mx.ini.

@1letter
Copy link
Contributor

1letter commented May 10, 2024

@jensens @instification

  • short Intermediate status: code coverage 89%
  • fix a bug in rest api endpoint for login
  • fix a bug in rest api endpoint for userpatch

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.

@1letter
Copy link
Contributor

1letter commented May 21, 2024

@jensens @instification @mamico
Do you have a need or interest in expanding the package? My ideas would be:

  • extends the account panel with a new tab "2FA", only available/visible if 2FA is active
  • recovery options for 2FA with a list of 10 digit keys like pypi/github
  • the tab contain the qr-code for configuration the totp app
  • the tab contain the list of recovery keys
  • the recovery keys are implemented as a annotation of user object
  • e-mail notification if access happen to recovery keys

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?

@mamico
Copy link
Collaborator

mamico commented May 22, 2024

@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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request
Projects
None yet
Development

No branches or pull requests

4 participants