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

Closed
Open
Created Apr 28, 2014 by Administrator@rootOwner

Gitlab API should allow me to create a user that needs no confirmation

Created by: darklajid

Migration: Gitorious -> Gitlab.

To migrate users/projects/repositories the plan is to do it exactly in that order: I need the users first to have some kind of mapping between permissions in Gitorious and Gitlab, when I create the projects.

Users are LDAP backed:

  • the email address is 100% correct
  • the password that I have to specify is utterly useless (might need another ticket) and random

Currently LDAP support means that users could easily 'register', they'd be autocreated when they try to log in. But THAT would mean that I couldn't define permissions for these not-yet-in-gitlab users. Creating these users using the web API I can grant permissions, but these users are now locked out as unconfirmed.

Testing the migration means that I'm doing this process over and over again (=> Sending mails would be bad) and even the final deployment shouldn't spam users.

The only workaround right now is to modify the DB directly, issuing something like

update users set confirmation_token=null, confirmed_at=now() where confirmed_at is null;

I propose extending the web API to create

  • users that need no confirmation
  • (optional) require no password (those users would be locked out of course or need to be ldap backed)
Assignee
Assign to
Time tracking