FAQ - Software Engineering Services (GitLab)
Each GitLab Account (via SSO) can create 50 projects within GitLab.
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.
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
Play Store: https://play.google.com/store/apps/details?id=com.google.android.apps.authenticator2&hl=de
After the install of the app, go to your GitLab profile (https://git.rwth-aachen.de/profile/account) and activate the two factor authentification.
First, you have to create a GitHub account beforehand and use it to log into git.rwth-aachen.de. When trying to log in, you will then receive an error "Email has already been taken". When creating the GitHub account, please make sure that you use the same email address as for your previous GitLab account.
After the login attempt send the following data to the IT-Servicedesk:
- your username
- your GitLab ID
- used email address
We will then link the two accounts and thus enable temporary access.
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
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.