EGI-EUDAT AAI interoperability - 17 May 2016

Attendees:
EGI: Enol, Christos, Nicolas, Diego
EUDAT: Dejan, Hans, Willem
ICOS: Ute

* Nicolas presented the EGI AAI. See slides attached in the agenda

* Willem presented the EUDAT AAI. See slides attached in the agenda

Open Discussion:

Willem: What are the EGI plans to move the new AAI into production?
Christos: the activity is a pilot but from a technology point of view we are ready to move the available components in production.
This will be a step by step process that should be completed by the end of 2016

Willem: I think that the simplest way to proceed is integrating both services (EGI IdP/SP proxy and B2ACCESS) as IdP of the other.
We need also to understand how to map EGI identities to EUDAT and viceversa.

Diego: the final target should be allowing end-users to transparently access EGI and EUDAT services. When a user is authenticated once on EGI and EUDAT,
it should be able to see the EGI and EUDAT services as services of a unique infrastructure. This is the e-infrastructure commons concept.

Diego describes the pilot use case of the EGI/EUDAT collaboration [1]. A user creates a VM in the EGI fedcloud, performs some computations on the VM and stage-out the output
of the computation in a B2STAGE/B2SAFE services. The user should be able to do it with a unique credential with a single sign-on.
This requires enabling delegation between EGI and EUDAT

Christos: this is very complex. We need to go step by step.

Willem: it is complex but we should have almost all the needed technologies

Christos: the first step is allowing access EGI and EUDAT web services with the same credential.
We can define a plan for the core integration in a short time.

Everybody agreed to draft the plan for the core integration by the 27th of May.

Willem: we should also work on the data privacy issue since we need ti share attributes between the 2 infrastructure. We need a policy harmonisation.

Christos: for the policy harmonisation we should rely on AARC

Actions:
- Diego will create a google doc to work on the core integration and to define a roadmap.
- Willem, Christos and Nicolas will work on this document --> to be ready by the 27 of May

[1] https://indico.egi.eu/indico/event/2544/session/37/contribution/203/material/slides/0.pptx