RocketChat / RocketChat/Rocket.Chat

Changing username in LDAP results in new user

Open
#11,413 2 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

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

Description

Hoi,
Our Rocket chat instance uses LDAP to connect to a central user directory. Changing a users username results in a new user being created in rocket chat within the next sync.

As I'm not an LDAP expert myself, I have to guess that the username is used as the unique identifier per default.

Steps to reproduce:
  1. Create a user in LDAP directory
  2. Sync to Rocket.Chat
  3. Change username in directory
  4. Sync again
Server Setup Information:
  • Version of Rocket.Chat Server: 0.66.0
Additional Info

Just for clarification on why usernames may be changed: our usernames consist of firstname.lastname. Once someone get married, they may change their lastname as well as their username.

Bonus: The same exact issue was fixed by Atlassian (confluence, jira..) some years ago.

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 file or test is named in the issue. Start by tracing the LDAP synchronization path and how it matches directory users to Rocket.Chat users; reproduce the four listed sync steps and confirm that changing an LDAP username updates the existing Rocket.Chat user instead of creating another one.

Written by the indexing model from the issue text.

Assessment

Tech stack
typescript
Domain
authentication, backend
Issue type
Bug
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
35/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.