Group Migration - Users
Problem to Solve
As described in the parent epic, in the current solution the users have to be manually migrated first in order for objects to be mapped to the appropriate users. This process is time-consuming and error-prone.
Proposed Solution (WIP)
In cases where there is no overriding security concern, the migration process should also create the users that belong to that group.
- On GitLab.com, Admin is required for user creation/access
- Group owner should be able to export (provided the user has a public email address)
- Any user can import a repository, but for users, we require an Admin token (otherwise random users could add members)
- In self-managed instances, we can require that Admin performs Group migration
- For SAML SSO, we can first create the user in GitLab, then map them to SAML
- Potential first iteration: self-managed user import
- Potential solution for GitLab.com: provision a user and trigger a reset password, so that they get an email to access the new group.
- Migrate:
- Avatar
- Profile
- Preferences
- Runner minutes limit
- Group SAML
- SSH Keys
- GPG KEys
- Secondary emails
Documentation
Following documentation should be updated with the fields added in this issue:
-
User docs: https://docs.gitlab.com/ee/user/group/import/ -
Dev docs: https://docs.gitlab.com/ee/development/bulk_import.html
This page may contain information related to upcoming products, features and functionality. It is important to note that the information presented is for informational purposes only, so please do not rely on the information for purchasing or planning purposes. Just like with all projects, the items mentioned on the page are subject to change or delay, and the development, release, and timing of any products, features, or functionality remain at the sole discretion of GitLab Inc.