• Publicationsclose
• Open Access close
• Report close
• English close
• EGI Federation close
• Instruct-ERIC close

The Life Sciences AAI Service (LS AAI), developed in joint collaboration with EGI, EUDAT and GÉANT, will result in a production-equivalent service to be operated for the Life Sciences community by the joint e-Infrastructures. As the pilot enters its second phase the LS AAI has to declare compliance to R&S and CoCo towards the R&E federations. This document provides preliminary guidance for the operators of the pilot LS AAI.

Instruct-ERIC Annual Report 2017-18

This specification defines how SP-IdP Proxies can provide hints about services towards Discovery Services to improve the user experience of the authentication process.

Authored by: the FIM4R Community The European Open Science Cloud (EOSC) will soon enter the next phase of integration and consolidation with the establishment of a common service portal listing underpinning services that enable distributed resources in the areas of computation, data, open access, and above-the-net collaboration services. The existing e-Infrastructures that are anticipated to be part of the EOSC each provide their own capabilities in terms of trust and identity management, integrity protection and risk management, as well as capabilities to support business continuity and disaster recovery in case of security incidents. There are also specific trust, collaboration management, and security services that are jointly managed by multiple e-Infrastructures for the benefit of (but in many cases not exclusively) the European research and collaboration community as a whole. These include for instance the glue between the EOSC AAI suite of services that each implement the AARC Blueprint Architecture (AARC BPA), i.e. the AAI services such as those from both national and pan-European Infrastructures as well as components such as credential translation bridge services.

This document provides a specification for expressing resource-specific capabilities using entitlements. A capability defines the resource or child-resource a user is allowed to access, optionally specifying certain actions the user is entitled to perform. Capabilities can be used to convey - in a compact form - authorisation information.

This document defines a generic browser-based protocol for conveying - to services - hints about the IdPs or SP-IdP-proxies that should be used for authenticating the principal. This protocol, colloquially referred to as Identity Provider (IdP) hinting, can greatly simplify the discovery process for the end-user, by enabling entities to produce and send hints that can be consumed by SP-IdP-proxies for routing the user to the correct upstream SP-IdP-Proxy or authenticating IdP.

Instruct-ERIC Annual Report 2019

Conveying affiliation information from origin providers across infrastructures proxies as defined in G025 is only possible if the origin identity provider releases such information. In case no eduPersonScopedAffiliation is provided, it may be partially reconstructed according to these guidelines. If there is no reliable way to infer origin

The AARC Blueprint Architecture (BPA) provides a set of building blocks for software architects and technical decision makers who are designing and implementing access management solutions for international research collaborations. This document describes the evolution of the AARC Blueprint Architecture, starting with a summary of the changes since AARC-BPA-2017. The current iteration of the BPA focuses on the interoperability aspects, to address an increasing number of use cases from research communities requiring access to federated resources offered by different research and e-Infrastructures. Hence the introduction of the Community AAI, which streamlines researchers’ access to services. These typically include services offered to members of a specific community, as well as infrastructure services that may be shared with other communities. Users can authenticate to the Community AAI primarily via institutional credentials from national identity federations in eduGAIN, but, if permitted by the community, can also use other Identity Providers.

This document reports on the activities of the Work Package 4 (WP4). Building on a considerable legacy of existing operational web portals developed and used by the Structural Biology / WeNMR user community, WP4 aims at provisioning a consistent einfrastructure to allow gradual integration of the existing isolated solutions to a single computing and data processing environment, based on the state of the art grid and cloud open source software tools and frameworks. This report follows the document D4.3, delivered at project month 15, and the document M4.4 delivered at month 24, so that only the progress achieved until project month 26 not already described previously will be reported here. The document starts with an updated description of the resources potentially available for the project from the EGI e-infrastructure, on top of which the consolidated West-Life platform is being built. It then presents a detailed view of resource usage and their geographical distribution in the second year of the project, as obtained from the EGI Accounting Portal. The remaining of the document reports the latest experiences and updates the activity plans on the consolidated job management mechanism, the programmatic access to datasets and the unified security and accounting model.