Used documentation
| Cookbook/ materials | Version | Location |
|---|---|---|
| Identity & Authorization Management (I.AM) - Overview | 1.0 | https://www.ehealth.fgov.be/ehealthplatform/file/view/c87f7d093e56ff1054c73d6aae09e0bb?filename=ehealth_i.am_-_overv |
| Technical specifications Identity & Authorization Management (I.AM)- Logout | 1.0 | https://www.ehealth.fgov.be/ehealthplatform/file/view/8f9881c65700081363c8922c5e7928da?filename=ehealth_i.am_-_logout |
| Cookbook Identity & Authorization Management (I.AM) - SP Shibboleth | 1.0 | https://www.ehealth.fgov.be/ehealthplatform/file/view/9eae84bee7bf8370f12841558ed2308a?filename=ehealth_i.am_-_sp_shibboleth_v1.0.pdf |
| NativeSPServiceLogout wiki page | old version (2010) | https://wiki.shibboleth.net/confluence/display/SHIB2/NativeSPServiceLogout |
| NativeSPSingleLogoutService wiki page | 2018 | https://wiki.shibboleth.net/confluence/display/SHIB2/NativeSPSingleLogoutService |
| NativeSPLogoutInitiator wiki page | 2018 | https://wiki.shibboleth.net/confluence/display/SHIB2/NativeSPLogoutInitiator |
| Issue 14 in JIRA | - |
General information
The IDP has itself a Logout link to end its own session properly.
Logout in an application and the IDP can be combined if needed but should be done with care as this actually breaks SSO.
logout by :
- pressing a button
- closing the mobile application
3 types of logout:
- Application logout
- IDP logout
- Application + IDP logout
Basic flow
| Flow | Specification | ||
|---|---|---|---|
| Use case ID | ATH-UC-08-BF | |
Use case name | Local logout | ||
Actors |
| ||
Short Description | |||
1 (High) Must have: The system must implement this goal/ assumption to be accepted. | |||
Pre-Conditions | |||
Post-Conditions |
| ||
Steps (basic flow) | 0 | The user accesses to the WebSSO based mobile application interface to locally logout | |
1 | |||
2 | |||
| 3 | |||
4 | |||
5 | |||
6 | |||
| 7 | |||
8 | |||
9 | |||
| 10 | |||
| 11 | |||
Exceptions (exception flows) | |||
Frequency |
| ||
