Description
Moved discussion from document in the repo to this issue and PR.
Study was conducted by @preriasusi
To solve what attributes authentication customers need, 14 potential stakeholder presenters were interviewed by mail, phone, skype or personally. Stakeholders were from school world and in touch with Educloud alliance. Stakeholders were potential service providers using authentication to authenticate users in school world.
Authentication is to identify users, and authentication data should contain only the info to identify person. For example license info is not included in authentication parameters, but with the unique id, license info could be asked from another service.
During the first round 6 of 14 answered, and on base of answers, the following attributes are chosen:
OID / unique identifier
Unique identifies on national level. For example in Finland ‘Oppijanumero’. https://confluence.csc.fi/download/attachments/8127300/Oppijanumero+ja+OID.pdf
All stakeholders who answered to questionnaire agreed to have this one. This was the most mandatory attribute.
Authorisation level
The authentication level of the session. Strong (for example Tupas, Mobile or Vetuma in Finland) or weak (usually social media, like Facebook, Twitter. May also be LMS).
This was important info for one stakeholder. Some stakeholders did not need this one.
Calling name(s)
First name, given name.
3 stakeholders considered name field as mandatory. For 2 it was “nice to have”.
Surname
3 stakeholders considered name field as mandatory. For 2 it was “nice to have”.
Birth year
Additional proposal.
Email
1 stakeholder proposed to add this one.
Role
Role in school. Teacher, student, pupil, principal for example.
Important info for stakeholders. One considered as mandatory.
School
The school identified with school’s national id
Important for most stakeholders.
Municipality
Code to identify municipality. Municipality list in Finland: http://www02.oph.fi/asiakkaat/rahoitus/perus01k/forms/kuntalista_help1.html
Important for most stakeholders.