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

Closed
Open
Created Mar 10, 2015 by Administrator@rootOwner

Filtered ldap users create "local accounts"

Created by: jonakarl

Applicable to gitlab-CE

To recreate:

Create a ldap filter that exclude some users.

Try to log on as such user on a gitlab-CE installation. The user will get created as a "local user" although they will never be able to log on the system (as they are refused due to the ldap filter).

More serious is that if you create a local user that has a email adress in the ldap catalog but are filtered out by the ldap filter, eg a student that should have acces to a staff gitlab installation. If this user by mistake try to log on in the "ldap tab" the accounts will be linked and the user can after this not log on as he/she is filtered in the ldap filter.

possible soultion:

Apply the filter earlier in the process

Assignee
Assign to
Time tracking