To enable federated access to shared resources of research communities and to enable the integrated use e-infrastructure services, the pilots activity in AARC will run a large number of pilots as a step-up to concrete AAI services. The requirements of research communities and e-infrastructures will drive the design of either missing AAI components or new services. To put this into action the AARC pilots activity consists of 4 tasks:
...
Below you find a more detailed description of the activities to be performed for each task
Task1: Pilots with research communities based on use cases provided (lead by GARR and GRNET)
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 |
|---|
 Image Modified
|
HelixNebulaHelixNebula pilot info and updates HelixNebula pilot intake form |
| Connecting services & Brokering Leverage the work done by AARC on policies and architectural blueprints Implementing Sirtfi Using eduGAIN | | Status |
|---|
| |
|---|
| colour | Green |
|---|
| title | Concluded |
|---|
|
|
AARC involvement was limited; however there is a lesson learned that can be useful for similar pilots.EISCAT_3D pilot info and updates EISCAT_3D pilot intake form | AAI | Move away from IP based access towards federated AAI according to the AARC BPA |
Cross infrause case integration with EGI/EUDAT/PRACE Controlled, granular access to resources. Need for a good LoA scheme for AuthZBlueImplementation | Initial work done by EISCAT to clone their environment on a dedicated VM.EPOS pilot info and updates EPOS pilot intake form | Cross infra use case integration Delegated and delegated federated access (non-interactive) |
WorkflowsBlueImplementation | Training delivered by NA2.
|
 Image Modified
| CTA |
CTA pilot info and updates CTA pilot intake form | Cherenkov Telescope Array | Initial implementation of Community IdP/SP proxy, Group/Role based access to resources, SIRTFI and CoCo/GDPR compliance | |
BlueImplementation | Proxy installed.
Documentation being prepared via SA1.T4
LifeWatch pilot info and updates LifeWatch pilot intake form | Integration,AAI | Implementation of AAI according to the AARC BPA; access for citizen |
scientistYellowDiscussionCORBEL pilot info and updates
CORBEL pilot intake formBlueImplementation | Pilot now in phase 2 until end of May.
 Image Removed
WLCG | WLCG pilot info and updates WLCG pilot intake form | Non webstuff (SAML-X509) Implementation of Sirtfi stuff Solution for a persistent unique ID (ORCID?)YellowDiscussion
Image Removed Image Added
|
LIGO
LIGO pilot info and updates LIGO pilot intake form | Non web scenarios + enrolment workflows| DARIAH AAI | Implementing an AAI according BPA to allow communication between DARIAH and other infrastructures | |
BlueImplementationTask2: Support and pilots for e-infrastructures interoperability and integration (lead by EGI)
This task will focus on piloting AAI components and frameworks to enable transparent interoperability between infrastructures in terms of authentication and authorisation and will build on the state of the art of the AAI services provided by the infrastructures.
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.
Infrastructures| Infrastructure | Links | Topics/Focus | Status |
|---|
 Image Modified Image Modified
|
EGI and EUDAT| 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. |
See also: This pilot has been absorbed by the LS AAI pilot |
Image Added Image Added | EUDAT-PRACE |
EUDAT-EGI Image RemovedImage RemovedEUDAT and PRACE | 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. |
| | Status |
|---|
| colour | Green |
|---|
| title | Concluded |
|---|
|
|
 Image AddedImage Added
| DARIAH AAI |
See also: EUDAT-PRACE pilot for cross-infrastructure access to resources
Image RemovedImage RemovedDariah and EGI | 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: - The DARIAH AAI will be extended with a proxy according to the AARC BPA. This proxy will be based on Shibboleth and enable further interoperability endeavors.
- Based on the work from the first pilot, the goal of this pilot is to achieve interoperability between the DARIAH AAI and EGI. This will include harmonization of LoA and group membership expressions, according to the AARC recommendations.
| | Status |
|---|
| |
|---|
| colour | Green |
|---|
| title | Concluded |
|---|
|
|
 Image Modified
 Image Modified
|
eduTEAMS and EUDAT and EGI
| Two pilots: - eduTEAMS + EUDAT B2ACCESS
- eduTEAMS + EGI CheckIn service
| 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)
This task will pilot solutions that complement the eight AAI use cases provided by the selected research communities (piloted within Task 1) and the cross e-infrastructure integration issues addressed by Task 2. As such, the task will investigate advanced AAI scenarios by taking into consideration the results of AARC1 and by building a feedback loop with JRA1 and NA3.
...
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.
Task4: Creation of showcases, deployment scenarios and documentation based on successful pilots in AARC2 (Lead by RETI)
The pilots in AARC and AARC2 will produce a lot of experience, documentation and interesting showcases. In collaboration with the NA2 activity, these results will be combined with technical training material and offered as one package to the community.
...
