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

Closed
Open
Created Jan 23, 2013 by Administrator@rootOwner

LDAP created users must be different.

Created by: nielsbasjes

We've setup Gitlab 4.0 with username/password validation against LDAP. What we found is that an account created because a new user logged in using LDAP creates an account that has several unwanted features.

  1. When a user logs in for the first time the system a new account is created (this is good) and the system sends them an email with their new (randomly generated) password (this is not good).
  2. The user can login using these credentials by opening the "Other signin" part of the login dialog.
  3. The user can change this "gitlab" password in the account settings.
  4. The user can change their username in the account settings.

The desired situation is that an account created because a user logged in via LDAP is marked as "an external system is the owner of the account data" and as such several features regarding such an account should be disabled (at least all of the features mentioned above).

Assignee
Assign to
Time tracking