FAQ - Software Engineering Services (GitLab)

Each GitLab Account (via SSO) can create 50 projects within GitLab.

https://blog.rwth-aachen.de/itc/2023/04/26/gitlab/

After login, a new account was generated because your contact email address from IdM Selfservice and the primary email address of your actual GitLab account are different.

However, the old account still exists. You can solve the problem on your own with the following steps:

1.     Set the primary email address stored in your original account as the contact email address in Selfservice.
2.     Delete the new account by yourself (git-ce: https://git-ce.rwth-aachen.de/-/profile/account // git.rwth: https://git-ce.rwth-aachen.de/-/profile/account)
3.     Wait for a synchronization time of about 20 minutes
4.     Now you can log back into the original account

* If you do not know the mail-address for 1., please contact the IT-ServiceDesk

Note: Afterwards, you can change your email addresses again as you wish, since a new ID has been saved in your GitLab account.

The Login via Github is intended only for external project partners who can't authenticate via Shibboleth. Please use the Github Login only when there is no possibility to authenticate via Shibboleth, because the account will otherwise be flagged as external and the right to create projects will be revoked.

DFN-AAI issue

This is related to the change of the login from 03/05/2023:

https://blog.rwth-aachen.de/itc/2023/04/26/gitlab/

If the error occurs, it means that your contact mail address from the Selfservice, is not set as primary mail address in GitLab, but as e.g.: secondary mail address.

You can solve the issue yourself by changing the contact mail address in Selfservice to the current primary address of your GitLab account, waiting for a synchronization period of 20 minutes, and then logging in again.

Note: This action is only necessary once to store a new ID in GitLab. You can change all mail addresses again afterwards.

Github issue

The error may be caused by the fact that you have logged in via GitHub. The login via RWTH Single Sign-On does not work if the contact email address in the Identity Management of RWTH is identical to the email address from GitHub.

If you are able to log in via GitHub, please try to activate the login via the RWTH Single Sign-On on your own:

1. log in via GitHub, if possible.
2. click on the avatar icon in the top right corner of your dashboard.
3. click "Edit Profile" in the menu that pops up.
4. click "Account" in the navigation on the left.
5. in the "Social sign-in" section, click on the "DFN-AAI Single Sign-On" button to sign in using RWTH Single Sign-On.

You can then log in using both GitHub and the RWTH Single Sign-On.

To be able to create projects and/or groups, you need to be additionally unlocked. To do so, please tell us your GitLab username (you can find it by clicking on the avatar icon in the upper right corner, behind the @).
We will grant the appropriate permissions.

When signing in using the Single Sign-On (SSO) you may receive the error message "Return parameter is not included in the positive list".

If this occurs, you should clear your browser's cache before trying to sign in again.

Once a group permission has been set, it is not possible to grant individual user permissions (that deviate from the set group permission) to members of the group.

Users can change their displayed username by themselves via "Profile → Account". Please be aware of the fact that by changing the username, the namespace will automatically be altered as well. As a consequence, all links to already existing projects will be altered too.

When git-cloning, users need to use their username from GitLab (not the email and not the Shibboleth username!) and a specific access token, that needs to be set in advance (user settings - access token), to log in. The username (format: ab123456) and the associated password can not be used in this case.

As a group, any number of projects can be created.The number of projects of a group does not affect the quota of each group member.

You can conventionally authenticate with a username and password to use GitLab push and pull. This password needs to be set in the GitLab userprofile though. As soon as a password has been set, push & pull will work out via https.

DSA keys are not supported by OpenSSH 7.0 and newer Versions but not rejected by GitLab. That leads to an error.

A RSA key is to be used instead of a DSA Key.

First, you need an App to generate two factor auth codes. A list of Apps with code generator

Google Authenticator
Play Store: https://play.google.com/store/apps/details?id=com.google.android.apps.authenticator2&hl=de
iTunes: https://itunes.apple.com/de/app/google-authenticator/id388497605?mt=8

Authy
Play Store: https://play.google.com/store/apps/details?id=com.authy.authy&hl=de
iTunes: https://itunes.apple.com/de/app/authy/id494168017?mt=8

After the install of the app, go to your GitLab profile (https://git.rwth-aachen.de/-/profile/account) and activate the two factor authentification.

You can find your Username

• In the usermenu on top right (just behind the @)
• On the site https://git.rwth-aachen.de/-/profile/account   // https://git-ce.rwth-aachen.de/-/profile/account ("Change Username")

Currently we do not offer a GitLab Runner for all users. To install your own GitLab Runner on your computer or server, please follow the official GitLab Runner instructions.

Git LFS is active by default on both GitLab instances of RWTH Aachen University in all repositories. A tutorial on git LFS can be found here

In order to restore the images, you have to follow the next steps:

1. Clone Wiki Repo (in the GUI under Wiki → "Clone Repository" at the top right, then execute the command shown)
2. Export repo (in the GUI under Settings → General → Extensions → Export project)
3. Unpack the generated export
4. Copy and push the files and directories from the uploads folder from the export to the uploads directory of the locally cloned wiki

5. Adjust the paths in all * .md files and make a backup at the same time:

6. Now "push" the changed files back into the repository. Ignore the .bak files

7. Check wiki in GUI