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

Closed
Open
Created Jun 13, 2014 by Administrator@rootOwner

Can't login through api (and gitlab-ci) using omniauth != LDAP

Created by: dpasqualin

I've installed gitlab-ci, which (as you know) can integrate with Gitlab users database through the api, but this feature doesn't seem to work with omniauth authentication (kerberos).

What I've found out so far:

When I first log in through kerberos, gitlab creates an internal account for the new user with a random password. Afterwards, I'm able to log in using my kerberos login/password in the Gitlab login page, and completely ignore the random password generated, as expected.

But if I try to log in through the api, instead of looking for my kerberos login/password, the api checks only for my Gitlab account information, and the random generated password, which I don't possess.

I've tried to track the login process at the code and it seems to me that the problem is in the lib/gitlab/auth.rb file, which tries to log in using either the Gitlab or LDAP account, but not any other omniauth provider.

Assignee
Assign to
Time tracking