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

"Users must use Two Factor Authentication" setting does not work #27592

Open
roshanrags opened this issue Dec 21, 2022 · 3 comments
Open

"Users must use Two Factor Authentication" setting does not work #27592

roshanrags opened this issue Dec 21, 2022 · 3 comments

Comments

@roshanrags
Copy link

Description:

As in the title, "Users must use Two Factor Authentication" setting does not work.

Steps to reproduce:

  1. Enabled "Users must use Two Factor Authentication" setting on the "user" role.
  2. Created new user with "user" role.
  3. Able to log in with the new user and do everything without setting up 2FA.
  4. Nothing is enforced.

Expected behavior:

  1. Server disallows any action till 2FA is set up.
  2. When user logs in or refreshes the page, some 2FA related setup flow pops up.

Actual behavior:

Nothing, user can do everything without ever setting up 2FA,

Server Setup Information:

  • Version of Rocket.Chat Server: 5.4.0
  • Operating System: ubuntu 22.04
  • Deployment Method: manual
  • Number of Running Instances: 1
  • DB Replicaset Oplog: enabled
  • NodeJS Version: 14.21.2
  • MongoDB Version: 6.0.3

Client Setup Information

Not sure what this means, accessing from browser.

Relevant logs:

Few other issues mention error logs in browser or server, but no error logs seen in this case.

@debdutdeb
Copy link
Member

Cannot reproduce onlatest develop.

@roshanrags
Copy link
Author

Upgraded to 5.4.2, issue is still there. Let me know what I can do to help debug.

@ulope
Copy link

ulope commented Apr 12, 2023

And now it doesn't even matter anymore since versions >6.0 have removed the option to edit roles in the non enterprise version (see #27481, /edit: fixed issue link).

This constant breaking of stuff is so incredibly tiring.
We're seriously tempted to suffer the pain of moving to a different chat solution just to not have to deal with this slapdash seat of the pants development model anymore.

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

No branches or pull requests

3 participants