This page is not fully translated, yet. Please help completing the translation.
(remove this paragraph once the translation is finished)
(back to Overview)
Can the concept of attribute quality be adopted 1:1 from SWITCH? See Attribute Quality
Attribute
Identity Proof
References:
Identity verification etc. | RAF | eIDAS | DFN-AAI | edu-ID |
---|---|---|---|---|
RAF: 1. Identity proofing and credential issuance, 2. renewal and replacement eIDAS: 2.1.2, 2.2.2, 2.2.4 | /IAP/low | – | Basic (only 1.) | Placeholder 1 |
/IAP/medium | low | Advanced (only 1.) | Placeholder 2 | |
/IAP/high | substantial | – | Placeholder 3 | |
– | high | – | Placeholder 4 |
Important question: Can we assume that the quality of the identity determination is proportional to the quality of the attributes derived from the respective identity source? If yes, then so(?):
Attribute/identity sources | Proposal categorization | Comments |
---|---|---|
self-asserted | Placeholder 0 | – |
Challenge-Response | Placeholder 1 | Analog DFN-AAI Basic |
eID (eIDAS) - eID server (clients: ID card app, card reader, etc.) | Placeholder 2-4 | If eIDAS LoA is known(?) |
eID (eIDAS) - other module confirmations (e.g. Post Ident) | Placeholder 2 | LoA not known - eIDAS low must be accepted |
Home institution (DFN-AAI) | Placeholder 1-2 | DFN-AAI Basic or Advanced |
Other - ORCID | Placeholder 1 | API + User Login |
Other … (others to be expected) | depending on the method used for linking |