Versions Compared

Key

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

...

  • As a user I want to change my profile So that the application (MAIN) could display relevant information related to my profile

Configuration:

  • depending of the scope of the application (MAIN), different profiles could be used. A list of all usable profiles must be done.
  •  
  • Citizen: for the principal with the basic authentication if the user wants to identify himself as a natural person. This is the default profile when a user authenticates on the eHealth IDP.
  • Quality: for the principals that identify the user as a professional (eg DOCTOR)
  • Organization: for the principals that identify the user as a representative of an organization he belongs to.
  • Mandate: for the principals that identify the user as the mandatary of another person or organization from whom he has received a mandate to act on their behalf in a specific context
  • k

...

Initial data/state:

...

Initial data/state:

  • The user must be logged out of MAIN (cf AUTH-TS-9) in order to change his profile

...

Test script IDTest ActionsAssertion
ATH-TS-11


SeqActorActionAutomatic/Manual
1MAINstarting an identification action

Automatic: could be automate but cannot be generic since the applications to test have all a different layout.

2TEST

initialize a test loop based on the application profile configuration

N=1

Automatic
3CSAMauthenticate himself with eid / TOTP / itsME

see TS 5,6 or 7

Manual

34CSAMchoose a the Nth profile (any of thembased on the application profile configuration)Could be difficult to automate as CSAM and MAIN are different applications
5TESTcheck assertion on mainAutomatic: could be automate but cannot be generic since the applications to test have all a different layout. (what to test ?)
6MAINGlobal logout from the applicationAutomatic: could be automate but cannot be generic since the applications to test have all a different layout.
7TESTif it remains profiles to test, goto 3automatic 


In sequence 5, the following assertions must be checked:

MAIN application:

  • the application must display correct information/layout following the profile connected

eHealth endpoint:

  • The IAM session should be open 
  • The IDP session should be open with the corresponding profile