JRA1.1 Requirements gathering

Leader: EGI.eu, Peter Solagna (peter.solagna@egi.eu)

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  1^_st 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 10^th 2015

JRA1.3 - Guest identities

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.)