Skip to content

GitLab

  • Menu
Projects Groups Snippets
    • Loading...
  • Help
    • Help
    • Support
    • Community forum
    • Submit feedback
    • Contribute to GitLab
  • Sign in
  • G gitlabhq1
  • Project information
    • Project information
    • Activity
    • Labels
    • Members
  • Repository
    • Repository
    • Files
    • Commits
    • Branches
    • Tags
    • Contributors
    • Graph
    • Compare
  • Issues 21
    • Issues 21
    • List
    • Boards
    • Service Desk
    • Milestones
  • Merge requests 12
    • Merge requests 12
  • CI/CD
    • CI/CD
    • Pipelines
    • Jobs
    • Schedules
  • Deployments
    • Deployments
    • Environments
    • Releases
  • Monitor
    • Monitor
    • Incidents
  • Packages & Registries
    • Packages & Registries
    • Package Registry
    • Infrastructure Registry
  • Analytics
    • Analytics
    • CI/CD
    • Repository
    • Value stream
  • Wiki
    • Wiki
  • Snippets
    • Snippets
  • Activity
  • Graph
  • Create a new issue
  • Jobs
  • Commits
  • Issue Boards
Collapse sidebar
  • gpt
  • large_projects
  • gitlabhq1
  • Issues
  • #5544

Closed
Open
Created Nov 05, 2013 by Administrator@rootOwner

LDAP authentication fails when multiple users have the same DN suffix

Created by: jsternberg

We had a user who couldn't clone because gitlab falsely labeled him as "blocked". We found when searching LDAP for his DN that he showed up with two entries. We found that when size: 1 is used, net-ldap returns nil instead of truncating the list. This is filed as ruby-ldap/ruby-net-ldap#75.

Upon closer analysis, the DN's were different. They were structured as:

CN=extra,CN=name,CN=users,OU=org,DC=pc,DC=example,DC=com
CN=name,CN=users,OU=org,DC=pc,DC=example,DC=com

Only the later of those two is what Gitlab should have been looking for. It seems Net::LDAP defaults to searching the whole tree scope instead of base. Searching only at the base scope fixes it so it only returns one entry instead of two.

Assignee
Assign to
Time tracking