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
  • Merge requests
  • !3060

Closed
Created 12 years ago by Administrator@rootOwner
  • Report abuse
Report abuse

Disable user creation mails if ldap auth is used

  • Overview 4
  • Commits 1
  • Changes 1

Created by: thomasdupas

Users were complaining of a confusing mail they received with a gitlab password, while they had to use ldap auth.

There is no point in sending the user a password which they shouldn't use (and can't use unless they choose "other auth method" in the login screen, which only increases the confusion)

Loading
Loading

  • Administrator
    Administrator @root · 12 years ago
    Owner

    Created by: raphendyr

    I have made this in generic way in my fork https://github.com/raphendyr/gitlabhq/commit/ae7d5505e34c602c8221fe3a9b1f1f64062f33ec

    Above is based on PR #3046.

    By Administrator on 2013-02-22T14:10:11 (imported from GitLab project)

  • Administrator
    Administrator @root · 12 years ago
    Owner

    Created by: amacarthur

    This is already fixed in a pull request that hasn't been pulled into master yet. Could we consolidate on a single fix?

    https://github.com/gitlabhq/gitlabhq/pull/1505

    By Administrator on 2013-02-22T15:51:16 (imported from GitLab project)

  • Administrator
    Administrator @root · 12 years ago
    Owner

    Created by: raphendyr

    Someone just should decide what's the correct way.

    I think that #1505 might bee best, if there is no omniauth providers that need it.

    By Administrator on 2013-02-22T16:22:26 (imported from GitLab project)

  • Administrator
    Administrator @root · 12 years ago
    Owner

    Created by: dzaporozhets

    closed in favor of #1505

    By Administrator on 2013-03-05T14:52:02 (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
0 Reviewers
Request review from
Milestone
No milestone
None
None
Time tracking
0
Labels
None
Assign labels
  • No matching results
  • Manage project labels
Lock merge request
Unlocked
participants
Reference:
Source branch: github/fork/thomasdupas/master

    0 pending comments