RocketChat / RocketChat/Rocket.Chat
After upgrading to 7.9.1 the TOTP stop working
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 46.1k
- Forks
- 13.9k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 130
Description
Description:
After upgrading to 7.9.1 yesterday, today the TOTP on my Workspace stop working when I arrived to work both my macOS App and browser sessions were logged out and when I tried to log back it was displaying a message saying my TOTP code was wrong. Unfortunately I didn't took a screenshot.
I asked a coworker to reset my TOTP so I could setup it again and right after logging back I went to setup TOTP again and the message in the screenshot appears saying "invalid-totp"
Steps to reproduce:
- Go to 'Account Preferences'
- Click on 'Security'
- Click on 'Two Factor Authentication'
- Click to enable 'Two-factor Authentication via TOTP'
- Try to setup an authenticator app (1Password, MS Authenticator)
Expected behavior:
Setup TOTP with an Authenticator app at my account security preferences
Actual behavior:
What actually happens with SCREENSHOT:
Server Setup Information:
- Version of Rocket.Chat Server: 7.9.1
- License Type: Community
- Number of Users: 800
- Operating System: Ubuntu 22.04.5 LTS
- Deployment Method:
- Number of Running Instances: 1
- DB Replicaset Oplog: Yes
- NodeJS Version: v22.16.0
- MongoDB Version: 6.0.25 / wiredTiger (oplog Enabled)
Client Setup Information
- Desktop App or Browser Version: macOS Desktop version 4.8.1 and Chrome 138.0.7204.184
- Operating System: macOS
Additional context
My active logged sessions on Desktop App and Chrome were logged except my phone app (iOS) but I couldn't change the security preferences or disable the TOTP settings.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start in Account Preferences > Security > Two Factor Authentication and reproduce the invalid-totp result with an authenticator app. The payload names no source files or tests, so trace the TOTP setup flow from that entry point; done means setup succeeds and valid codes are accepted after upgrading to 7.9.1.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- authentication, security
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 32/100