RocketChat / RocketChat/Rocket.Chat
Persistent User login issues
Open
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 46.1k
- Forks
- 13.9k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 130
Description
Description:
My users are finding that their user ids and passwords are getting rejected at a suspiciously high rate. While I expect users to mess up their authentication periodically, we're seeing many users, even those using password managers, getting locked out of Rocket.chat with messages that their authentication has failed. They've experience this in the browser, as well as the mobile apps.Steps to reproduce:
- go to the login page
- Enter user id and password
- Observe that failure message is presented.
Expected behavior:
Authentication, and proceeding...
Actual behavior:
Rejection of credentials.
Server Setup Information:
Firewalls involved: none
- Version of Rocket.Chat Server: 5.0.3
- Operating System: Ubuntu 20.04
- Deployment Method: Digital Ocean One-Click install
- Number of Running Instances: 1
- DB Replicaset Oplog: Enabled
- NodeJS Version: 14.19.3 -x64
- MongoDB Version: wiredTiger
Client Setup Information
- Browser Version: All
- Operating System: Windows/ IOS
Additional context
Relevant logs:
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
No source file or test is named. Start by reproducing the login failure from the listed login steps and inspect the attached Rocket.Chat server logs, comparing browser and mobile behavior on the reported setup. Done means valid credentials authenticate reliably without the reported rejection.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- mongodb, node.js, typescript
- Domain
- authentication, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100