RocketChat / RocketChat/Rocket.Chat

Can't proceed successful login using LDAP via Samba4 AD Domain Controller

Open
#11,712 6 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

Description:

RocketChat doesn't proceed to login with correct credentials on Samba4 DC's own LDAP implementation. Login proceeds with very similar setup on Windows 2008 AD DC but not on Samba4 AD DC.

Steps to reproduce:
  1. Configure required fields for LDAP authentication.
  2. Test configuration with "TEST CONNECTION" button.
  3. See the "Success Connection_success" notification: OK
  4. Then try to login with an actual user with correct credentials.
Expected behavior:
  1. RocketChat must proceed successful login with correct credentials.
  2. Then allow to user login.
Actual behavior:
  1. Login failed with "User not found or incorrect password" error.
Server Setup Information:
  • Version of Rocket.Chat Server: 0.66.3 - 9c8265045c
  • Operating System: Ubuntu 16.0.4
  • Deployment Method: snap
  • Number of Running Instances: 1
  • DB Replicaset Oplog: Enabled
  • NodeJS Version: 8.11.3 - x64
  • MongoDB Version: 2.6.10-0ubuntu1
Additional context

Log level raised to "Trace" level.
Correct credentials confirmed by logs:
"LDAPResult\",\"status\":0"

Deliberate failed login with incorrect username:
"Error: User not Found"

Deliberate failed login incorrect password:
"Simple Bind Failed: NT_STATUS_LOGON_FAILURE"

Relevant logs:

rocket-ldap.log

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

Start by reviewing Rocket.Chat's LDAP authentication flow and the attached rocket-ldap.log, comparing the successful connection test with the later user login. Reproduce the Samba4 AD case and determine why valid credentials do not resolve a user; done means successful login with Samba4 while preserving the reported incorrect-password behavior.

Written by the indexing model from the issue text.

Assessment

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

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.