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
  • #7213

Closed
Open
Created Jun 27, 2014 by Administrator@rootOwner

Former ldap user can not login

Created by: jcockhren

When a user has ldap credentials, the system attempts to access the ldap server even if the ldap authentication is disabled in the config. The following error appears:

Net::LDAP::LdapError (No such address or other socket error.):
  lib/gitlab/ldap/adapter.rb:7:in `open'
  lib/gitlab/ldap/access.rb:7:in `open'
  app/controllers/application_controller.rb:203:in `gitlab_ldap_access'
  app/controllers/application_controller.rb:184:in `ldap_security_check'

This issue existed as #6188 (closed) before the merge with the gitlab EE codebase and was resolved with #6189.

Given the merge of the codebases, the issue resurfaced given the difference in approaches to authentication.

Assignee
Assign to
Time tracking