Login with Single Sign-On (SSO)

Single Sign-On lets you access multiple IT services using your AEI account. After signing in at our login page (see below), you can open other SSO-enabled services without entering your password again.

Single Sign-On = Authenticate once per day and access multiple services without entering your password again.

How to sign in

  1. Open the application and choose AEI Single Sign-On (SSO) login.
  2. You are redirected to the Single Sign-On login page (see screenshot below)
  3. Enter your username (e.g. firstname.lastname@aei.mpg.de or username) and your password.
  4. You are redirected to the application.

Login Screen Example

The following screenshot shows what the SSO login page looks like:

Screenshot of the Single Sign-On login page

The URL of the SSO login page looks like https://sso.aei.mpg.de/realms/ucs/login-actions/authenticate?execution=bc88c097-f3aa-417d-affa-29d2e7...

Services enabled with SSO (Work-in-Progress)

Productive Service set SSO productive
https://it-docu.aei.mpg.de ✅
https://help.aei.mpg.de ✅
https://it-support.aei.mpg.de ✅
https://verwaltung.aei.mpg.de ✅
https://services.aei.mpg.de ✅
https://seminars.aei.mpg.de ✅
https://apps.aei.mpg.de ✅
https://personaldb.aei.mpg.de ✅
https://wolke7.aei.mpg.de ✅
https://logbooks.aei.uni-hannover.de ✅
https://inventory.aei.mpg.de ✅
https://app.paperless.io ✅
https://git.aei.mpg.de ✅
https://et-wiki.aei.uni-hannover.de/ ✅
https://astro-cosmo-rel-wiki.aei.mpg.de/ ✅
https://cra-wiki.aei.mpg.de/ ✅
https://library.aei.mpg.de ❌
https://projects.aei.mpg.de ❌

Security Tips

Gitlab: git clone - You must switch from https to using ssh-key

The introduction of Single-Sign-on (SSO) and later Multi-Factor Authentication (MFA) requires us to change how git repos can be cloned.
After the 15th of March 2026 cloning via HTTP/HTTPS will no longer be possible and you will have to use an SSH-Key to clone and work with repositories.

External Users will be forced to enable Two-Factor Authencation (2FA) in gitlab to implement MPG security guidelines!

The preferred way to clone a gitlab repo is with a ssh-key as it is more secure compared to cloning via HTTP or HTTPS.

If you are already using a repo cloned with https you can easily switch to using ssh-key.

  1. Check if you need to create an ssh-key pair or if you already have one. (public- and private-key)
  2. Add your public-key to your git account.
    • Go to git.aei.mpg.de and click on your profile picture in the top right.
    • Click on Preferences.
    • Go to SSH Keys in the User settings on the left.
    • Click the Add new key button in the top right of the table.
    • Paste your PUBLIC Key into the textfield below Key. The other fields can be left default.
    • By default an Expiration date is set. After that date you will have to add your key again. You can also remove the expiry date.
    • Click on Add key.
  3. In your terminal go to your git project folder and type
    git remote -v

    this will display the current URL's used for authenticating with git and look like this:
    origin https://git.aei.mpg.de/{username}/{project}.git (fetch) 
    origin https://git.aei.mpg.de/{username}/{project}.git (push)
  4. Now run the following comand to change the origin URL
    git remote set-url origin git@git.aei.mpg.de:{username}/{project}.git
    as an example the URL's shown above the command would look like this:
    git remote set-url origin git@git.aei.mpg.de:richter/test-p.git
  5. To verify that the change worked check the origin URL's again:
    git remote -v
    It should look similar to this:
    origin git@git.aei.mpg.de:{username}/{project}.git (fetch) 
    origin git@git.aei.mpg.de:{username}/{project}.git (push)
  6. Now run
    git pull
    You will be asked for the pass-phrase of your ssh-key, you are fine now!

If you get an error, check the URL again.

The differences are minimal but for a SSH URL you will see the following: git.aei.mpg.de:{username}/{project}

If your URL still has a / after git.aei.mpg.de or beings with https:// the update did not work correctly.
You can try the commands again, change the URL manually by editing the config file in your .git directory (only if you know what you are doing) or make a small trip to the IT Office (1.03).


Legal Notice, Datenschutzhinweis (Privacy Policy)