...
A total of eight use-cases from research communities have been selected to pilot with AAI solutions. A support team will be created to work with the research communities to match the best solutions and architecture with those use cases. Intermediate results will be shared with the relevant communities and feedback will be used to advance the further work.
| Community | Links | Topics/Focus | Status | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Connecting services & Brokering Leverage the work done by AARC on policies and architectural blueprints Implementing Sirtfi Using eduGAIN |
| |||||||||
| Move away from IP based access towards federated AAI according to the AARC BPACross infrause case integration with EGI/EUDAT/PRACE Controlled, granular access to resources. Need for a good LoA scheme for AuthZ |
| |||||||||
| Evolve current AAI towards one that is fully compliant with AARC BPA; support cross infra use cases Cross infra use case integrationwith EGI/EUDAT/PRACE Delegatedand delegated federated access (non-interactive) Workflowsworkflows |
| |||||||||
| Initial implementation of Community IdP/SP proxy, Group/Role based access to resources, SIRTFI and CoCo/GDPR compliance |
| |||||||||
| Implementation of AAI according to the AARC BPA; Integration, access for citizen scientistscientists |
| |||||||||
| Inter compatibility, share a common AAI shaping according to the ideas in Elixir. Also focus on sustainability and operational aspects
|
| |||||||||
| Implementation of IdP/SP Proxy, mainly to provide Token Translation Services to allow end users to login without the need of manually managing X.509 certificates Non webstuff (SAML-X509) Implementation of Sirtfi stuff Solution for a persistent unique ID (ORCID?) |
| |||||||||
| Implement AAI according to AARC BPANon web scenarios + enrolment workflows |
| |||||||||
| DARIAH AAI | Implementing an AAI according BPA to allow communication between Dariah DARIAH and other infrastructures |
|
Task2: Support and pilots for e-infrastructures interoperability and integration (lead by EGI)
...
This task’s work will be driven by the requirements and use cases of both e-infrastructures and research infrastructures and the results of the JRA1 activity.
| e-Infrastructure | Links | Topics/Focus | Status |
|---|---|---|---|
| EUDAT-EGI pilot for cross-infrastructure access to resources | The technical integration of the EGI and EUDAT AAIs has started but we recognize that additional effort is needed to harmonise attributes and Level of Assurance (LoA) definitions. The team therefore continues to work on an earlier started joint proposal by AARC, EGI and EUDAT to harmonise the LoA of their identities for consumption by their internal services. |
This pilot has been absorbed by the LS AAI pilot | ||||||
| EUDAT-PRACE pilot for cross-infrastructure access to resources | The high-level goal of this pilot is to achieve AAI interoperability between EUDAT and PRACE and to examine how Unity technology may be used to accomplish this task. The solution consists of two components. The first one is the automatic provisioning of accounts for selected PRACE users who authenticate with x.509 certificates. EUDAT accepts these certificates and PRACE users become registered users in the EUDAT authentication and authorisation service. This gives PRACE users access to non-x.509-based EUDAT services. The second component needs to synchronise these accounts with EUDAT data services using certificate credentials. |
|
|
| ||||||||
| DARIAH AAI | Implementing a Proxy-Element according to the AARC BPA in the DARIAH AAI and enabling integration with EGI There are two consecutive and related pilots:
|
|
|
| ||
| Two pilots:
|
This pilot has been absorbed by the LS AAI pilot |
Task3: Piloting advanced use cases, new solutions and approaches based on the outcomes of JRA1 and NA3 (Lead by GRNET)
...
In addition, this task will deal with cross community use cases. In Q4 2017, Task3 started the life science Life Sciences & health Health pilot for the CORBEL community. This was triggered by a formal request by CORBEL to come up with an overarching AAI infrastructure. Since AAI is not the 'core business' of CORBEL, they prefer having that part sustained by the e-Infrastructures. Therefore, CORBEL wrote a document with their AAI requirements (See: https://goo.gl/zvTQmB) and asked requested the 3 e-Infrastructures in AARC2 (EGI, EUDAT & GÉANT) to respond with a proposal. It quickly became clear that the best way to approach this respons was to submit a combined proposal, where each e-Infrastructure provides a part of the final solution. A first phase of a pilot has been finalised early February. A recording of the demo is available here: https://geant.app.box.com/v/ls-aai-phase-1-demo
. The second phase of the life science pilot commenced in February, results will follow soon.
...