This version is a draft one and it will be enhanced as the sprints progress.
Table of Contents |
---|
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 |
Identity & Authorization Management (I.AM) - Identity Provider (IDP) | 1.0 | https://www.ehealth.fgov.be/ehealthplatform/fr/data/file/view/d43784683d86392e68f1a95b860f721170f30c7b?name=ehealth_i.am_-_idp_v1.0.pdf |
CSAM Youtube channel | - | https://www.youtube.com/channel/UCzMGudd9xdMeGjYpbpjsXFw |
General information
In the figure below, we provide an overview about the interaction between the different services of the e-health platform involved in the IAM. It is noteworthy that the presented architecture is dedicated to the WebSSO solution.
Basic flow
Flow | Specification | ||
---|---|---|---|
Use case ID | ATH-UC-05-BF | ||
Use case name | Authentication using an eID card | ||
Actors |
| ||
Short Description | This use case denotes the authentication of a user via an eID card. | ||
1 (High) Must have: The system must implement this goal/ assumption to be accepted. | |||
Pre-Conditions |
| ||
Post-Conditions |
| ||
Steps (basic flow) | 0 | The user access to the WebSSO application interface to authenticate him/herself and choose the option eID | |
1 | The user connects using his/her credentials (eID card + PIN) and the wireless card the card reader | ||
2 | The application sends an access request to the SP | ||
3 | The SP sends | an authenticationa request message to the AS to access to the IDP | |
4 | The AS sends a message to the IDP to identify the non authenticated user | ||
5 | The IDP checks the identity of the user with the AA | ||
56 | The IDP sends a response message to the SP AA to inform it that the user is identified | ||
7 | The AS sends a message with the identify of the user to the SP | ||
86 | The SP returns a response message to the application to enable the authentication | ||
79 | The user is authenticated and can use the the services of the mobile application | ||
Exceptions (exception flows) |
| ||
Frequency |
|
Alternative flow 1
Specification | ||
---|---|---|
Use case ID | ATH-UC-05-AF-01 | |
Use case name | First authentication using an eID card | |
Actors |
| |
Short Description | Depending on the profile of the actor, this alternative flow will be instantiated by one of the four use cases dedicated to the creation of a new account (refer to the basic flows): ATH-UC-01, ATH-UC-02, ATH-UC-03, ATH-UC-04. To implement this flow, the user should authenticate him/herself in the mobile application using the eID card. | |
Priority | 1 (High) Must have: The system must implement this goal/ assumption to be accepted. | |
Pre-Conditions |
|
| ||
Post-Conditions |
| |
Steps | For more details and depending on the type of the actor, see: | |
Exceptions (exception flows) |
|
| ||
Frequency |
|
Exception flow 1
Specification | ||
---|---|---|
Use case ID | ATH-UC-0105-EF-01 | |
Use case name | The PIN of the eID card is not correct | |
Actors |
| |
Short Description | It denotes the use case when the user tries to authenticate with his/her eID card and fails in entering the PIN. | |
Priority | 1 (High) Must have: The system must implement this goal/ assumption to be accepted. | |
Pre-Conditions |
| |
Post-Conditions |
| |
Steps (basic flow) | 0 | The user access to the WebSSO application interface to authenticate him/herself and choose the option eID |
1 | The user tries to connect using a wrong PIN code | |
2 | The authentication is interrupted | |
Frequency |
|
Exception flow 2
Specification | ||
---|---|---|
Use case ID | ATH-UC-05-EF-02 | |
Use case name | The creation is aborted (e.g. loss of connection, problem with |
the card reader, the session is expired) | ||
Actors |
| |
Short Description | It denotes the exception use case when the user loses the connection and he/she will not be able to finish the authentication. It may happens at any step of the basic and alternative flows. | |
Priority | 1 (High) Must have: The system must implement this goal/ assumption to be accepted. | |
Pre-Conditions |
|
| ||
Post-Conditions |
| |
Steps (basic flow) | ||
Frequency |
|