This additional explanation covers the sessions at the Identity Provider and
the Service Provider.
It illustrates the different flows in case the user has already a valid session at the one of them.
Furthermore, some facts about Shibboleth sessions are outlined and it is shown what data is contained in a valid session and which information is bound to a
session.
The Service Provider checks:
Data bound to a Service Provider session is:
Note: If the Discovery Service is setting a cookie containing the user's Identity Provider selection, the dashed steps are omitted and the user's web browser is redirected directly to the user's Identity Provider.
The Identity Provider checks the following:
If one of these points does not match, the Identity Provider will enforce an authentication for the user.
Both timeouts (session and authentication method) are based on inactivity,
they are updated during each authentication request.
If the session expires, all authentication method timeouts are cleared.
| Take a look at the expert demo if you would like to see this login procedure in action. |