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

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

  • Report abuse

  • New issue

  • Report abuse

signin_enabled: false has no effect on GitLab 7.7.1

Closed

signin_enabled: false has no effect on GitLab 7.7.1

Created by: JonathonReinhart

I'm using GitLab 7.7.1 omnibus, and want to force LDAP sign-in.

I've edited /etc/gitlab/gitlab.rb and specified gitlab_rails['signin_enabled'] = false, and re-configured. Indeed, I see that /opt/gitlab/embedded/service/gitlab-rails/config/gitlab.yml has the line signin_enabled: false, as expected.

However, after restarting GitLab (with gitlab-ctl restart), I still see the normal sign-in tab on the sign-in page, (along with LDAP sign-in). I was expecting only the LDAP sign-in tab to be present.

Linked issues
0


  • Administrator
    Administrator @root · 10 years ago
    Owner

    Created by: silicht

    Same problem with gitlab_rails['gitlab_signup_enabled'] = false

    By Administrator on 2015-01-30T11:25:13 (imported from GitLab project)

  • Administrator
    Administrator @root · 10 years ago
    Owner

    Created by: JonathonReinhart

    I'm not seeing that. I have signup disabled successfully. On Jan 30, 2015 6:25 AM, "thwfreak" notifications@github.com wrote:

    Same problem with gitlab_rails['gitlab_signup_enabled'] = false

    — Reply to this email directly or view it on GitHub https://github.com/gitlabhq/gitlabhq/issues/8689#issuecomment-72187649.

    By Administrator on 2015-01-30T13:14:22 (imported from GitLab project)

  • Administrator
    Administrator @root · 10 years ago
    Owner

    Created by: silicht

    Hmm... what did you do exactly? With gitlab_rails['gitlab_signup_enabled'] = false there is signup_enabled: false in /var/opt/gitlab/gitlab-rails/etc/gitlab.yml. Also I reconfigured and restartet with gitlab-ctl, but the Signup form is allready in the front page.

    By Administrator on 2015-01-30T13:51:34 (imported from GitLab project)

  • Administrator
    Administrator @root · 10 years ago
    Owner

    Created by: arif-ali

    See #8648 (closed)

    You now have to do it from the Admin settings page

    By Administrator on 2015-01-30T16:12:19 (imported from GitLab project)

  • Administrator
    Administrator @root · 10 years ago
    Owner

    Created by: robertd

    @arif-ali Thanks!

    By Administrator on 2015-01-30T17:02:38 (imported from GitLab project)

  • Administrator
    Administrator @root · 10 years ago
    Owner

    Created by: silicht

    @arif-ali Thank you!

    By Administrator on 2015-01-30T17:17:19 (imported from GitLab project)

  • Administrator
    Administrator @root · 10 years ago
    Owner

    Created by: robertd

    FYI... in v7.7.2 default option for signup_enabled is false. In current master it's true

    By Administrator on 2015-01-30T17:18:57 (imported from GitLab project)

  • Administrator
    Administrator @root · 10 years ago
    Owner

    Created by: nneul

    That option should probably be removed entirely from the config since it doesn't seem to have any effect.

    By Administrator on 2015-01-31T19:11:21 (imported from GitLab project)

  • Administrator
    Administrator @root · 10 years ago
    Owner

    Created by: JonathonReinhart

    Yes, I agree. Both "signup" and "signin" have entries in the GUI now. On Jan 31, 2015 2:11 PM, "Nathan Neulinger" notifications@github.com wrote:

    That option should probably be removed entirely from the config since it doesn't seem to have any effect.

    — Reply to this email directly or view it on GitHub https://github.com/gitlabhq/gitlabhq/issues/8689#issuecomment-72331341.

    By Administrator on 2015-01-31T19:19:23 (imported from GitLab project)

  • Administrator
    Administrator @root · 10 years ago
    Owner

    Created by: thias

    +1 : Second time I get bitten by the setting being ignored after an upgrade, and digging through the code without understanding why...

    By Administrator on 2015-03-04T15:01:14 (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
None
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