You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 18 Next »

JRA1: Architectures for an integrated and interoperable AAI

Work Package Leader: GRNET, Christos Kanellopoulos (grnet)

 

Existing AAIs serve the needs of the R&E community worldwide on a segmented basis. These are well established within their local communities, but individually they lack the ability to form an interoperable AAI. Some examples of these include

  • eduGAIN to offer Single Sign-On for web applications;

  • Libraries that still use IP-based access;

  • PRACE and EGI that use digital certificates,

  • Government spaces that rely on national e-IDs and STORK. A citizen who is also a student or an educator could in principle link a government identity with an educational one, with the possibility to access different context providers during the different ages, i.e. at the education stage and at the university stage.

 

This work package will investigate the obstacles that prevent users, educators and researchers from using their credentials to access services offered by the various e- Infrastructures, libraries and research communities. 

This work package will carry out research to:

  • Facilitate access to resources and collaboration between researchers, students and educators;

  • Reduce duplication of efforts for developing and deploying AAI services common to many e-infrastructures;

  • Explore the technical elements needed for the integrated AAI: attribute frameworks and deployable non-web technologies;

  • Expand the coverage of national identity federations for network, services and applications by supporting research institutions with low levels of technical or organisational preparedness by delivering easy-to-use solutions for them to enable federated access.

The output of this work package will be the technical design of the integrated AAI framework. All research aspects and architectural design will be carried out in this JRA1, NA3 will provide the necessary policies, while any implementations and pilots are done in SA1. The JRA1 final results will be informed by feedback from SA1’s pilot results. 

JRA1.1 Requirements gathering

Task Leader: EGI.eu, Peter Solagna

Goals of the task:

  • Describe the authentication and authorisation technologies used by the different e-Infrastructures, including research communities, libraries and educational service providers and identify the existing gaps that prevent their interoperability. Explore how the current e-Infrastructures can support broader cross-domain collaboration, for instance when dealing with commercial services and or with e-Government initiatives.
  • Prioritise the work to undertake on the basis of the community requirements, results of pilots carried out by the GN3plus project and FIM4R group and on the technical analysis of existing pilots to support groups, token translation and SSO for non-web.
  • Explore how the current e-Infrastructures can support broader cross-domain collaboration, for instance when dealing with commercial services and or with e-Government initiatives.
  • Gather information on the penetration of AAIs and eduGAIN in R&E sector, libraries and e-Government.
  • Gather information on the interoperation experiments between R&E federations (including eduGAIN) and eGOV in the different European countries. Determine the maturity level and portability of the solutions enabling non-Web SSO, which is important when access to computing and storage services in several e-Infrastructures and cloud is considered.
  • Document relevant standards bodies and other interoperation activities and their role in supporting AAI

Actions and activities of the task

First action of the task has been to prepare and circulate a questionnaire among the relevant communities (circulated on the  1st of July 2015) to gather requirements both on the technical architecture and the dissemination/training activities.

The questionnaire can be downloaded here: AARC Requirements questionnaire

The first round of requirements will be collected until July 10th 2015

JRA1.2 - Blueprint Archtectures

Task Leader: KIT, Marcus Hardt

First action was to start the discussion about the points raised at the JRA1 presentation in the kickoff.

Please read and comment in the Report from the kickoff meeting.

JRA1.3 - Guest identities

Task Leader: STFC, Jens Jensen - STFC UKRI

Guest identities are about making use of external IdPs. The basic idea is to accept social media logins:

  • Assign a suitable Level of Assurance (LoA) to them
  • Allow users to build reputation
  • Allow reputation to be communicated - e.g. from one community to another
  • Investigate a "web of trust" - whether users can vouch for each other, say.
  • Within AARC, links to NA3 (policy and LoA for guest identities) and SA1 (piloting guest identities)

JRA1.3

  • Accommodating "guest identities" - please find the deliverable-in-progress AARC MJRA1.2 (everyone with the link can comment; if you need write access please request it.)

JRA1.4 - Models for implementing Attribute Providers and Token Translation Services

Task Leader: GARR, Andrea Biancini.

Within this task we will evaluate how Attribute Providers and Token Translation services could be used to extend the current scope of existing identity federations to existing communities of users and projects.

The overall goal of this task is twofold:

  1. integrate different AAIs with existing federations (already interfederated in eduGAIN); in this respect the main communities considered will be:

    • NRENs, with SSO for web applications

    • libraries, using IP-based access

    • PRACE and EGI, using x509 certs

    • government spaces (for instance using STORK)

  2. provide a model for implementing pilots:

    • on Attribute Authorities, and

    • on Token Translation Services.

Documents and deliverables:

The project activities, so far, produced the following relevant documentation:

  • Flows for AAs [JRA1.4-1 Information flows for AAs]

    This is a working document which will intend to describe the possible flows and high level use cases of user interactions involving Attribute Authorities. It is intended to be an outline/draft for people to work on and will provide input to a one pager describing the main terms and concepts regarding AAs to be shared among all participants.
  • Terms and definitions for AAs [link on Google Drive]
    This is a working document which will intend to describe some common terms and definitions of AAI processes involving Attribute Authorities. It is intended to be simple and direct to describe the main terms and concepts regarding AAs to be shared among all participants. 
  • No labels