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

Closed
Open
Created Apr 23, 2013 by Administrator@rootOwner

"Other sign-in" broken when ldap is enabled in 5.1

Created by: fredrik-w

Hi,

After upgrading GitLab to 5.1 I noticed that the "Other sign-in" to use local sign-in isn't working when ldap is enabled. I just keep getting the "Invalid email or password." message. I've done some debugging and found the offending commit: 9d92433a. Specifically in the "devise.rb" [1] initializer, if I revert that minor change (":login" => ":email") both ldap and local logins work fine.

In "lib/api/session.rb" it seems like we're still sending the parameter name in as "email" rather than "login". Though my ruby isn't any good so I might be wrong.

[1] https://github.com/gitlabhq/gitlabhq/blob/9d92433a7c83432657faf4c02839bba1ba6f22ac/config/initializers/devise.rb#L26

Regards, Fredrik

Assignee
Assign to
Time tracking