RocketChat / RocketChat/Rocket.Chat

[BUG] The room list from the old user is still displayed when logging in to a new account on the same browser.

Open
#25,973 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Dominant language
TypeScript
Stars
46.1k
Forks
13.9k
Avg merge
3d 3h
Merged PRs (30d)
130

Description

Description:

The room list from the old user is still displayed when logging in to a new account on the same browser.

Steps to reproduce:
  1. Login account A on the browser
  2. Register any account in an incognito browser
  3. Access the newly created account verification email in the same browser that A is logging in
  4. Click on email verification and check the room list of 2 accounts
Expected behavior:

Clear cache of user A

Actual behavior:

Account A's previous login has changed to B, but A's room list is still displayed along with B's room list.

https://user-images.githubusercontent.com/35986099/175198963-48d0b92e-4635-45da-88cc-bbeca2d2c2cf.mp4

image

Server Setup Information:
  • Version of Rocket.Chat Server: 4.6.3 (due for an upgrade soon)
  • Operating System: Ubuntu
  • Deployment Method: snap
  • Number of Running Instances: 1
  • DB Replicaset Oplog: Enabled
  • NodeJS Version: 14.18.3
  • MongoDB Version: 5.0.6
Client Setup Information
  • Desktop App or Browser Version: Chrome 102.0.5005.115 (Official Build) (64-bit), Firefox Version 101.0.1 (64-bit)
  • Operating System: Ubuntu 20.04.4 LTS 64-bit
Additional context
Relevant logs:

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reproducing the account-switching flow in a browser using the listed steps and verify which room lists remain after account B is verified. No files or tests are named, so trace the client-side session and room-list behavior; done means account A's rooms are no longer displayed after switching to B.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
authentication, frontend
Issue type
Bug
Difficulty
4/5
Estimated time
3-5 days
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.