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

Closed
Open
Created Jan 23, 2014 by Administrator@rootOwner

ldap -> enabled: false is not being respected

Created by: izreal

In the default gitlab.yml (verified in 6.3 and 6.4), the ldap configuration seems to be used/consumed even when enabled: false is set.

The symptoms are that everything appears to be working correctly, but git commands over SSH fail with "Access denied.", even though I can successfully ssh directly with the git user.

In the production.log, you will see a line like URI::InvalidURIError (the scheme ldaps does not accept registry part: _your_ldap_server:636 (or bad hostname?))

The fix for me was to configure real LDAP configuration but keep enabled: false because I didn't actually want LDAP integration at this time.

Assignee
Assign to
Time tracking