...
Flow | Specification | ||
---|---|---|---|
Use case ID | ATH-UC-07-BF | ||
Use case name | Authentication via TOTP | ||
Actors |
| ||
Short Description | This use case denotes the authentication of a user via TOTP. | ||
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 to connect via a security code via mobile app (TOTP) | |
1 | The user enters his/her username and his/her password | ||
2 | The user connects to the TOTP based mobile application | ||
3 | The user chooses the digital key of CSAM and enters it in the authentication interface | ||
4 | The user sends his/her credentials | ||
5 | The SP sends a request message to the authorization server (AS) to access to the IDentity Provide (IDP) | ||
6 | The AS sends a message to the IDP to identify the non authenticated user | ||
7 | The IDP checks the identity of the user with the AA | ||
8 | The IDP sends a response message to the AS to inform it that the user is identified | ||
9 | The AS sends a message with the identify of the user to the SP | ||
10 | The SP returns a response message to the application to enable the authentication | ||
11 | The user is authenticated | ||
Exceptions (exception flows) |
| ||
Frequency |
|
Alternative flow 1
Specification | ||
---|---|---|
Use case ID | ATH-UC-07-AF-01 | |
Use case name | First authentication via TOTP | |
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 carda TOTP-based mobile application. | |
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-07-EF-01 | |||
Use case name | The PIN of the eID card username or the password is not correctrecognized | |||
Actors |
| |||
Short Description | It denotes the use case when the user tries to authenticate with his/her eID card via a TOTP and fails in entering the PIN.his credentials (username/password) | |||
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 enters his/her username and his/her password | 1 | The user tries to connect using a wrong PIN code | |
2 | The authentication is interrupted because the credentials are not recognized | |||
Frequency |
|
Exception flow 2
Specification | ||
---|---|---|
Use case ID | ATH-UC-07-EF-02 | |
Use case name | The creation is aborted (e.g. loss of connection, problem with the wireless 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 |
|