This page describes the future plans for the EOSC-hub AAI. These include alignment activities across the EOSC-hub AAI services which can be classified into technical and policy-related activities.

Technical alignment activities

The following technical alignment activities have been identified:

The table below lists the identified technical alignment activities and their status. A green checkmark indicates a complete activity, otherwise the expected time of implementation is provided.

ActivityB2ACCESSCheck-ineduTEAMSINDIGO-IAM
Alignment of user attributes
Alignment of VO/group membership and role information
Alignment of resource capabilities information
Alignment of affiliation informationM34M36
Alignment of assurance information (including freshness of affiliation information)M36M35M36
OAuth2 token validation across multiple domains (multi-proxy connection workaround)
OAuth2 token validation across multiple domains (interim implementation based on OAuth2 introspection)M36M36M30

Policy-related integration activities

The following policy-related alignment activities have been identified:

The table below lists the identified policy-related activities and their status. A green checkmark indicates a complete activity, otherwise the expected time of implementation is provided (M21 is September 2019).

ActivityB2ACCESSCheck-ineduTEAMSINDIGO-IAM
Alignment of privacy statementsQ1 2021
Alignment of operational security and incident response policies
Alignment of Acceptable Use Policies (AUPs)

Integration of EOSC-hub AAI services

This section presents the integration roadmap of the EOSC-hub AAI services. The expected time of implementation is described in the table below. Integrations which have already been established are marked with a check mark. The currently identified integration gaps are included in the known issues list.


EUDATEGIGEANTINDIGO-IAM
B2ACCESS
M36M36
Check-in
M36
eduTEAMS
M36
INDIGO-IAMM36

Known issues