RocketChat / RocketChat/Rocket.Chat

initial verification link should be invalidated or expired.

Open
#31,534 1 comment 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 user is initially sent a verification email, and if they choose to resend the verification email, the first link becomes invalid, and a new email with a new verification link is sent to the user. This ensures that only the most recent verification link is valid for completing the registration process.

Steps to reproduce:
  1. When the user requests to resend the verification email, generate a new unique token and update the expiry time.

  2. Invalidate the previous token associated with the user.

Expected behavior:

first link becomes invalid, and a new email with a new verification link is sent to the user

Actual behavior:

both link are valid

Server Setup Information:
  • Version of Rocket.Chat Server:
  • Operating System:
  • Deployment Method:
  • Number of Running Instances:
  • DB Replicaset Oplog:
  • NodeJS Version:
  • MongoDB Version:
Client Setup Information
  • Brave:
  • Window 10:
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

No files, tests, or entry points are named. Trace the resend-verification flow from the issue description, then verify that resending creates a new token and expiry, invalidates the previous token, and leaves only the newest link usable.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
authentication, backend
Issue type
Bug
Difficulty
3/5
Estimated time
1-2 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.