RocketChat / RocketChat/Rocket.Chat

users not getting e2e keys but admin does

Open
#30,389 3 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:

I deployed a docker container with rocket.chat locally
As the admin i enabled e2e and got my key, well and good.
However, my users never got the pop up to get the e2e key yet in the settings its as if they already have gotten it and their only option is reset e2e key, yet when they do it does nothing somehow.

Steps to reproduce:
  1. enable e2e and login as user on a deployed docker container
  2. account settings > e2e settings > e2e will be enabled yet you did not get your key
  3. e2e and otr will be unavailable
Expected behavior:

e2e key given and otr working

Actual behavior:

otr causes many errors regarding e2e key being missing and e2e simply not working as intended

Server Setup Information:
  • Version of Rocket.Chat Server: latest
  • Operating System: Windows 11 pro
  • Deployment Method: Docker
  • Number of Running Instances: 1
  • NodeJS Version: latest
  • MongoDB Version: latest
Client Setup Information
  • Desktop App or Browser Version: Opera GX
  • Operating System: Windows 10 Pro
Additional context
Relevant logs:

no 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

Reproduce the issue in the Docker deployment by enabling E2E as an admin, then checking a regular user's Account Settings > E2E settings. Compare the admin and user flows and capture the browser and server errors around the missing key and OTR failure. Done means users receive or can successfully reset their E2E key and OTR works.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.