To log into GitLab using the browser, it should be simple as always with the only difference being that you will be redirected to the academiccloud for authentication.

Difficulties may arise when trying to access GitLab using git or a git client.

1. After the change you may not access your remote repository using HTTPS in combination with your account password anymore. There are different ways of solving that issue:
   Use an SSH keypair. We strongly suggest you to use this method! You may read on how to set it up here. At first login with your new SSH key, you will be asked to verify the integrity of the server. The fingerprint may be found here. Note that you will have to change the remote origin of your local repositories to use the SSH-url, either using the command
   git remote set-url origin git@gitlab.gwdg.de:Path/to/project.git
   or directly editing the url-field in .git/config.
2. Use a Token. In your account settings, you may generate a "personal access token" with the scopes you need. These tokens have a maximum lifetime of one year and you may use them like a password, once prompted for it. There are also token created in a group-context or in a project and are usually used in special contexts.
3. Set a password. You may also set a password inside GitLab. We don't suggest this method.