RocketChat / RocketChat/Rocket.Chat
LDAP sync (Email already exists)
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 46.1k
- Forks
- 13.9k
- Avg merge
- 3d 3h
- Merged PRs (30d)
- 130
Description
Your Rocket.Chat version: 0.40
Unable to merge with existing user using LDAP sync.
[34mI20160928-12:35:51.781(5.5) rocketchat:ldap sync.js:184 [31mLDAPSync ➔ error Error creating user { [Error: Email already exists. [403]] error: 403, reason: 'Email already exists.', details: undefined, message: 'Email already exists. [403]', errorType: 'Meteor.Error' }
[34mI20160928-12:35:51.783(5.5) rocketchat:ldap sync.js:249 [31mLDAPSync ➔ error { [Error: Email already exists. [403]] error: 403, reason: 'Email already exists.', details: undefined, message: 'Email already exists. [403]', errorType: 'Meteor.Error' }
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reading sync.js around lines 184 and 249 and trace the LDAP sync path that attempts user creation when an email already exists. Reproduce the failure with the issue's LDAP scenario, then verify that an existing matching account is handled without the 403 and that synchronization completes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- authentication
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100