RocketChat / RocketChat/EmbeddedChat

EmbeddedChat Not Workingwith DMs and Private Channels

Open
#1,031 1 comment 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

bug
Dominant language
JavaScript
Stars
165
Forks
381
Avg merge
1d 2h
Merged PRs (30d)
1

Description

EmbeddedChat component fails to function properly when attempting to connect to Direct Messages (DMs) and Private Channels in Rocket.Chat. The component works correctly with public channels but encounters issues with private room types.

Environment
Rocket.Chat Server: localhost:3102
User: xxxx (ID: NxQupzo5KTHwkCgAX)
Auth Token: Valid and verified
Room Type: Private Channels / Direct Messages
Example Room ID: 69321c45a340bdc91ea303cb
Current Behavior
When attempting to use EmbeddedChat with private channels or DMs:

The component fails to load the chat interface properly
Authentication appears to succeed (valid token and user ID)
Room access is denied despite valid credentials
Expected Behavior
EmbeddedChat should work seamlessly with:

✅ Public channels
❌ Private channels
❌ Direct Messages (DMs)
Technical Details
Authentication Data
json
{
"userId": "NxQupzo5KTHwkCgAX",
"authToken": "mYu1uNr49meFT28nd7Dia70OJj6fg1YUu6NDPyyiI2C",
"username": "xxx",
"roles": ["user"],
"status": "online"
}
API Request Example
bash
curl 'http://localhost:3102/api/v1/channels.members?roomId=69321c45a340bdc91ea303cb'
-H 'X-Auth-Token: mYu1uNr49meFT28nd7Dia70OJj6fg1YUu6NDPyyiI2C'
-H 'X-User-Id: NxQupzo5KTHwkCgAX'
Steps to Reproduce
Initialize EmbeddedChat with valid auth credentials
Attempt to connect to a private channel or DM using room ID
Observe that the chat interface fails to load or shows permission errors
Compare with public channel behavior (works correctly)
Additional Context
This issue is blocking the implementation of a complete chat solution that requires support for private conversations and direct messaging functionality.

Contributor guide

No contributing guide indexed for this repository

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 failure in the EmbeddedChat component with the provided private-channel and DM room IDs, then compare its behavior with a public channel and inspect the shown channels.members API request. Done means authenticated users can load the chat interface and access permitted private channels and direct messages without permission errors.

Written by the indexing model from the issue text.

Assessment

Tech stack
javascript, react
Domain
api, frontend
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.