The Policy Harmonisation work package (NA3) seeks input on requirements from communities seeking to implement an "Espresso" profile AAI.
Please edit this page and provide your input (description and/or links) under "Use Cases" below.
Background
The REFEDS Assurance Framework defines 2 profiles covering identification and subsequent authentication -
- Cappuccino profile for low risk use cases
- Espresso profile for demanding use cases
Further information: Draft Assurance Framework (Presentation / Document )
Use Cases
ELIXIR
ELIXIR AAI requires MFA when accessing sensitive data. Principal issues relate to which attribute is associated with the MFA, and what is the resultant reliability, usefulness and cost. A pilot has been run to test a preferred senario with MFA linked to ORCID ID.
Full discussion of senarios and problems are discussed in this document (google doc) together with the pilot roadmap (google doc).
BBMRI
Issues identified with the REFEDS AF are related to
- lack of prescribed attributes and
- timely removal of attributes (1 day required rather than 1 month following termination of employment.)
and are discussed in this document (Overleaf doc).