Login: Overview
frentix customers
The entries "Shibboleth" and "LDAP" only appear in the menu if the respective integration is switched on in the server configuration. For frentix customers, their customer advisor at frentix takes care of the change.

System administrators define how users log in to OpenOlat and register themselves in the adjacent menu of the system administration:
Administration > Login
Profile
| Name | Login |
|---|---|
| Available since | Release 10.2 (2015) |
Login procedures
Before people work with OpenOlat, you define how they log in. Besides the OpenOlat password, a connected system can take over the login, the people then need no OpenOlat password of their own. OpenOlat knows three such login procedures, which can be switched on side by side:
- Cloud login: An identity provider such as Microsoft, Google, Keycloak or Switch edu-ID takes over the login.
- LDAP: OpenOlat takes over the accounts from a directory such as Active Directory and checks the login against this directory.
- Shibboleth: People log in at their university in a Shibboleth federation.
A directory such as Active Directory can be connected in two ways: via LDAP, OpenOlat takes over the accounts from the directory. Via the cloud login integrations "Active Directory Federation Services" and "Microsoft Azure Active Directory" (at Microsoft now Microsoft Entra ID), Microsoft takes over the login, and OpenOlat only receives the confirmation.
System administrators set up the cloud login directly in the menu Login. LDAP and Shibboleth require the server configuration, only then do they appear in the menu. The server configuration is the configuration file of the installation. This file is maintained by the body that operates OpenOlat.
Administrators see the login procedures of a single account in the "Authentications" tab of the account:
User management > "Account of the person" > Tab "Authentications"
Menu items
If you are looking for a menu item, the overview tells you in one sentence what it is for, and the link takes you to its description. The table follows the order of the menu "Login".
| Menu item | Purpose |
|---|---|
| Security | Weigh each protection function of the instance against its effect on embedded content and switch it on. |
| Password and authentication | Select the security level of the login with the OpenOlat password, with or without passkey, determine the rules for passwords and define in the tab "Password change policies" how often users have to change their password. |
| Cloud login | Connect OpenOlat with an identity provider, for example Google, Microsoft Azure Active Directory, Keycloak, Switch edu-ID or your own OAuth 2.0 provider, so that users log in with the account of this service. |
| Shibboleth | Restrict access via Shibboleth to people with certain attributes and read the direct link for the login via Shibboleth. The entry only appears when Shibboleth is switched on in the server configuration. |
| LDAP | Start the synchronization with the directory by hand and remove accounts that are missing from the directory. The entry only appears when LDAP is switched on in the server configuration. |
| Anonymous and external users | Define whether and how far anonymous guests and external users use OpenOlat. |
| Self-registration | Switch on self-registration so that people create their account themselves, and limit with "Validity period of the login data" how long such an account stays valid. |
| SMS | Set up an SMS service so that users reset a forgotten password with a code by SMS. Described further down on this page. |
SMS
So that users can reset a forgotten password with a code by SMS, you set up an SMS service here. With "SMS distribution" you switch on the sending and select the provider under "Service". Then you define whether the code is used for "Reset password" and whether OpenOlat asks for a missing phone number at the first login with "Phone number verification". Costs are incurred for each SMS sent.
Further information
Further reading
Login Concept >
Login Page >
Roles and Rights: Guest access >