1. https://aarc-project.eu Authentication and Authorisation for Research and Collaboration Bari, Italy Training and Outreach Authentication and Authorisation for Research and Collaboration 12th November 2015 Maria Laura Mantovani NA2 T4 Leader, GARR and Università di Modena e Reggio Emilia

2. https://aarc-project.eu “A primary objective of this project is to promote and further deploy federated access for researchers, educators and students. Dedicated training and outreach material should help to lower barriers to entry for organisations not already participating in identity federations.” 2 The essence Repackage and add what is missing

3. https://aarc-project.eu Report on the identified target groups for training and their requirements – DNA2.1 (M3) https://aarc-project.eu/wp-content/uploads/2015/04/AARC-DNA2.1.pdf First online module Federation101 on federated access – DNA2.2 (M5) https://aarc-project.eu/documents/training-modules/federations-101/ Training Material for resource providers – DNA2.3 (M9) Training Material for Identity Providers – DNA2.4 (M14) 3 Training and Outreach: Deliverables

4. https://aarc-project.eu First document describing the approach to the training – MNA2.1 (M3) First SP training delivered – MNA2.2 (M9) First IdP Training delivered – MNA2.3 (M14) https://aarc-project.eu/documents/milestones/ 4 Training and Outreach: Milestones

5. https://aarc-project.eu Libraries: represented by LIBER and MKZ. Arts and humanities: DARIAH represented by DAASI. Bio-medical: ELIXIR represented by CSC. High-energy physics: represented by CERN. E-Infrastructures: represented by EGI and SURFsara (for PRACE and – jointly with CSC – for EUDAT). NRENs: They not only represent the national federations, but also the organisational communities that have been supported by NRENs for decades (e.g. library, IT staff, educators, students, researchers etc.) 5 AARC Partners and User Communities

6. https://aarc-project.eu Three-dimension approach: The individual requirements of each of the different communities; Different roles have different needs and different requirements; Whether an institution deploys federated access or not. The methodology followed used two main approaches to identify the requirements: A survey sent to the organisations belonging to different communities that are not yet federated. The questions in the survey were elaborated keeping in mind the different target roles. Meetings with specific user communities. 6 Process and Methodology for Requirements collection

7. https://aarc-project.eu Decision makers: The term “decision maker” refers to high-level managers in universities and institutions, and leaders of large (research) consortia. Identity Provider (IdP) operators: The people in the organisation that set up and operate an Identity Provider service. Service Provider (SP) operators and Service developers: Service provider operators and service developers have a distinct role in the uptake of federated identity… End Users; 7 Identified Target groups

8. https://aarc-project.eu In our 3-dimension approach the questionnaire was sent to a group of technical people (target role) belonging to organisations that are not federated yet (status). At the same time, with this survey we targeted all the user communities. The group of organisations involved in the survey that were not yet federated was then further divided in two groups: Universities. Other institutions (National libraries and archives, Research institutions in bio-medical fields, Institutions for Arts and Music). 8 Survey findings

9. https://aarc-project.eu Common Identified Requirements: Information material for decision makers: when asked for more information on why the organisation lacks the technical people required to implement an IdM the most prevalent answer was that decision makers do not understand the business benefit of federated identity. Lack of identifiable benefits leads to skepticism and reluctance to invest money in hiring or training personnel on the deployment and operation of federated identity services. Training to fill in the gaps in the knowledge of the technical people already in the organisation. A better organised eduGAIN service catalogue that shows the benefits that the resources can bring to the organisations. Information material about eduGAIN. 9 Survey findings

10. https://aarc-project.eu Module concept: on-line modules for self study re-use existing well-chosen material Module contents: Motivation How to Secure Content A Service Provider, and an Identity Provider So What is a Federation? And What if the Online Resource is in a Different Country from my Users? But what is Shibboleth then? Are there other Technologies for Federation? https://aarc-project.eu/documents/training-modules/federations-101 10 Federations 101 Module aim: basic concepts of federated access focus on videos for people with little or no background in federations

11. https://aarc-project.eu Small and new institutions that want to use IP-based authentication and that cannot rely on many public IPs (as this is becoming more difficult). They or the publishers might be a target group; Funding agencies (nationally and internationally) to add a requirement along the lines federated access should be preferred to any other approach; Push the EC to enable federated access for their website; Translate the results of AARC work in an easy language; (federation 101) Consultancy on federated access would help - start by targeting a few groups; 11 Feedbacks (I2-TE and Brussels workshop)

12. https://aarc-project.eu Library users are ideal users for R&E collaboration services and e-infrastructures If library users are provided with digital identities, they can easily access to collaboration services and e-infrastructures Thanks to eduGAIN, libraries can rely on many federated services among publishers Not-federated publishers are still running Libraries want an easy to use and direct access to publishers Libraries don’t want their users need to tackle with complex and not clear procedures AARC works to overcome ip-based authN/Z, but still many libraries rely on it Many libraries still don’t rely on federated access towards publishers Contracts with publishers don’t foresee duty for publishers about federated access 12 Library problem

13. https://aarc-project.eu Identify which are in Europe the Bodies that at National level make Negotiation of Electronic Resources (https://goo.gl/cfmLBN )https://goo.gl/cfmLBN Collect in each country 2-3 libraries happy to collaborate with AARC to provide requirements and to pilot use cases Compare how federated access towards publishers is working from different European countries (https://goo.gl/pwMiZN )https://goo.gl/pwMiZN Compare clauses on federated access in license contracts in order to drive towards an harmonization at European level Produce a value proposition on federated identity for decision makers in libraries with focus on the library use case Training for libraries on the library use case 13 What AARC is doing for libraries?

14. https://aarc-project.eu Info material for decision makers within libraries Federation 101 as a real training (90 minutes training at Liber Conference in Helsinki 29.june-1.july 2016) Training for SPs (two-days hands-on training in March 2016 in Manchester) Dissemination of AARC results 14 Plan for the next future

15. https://aarc-project.eu Thank you Any Questions? © GÉANT on behalf of the AARC project. The work leading to these results has received funding from the European Union’s Horizon 2020 research and innovation programme under Grant Agreement No. 653965 (AARC). https://aarc-project.eu marialaura.mantovani@garr.it