Use of old authentication token leads to Registration page instead of existing content

[vincgj]

Description:

Using an old auth token
Trying to restore a mongodb dump then accessing the interface led to the Registration page instead of existing content.

Steps to reproduce:

1. have an old token (not easily reproducible)
2. restore a RC mongodb backup/dump
3. access the UI

Expected behavior:

Show "normal" content of the instance

Actual behavior:

• Show / stuck on the Registration page
• Even if from filled, cannot go to step 2

Server Setup Information:

• Version of Rocket.Chat Server: 7.13.2
• License Type: CE
• Number of Users: 50
• Operating System: ubuntu lts
• Deployment Method: docker
• Number of Running Instances: 1
• DB Replicaset Oplog: Enabled
• NodeJS Version: 22.16.0 - x64
• MongoDB Version: 6.0.27

Client Setup Information

• Desktop App or Browser Version: Firefox 147.0.2 (64 bits) / Chromium 144.0.7559.109
• Operating System: NixOS

Additional context

Instance is "public" : no need to login to see content

Authentication / account is still required for posting or admin roles

Relevant logs:

nothing relevant in logs, startup as usual

[vincgj]

Cause: issue with existing / old auth token in local browser

Resolution: Clear the cache of your browser to start a new auth from scratch

[vincgj]

Created issue if the team have an automated way to invalidate remote cache or make RC available to authenticated users.

[jaiswalism]

Hi @vincgj, thanks for the clarification, that helps.

Since clearing cache resolves it, this looks like a stale client auth token not being invalidated on startup, leading to a redirect to registration instead of login.

I’ll try reproducing this locally and work on clearing invalid tokens and redirecting to login. Happy to adjust if maintainers expect different behavior.