Skip to content

GitLab

  • Menu
    • Projects Groups Snippets
      Help
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
  • #605

Closed
Open
Created 13 years ago by Administrator@rootOwner
  • New issue

  • Report abuse

  • New issue

  • Report abuse

Disable regular auth and only allow LDAP?

Closed

Disable regular auth and only allow LDAP?

Created by: jacobfike

So, I am attempting to setup gitlab as a possible replacement for github for my company, but I need to be able to restrict access to valid LDAP accounts.

I can successfully log in through LDAP, but then Gitlab sends me an email with a random password that I can then use to log in with instead of with LDAP. This is bad. The whole point of using LDAP is that if the account is disabled on the LDAP directory, then that account immediately loses all access to any services that use LDAP.

Are there plans to fix this? Ideally, I would like to be able to set LDAP as the only authentication method, and avoid sending the "Your new account is ready" emails.

Can I make this modification myself? Any suggestions?

Linked issues
...

    Related merge requests

    • Administrator
      Administrator @root · 13 years ago
      Owner

      Created by: vsizov

      it would be great. We waiting for pull request from you ;)

      By Administrator on 2012-03-27T21:44:39 (imported from GitLab project)

    • Administrator
      Administrator @root · 13 years ago
      Owner

      Created by: jacobfike

      Sorry, I should have been more clear, I was asking if anyone knows how to make the modification, not offering to write the code for it. I am not a ruby person. I suppose I could poke around in it, but no promises.

      By Administrator on 2012-03-27T22:38:00 (imported from GitLab project)

    • Administrator
      Administrator @root · 13 years ago
      Owner

      Created by: anark

      I did this using devise_ldap_authenticable instead of omniauth. Code is available here https://github.com/versapay/gitlabhq/tree/devise-ldap-auth but still need to do some work to make the tests work with ldap authentication

      By Administrator on 2012-03-28T00:06:29 (imported from GitLab project)

    • Administrator
      Administrator @root · 13 years ago
      Owner

      Created by: GMiLL5

      Are there any plans to implement LDAP-only authentication?

      In addition, could it be configurable to default the login page to LDAP instead of requiring users to click on a "Sign in with LDAP" button?

      By Administrator on 2012-05-31T19:27:03 (imported from GitLab project)

    • Administrator
      Administrator @root · 13 years ago
      Owner

      Created by: vsizov

      maybe. But it is low-priority task.

      By Administrator on 2012-05-31T20:46:29 (imported from GitLab project)

    • Administrator
      Administrator @root · 12 years ago
      Owner

      Created by: bytheway

      It's a hack, but I added this to my routes to force ldap login:

      match '/users/sign_in' => redirect("/users/auth/ldap")

      By Administrator on 2012-09-04T16:15:02 (imported from GitLab project)

    • Administrator
      Administrator @root · 12 years ago
      Owner

      Created by: docwhat

      @bytheway Thanks! That's a big help. It's worth noting this needs to be at the top of the config/routes.rb file...

      By Administrator on 2012-09-04T18:11:38 (imported from GitLab project)

    • Administrator
      Administrator @root · 12 years ago
      Owner

      Created by: harryxu

      +1 for this

      By Administrator on 2013-01-16T18:01:02 (imported from GitLab project)

    • Administrator
      Administrator @root · 12 years ago
      Owner

      Created by: dmsimard

      +1

      By Administrator on 2013-02-20T22:24:35 (imported from GitLab project)

    • Administrator
      Administrator @root · 12 years ago
      Owner

      Created by: dosire

      Moved to http://feedback.gitlab.com/forums/176466-general/suggestions/3788023-only-allow-login-via-ldap

      By Administrator on 2013-03-27T08:41:17 (imported from GitLab project)

    • You're only seeing other activity in the feed. To add a comment, switch to one of the following options.
    Please register or sign in to reply
    0 Assignees
    Assign to
    Milestone
    No milestone
    None
    None
    Time tracking
    Due date
    None
    None
    0
    Labels
    None
    Assign labels
    • No matching results
    • Manage project labels
    Confidentiality
    Not confidential

    You are going to turn on confidentiality. Only team members with at least Reporter access will be able to see and leave comments on the issue.

    Lock issue
    Unlocked
    participants
    Reference:

    Menu

    Projects Groups Snippets
    Help