RocketChat / RocketChat/Rocket.Chat
User logouts
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 46.1k
- Forks
- 13.9k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 130
Description
Description:
When using the users.update api endpoint we keep the users password updated with our main userbase system. In 99% of cases this is just setting the password to exactly what it is, the main idea is to keep it in sync across both platforms. However when we use this update the users are logged out of the app.
Steps to reproduce:
- Login to app
- Use the users.update api to set the users password to exacrly the same password
- Go into the app, go to settings then clear server cache.
- Once refreshed the user is then logged out.
Expected behavior:
User to remain logged in
Actual behavior:
User is logged out and recieves and Oops, you have been logged out of the server please log in again messaage
Server Setup Information:
- Version of Rocket.Chat Server: 3.7
- Operating System: ubuntu 20.04
- Deployment Method: manual
- Number of Running Instances: 1
- DB Replicaset Oplog:
- NodeJS Version: v12.14.0
- MongoDB Version:4.0.20
Client Setup Information
- Desktop App or Browser Version: normal app and experimental app
- Operating System: android and 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
Start by reproducing the issue through the users.update API endpoint, using the listed server and client setup, then clear the server cache as described. Trace the logout behavior after setting an unchanged password; done means the user remains logged in and no logout message appears.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- api, authentication, backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100