Known Issues of User Management for GitLab

Last modified by Boris Folgmann on 2025/12/01 14:53

The following table lists known issues for using GitLab within DevOps-as-a-Service, especially in relation to the central user and project management in the self-service portal.

The entries do not describe real errors, but rather provide assistance on how to avoid inconsistencies between GitLab and the central user management via the self-service portal.

Title	Description	Reproduction	Recommendation to avoid Errors	Workaround in case of Errors
User edit while deassigned from GitLab	When a user is deassigned from GitLab and the user name changed afterwards in the DevOps Portal, then this change is not performed in GitLab.	Create a user A, and add tool GitLab to the user The user account A is created in GitLab Remove GitLab tool assignment from the user A in the DevOps Portal Rename the user in the DevOps Portal to B Assign GitLab to the user The result: user account in GitLab is still A Until a new user name update in the DevOps Portal the name in GitLab remains the same. Role changes do not affect the user name either.	Avoid the change of a user name for a user which was assigned to GitLab and is now deassigned.	After reassigning the user to GitLab, change the user name again in the DevOps Portal, then this changed user name will be propagated to GitLab.
Technical Users	The creation of technical users for Gitlab in the DevOps Portal is currently not supported.		Don't use the technical user feature in the DevOps Portal for GitLab.	Use the features within GitLab to set up tokens for technical users.