ATH-UC-05: Authentication using an eID

This version is a draft one and it will be enhanced as the sprints progress.

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

TBC

Specification
Use case ID	ATH-UC-05-BF
Use case name	Authentication using an eID card
Actors	Citizen Healthcare giver Representative of an institution
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	The user has already an account The user has: an eID card a PIN code of his/her eID card a wireless card reader
Post-Conditions	The user is authenticated The user has access to the services of the mobile application
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 reader
	2	The application sends an access request to the SP
	3	The SP sends an authentication request to the IDP
	4	The IDP checks the identity of the user with the AA
	5	The IDP sends a response message to the SP to inform it that the user is identified
	6	The SP returns a response message to the application to enable the authentication
	7	The user is authenticated and can use the the services of the mobile application
Exceptions (exception flows)	The PIN of the eID card is not correct The creation is aborted (e.g. loss of connection, problem with the wireless card reader, the session is expired)
Frequency	Every time the user needs to authenticate to the mobile application

Flow	Specification
	Use case ID	ATH-UC-05-AF-01
	Use case name	First authentication using an eID card (ATH-UC-(01,02,03,04)-BF)
	Actors
	Short Description
	Priority	1 (High) Must have: The system must implement this goal/ assumption to be accepted.
	Pre-Conditions
	Post-Conditions
	Steps	0
		1
		2
		3
		4
		5
		6
		7
		8
		9
		10
	Exceptions (exception flows)
	Frequency

Specification
Use case ID	ATH-UC-01-EF-01
Use case name	The PIN of the eID card is not correct
Actors	Citizen Representative of an institution Healthcare giver
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	The user has already an account The user has: an eID card a PIN code of his/her eID card a wireless card reader
Post-Conditions	The authentication is interrupted
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	Every time for a user needs to authenticate him/herself and enter a wrong PIN code

Specification
Use case ID	ATH-UC-05-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	Citizen Representative of an institution Healthcare giver
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	The user has already an account The user has: an eID card a PIN code of his/her eID card a wireless card reader
Post-Conditions	The authentication is interrupted
Steps (basic flow)
Frequency	Every time for a user needs to authenticate him/herself and loses the connection