Table of Contents |
---|
Used documentation
General information
The user chooses a profile/a mandate when he is authenticated in the CSAM portal and identified in the IDP and the AA.
...
- Create the mandates with limited or unlimited duration
- Revoke the mandates
- Transfer a mandate from a mandated user to an other one
Basic flow
Flow | Specification | ||
---|---|---|---|
Use case ID | ATH-UC-23-BF | ||
Use case name | Consult and choose a mandate | ||
Actors |
| ||
Short Description | In order to consult and choose a mandate, the user should find the list of the profiles mandates in the IDP in a web browser. This list is updated every time the user is authenticated and identified in the IDP from the authentic data sources. | ||
Priority | 1 (High) Must have: The system must implement this goal/ assumption to be accepted. | ||
Pre-Conditions |
| ||
Post-Conditions |
| ||
Steps (basic flow) | 1 | The user connects via the mobile application | |
2 | The mobile application sends an openID connect authorization request to the IAM connect | ||
3 | The IAM connects redirects the message to the eHealth IDP in a browser | ||
4 | The IDP detects that there is not an open session with the NISS and the name of the user | ||
5 | The IDP redirects the request to the CSAM in order to open a session | ||
6 | The user selects the authentication way (i.e. itsme, eID, TOTP) | ||
7 | The user is authenticated and CSAM returns a SAML assertion to the IDP regarding the user | ||
8 | The user selects a profile and a mandate. The IDP returns the selected profile and mandate to the IAM connect | ||
9 | The IAM connect creates an access token JWT with the selected profile - mandate and returns it to the client | ||
10 | The user is authenticated and accesses to the permitted services in the mobile application with respect to his/her profile and the selected mandate | ||
Exceptions (exception flows) | |||
Frequency |
|
...