Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

FlowSpecification










Use case ID

ATH-UC-06-BF

Use case name

Authentication using itsme

Actors

  • Citizen

  • Healthcare giver
  • Representative of an institution

Short Description

This use case denotes the authentication of a user via itsme.


1 (High)

Must have: The system must implement this goal/ assumption to be accepted.

Pre-Conditions

  • The user has an account

  • The user has:

    • a phone number

    • an account in itsme

    • a smartphone with the application itsme

    • a five secure code to confirm the operation on itsme

Post-Conditions

  • The user is authenticated

  • The user has access to the services of the mobile application

Steps (basic flow)

0

The user accesses to the WebSSO application interface to authenticate him/herself

1

The user chooses to connect via itsme 


2The user enters his/her phone number recognized by itsme

3The user connects to the itsme application and confirms the operation

4The user sends his/her credentials

5

The application sends an access request to the SP

6The SP sends a request message to the AS to access to the IDP

7

The AS sends a message to the IDP to identify the non authenticated user


8

The IDP checks the identity of the user with the AA 


9

The IDP sends a response message to the AS to inform it that the user is identified


10The AS sends a message with the identify identity of the user to the SP

11

The SP returns a response message to the application to enable the authentication


12

The user is authenticated and can use the the services of the mobile application

Exceptions (exception flows)

  • The user makes an error when editing his/her credentials (e.g. The phone number of the user is not recognized by itsme)
  • The creation is aborted (e.g. loss of connection, the session is expired)

Frequency

  • Every time the user needs to authenticate to the mobile application

...