...
focus on the integration aspects of the blueprint architecture
provide recommendations and guidelines for implementers, service providers and infrastructure operators on implementing scalable and interoperable AAIs across e-infrastructures and scientific communities
work in close collaboration with the policy, pilots, and the training and outreach activities of AARC2
work on the evolution of the blueprint architecture, with a focus on identity provider / service provider (IdP/SP) proxies, scalable authorisation solutions for multi-service provider environments and other solutions for integrating with R&E federations and cross-sector AAIs
Documents
Final
Guidelines
| ID | Title | Summary | Links | Status | ||||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
AARC-G002 Supersedes: AARC-G001 (June 13, 2017) Other identifiers: AARC-JRA1.4A) | Guidelines on expressing group membership and role information | This document standardises the way group membership information is expressed. It defines a URN-based identification scheme that supports: indicating the entity that is authoritative for each piece of group membership information; expressing VO membership and role information; representing group hierarchies. | AARC-JRA1.4A (201710) [PDF] Older versions AARC-JRA1.4A (1.0) [PDF] |
| ||||||||||||
AARC-G003 Other idenftifiers: AARC-JRA1.4B | Guidelines on attribute aggregation | This document discusses attribute aggregation scenarios applied in international research collaborations. Attribute aggregation can take place at proxy, SP or TTS services, in-line with the Blueprint Architecture. | ||||||||||||||
AARC-G004 Other idenftifiers: AARC-JRA1.4C | Guidelines on token translation services | This document discusses attribute aggregation scenarios applied in international research collaborations. Attribute aggregation can take place at proxy, SP or TTS services, in-line with the Blueprint Architecture. | ||||||||||||||
AARC-G005 Other idenftifiers: AARC-JRA1.4D | Guidelines on credential delegation | In distributed environments it is often necessary for a remote service to access other services on behalf of a user, or for a software agent to act on behalf of the user. This guidelines consider delegation of credentials based on signed assertions, session tickets, “tokens” of various types, and proxy certificates. | ||||||||||||||
AARC-G006 Other idenftifiers: AARC-JRA1.4E | Best practices for managing authorisation | This document provides best practices for a range of models for Authorisation policy enforcement that apply at service providers end-points, even if not always solely on the resource SP alone, e.g. in the case of an IdP/SP proxy. | ||||||||||||||
AARC-G007 Other idenftifiers: AARC-JRA1.4F | Guidelines on non-browser access | Overview of non-web access mechanisms in common use for both interactive (command-line) access and for API based access. Mechanisms based on ssh, PKIX/X.509, API keys and OIDC are reviewed and placed in context. | ||||||||||||||
AARC-G008 Other idenftifiers: AARC-JRA1.4G | Guidelines for implementing SAML authentication proxies for social media identity providers | This guidelines provides recommendations and best practices for implementing authentication proxies that can connect social media identity providers with federated SAML 2.0 service providers. | ||||||||||||||
AARC-G009 Other idenftifiers: AARC-JRA1.4H | Account linking and LoA elevation use cases and common practices for international research collaboration | In Identity linking (account linking) the user’s infrastructure identity is associated with external identities, i.e. created and assigned outside of the administrative boundaries of the infrastructure, such as institutional IdPs or social media IdPs. This linking may be either implicit or explicit to the user. The document reviews use cases and considers consistency of representation, accounting, and traceability of linked identities. | ||||||||||||||
AARC-G010 Other idenftifiers: AARC-JRA1.4I | Best practices and recommendations for attribute translation from federated authentication to X.509 credentials | This guideline suggests the common way to encode authentication and authorization in X.509 credentials, to increase the re-usability and interoperability of X.509 credentials generated by token translation services. | ||||||||||||||
AARC-G021 (was AARC2-JRA1.1A) | Guideline on the exchange of specific assurance information between Infrastructures | Infrastructures and generic e-Infrastructures compose an ‘effective’ assurance profile derived from several sources, yet it is desirable to exchange the resulting assurance assertion obtained between Infrastructures so that it need not be re-computed by a recipient Infrastructure or Infrastructure service provider. This document describes the assurance profiles recommended to be used by the Infrastructure AAI Proxies between infrastructures. |
| |||||||||||||
AARC-G029 (was AARC2-JRA1.2C) | Guidelines on stepping up the authentication component in AAIs implementing the AARC BPA | A number of research community use cases require users to verify their identity by using more than one type of credentials, for instance using password authentication, together with some physical object such as a phone or usb stick that generates tokens/pins, etc. At the same time, there are services that may require an already logged in user to re-authenticate using a stronger authentication mechanism when accessing sensitive resources. Authentication step-up is then needed to improve the original authentication strength of those users. This document provides guidelines on step-up of the authentication component. It covers requirements and implementation recommendations, describes a proposed authentication step-up model, and outlines related work and documentation. |
| |||||||||||||
AARC-G031 (was AARC2-JRA1.3A) | Guidelines for the evaluation and combination of the assurance of external identities | The Research Infrastructures (from now on just Infrastructures) that follow the AARC Blueprint Architecture [AARC-BPA] set up their own AAI to grant access to their services. The AAI is typically based on a central IdP-SP proxy that act as a gateway for the Infrastructure services and resources. In order to assign an identity to the users of the research collaboration or the community they serve, Infrastructures rely on external Identity Providers and employ identity linking strategies. The Infrastructures also define one or more assurance profiles, or a combination of assurance components, tailored to a specific risk assessment [AARC-G021]. In order to assign an assurance profile to a user, the Infrastructure shall evaluate the assurance components of the linked identity, or identities, used to register to the Infrastructure’s AAI or used during authentication at the infrastructure proxy. These guidelines provide a method to combine assurance information and to compensate for the lack of it. |
|
Deliverables
| ID | Title | Summary | Links | ||||||
|---|---|---|---|---|---|---|---|---|---|
| Authorisation Models for SPs | This deliverable describes possible authorisation models for SAML-SPs and OIDC-RPs in a proxied environment. We provide an overview about available and upcoming technologies currently in use or development for community and research infrastructures. |
Active Drafts
Deliverables
| ID | Title | Summary | Links | Status | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|
| AARC2-DRJA1.1 | Use-Cases for Interoperable Cross-Infrastructure AAI | The researchers’ need to access online services and resources offered by different research and e-infrastructures has increased over the last years. Through federated access, researchers should be able to seamlessly and securely access resources across these infrastructures using their existing credentials from their home organisations. AAI interoperability is a key requirement to support this. The AARC Blueprint Architecture has been designed to address this need, aiming to improve the user experience when accessing and sharing resources provided by different infrastructures. To this end, this document analyses research community use cases that require access to services and resources across infrastructures. The research community specific use cases have been mapped to a set of generic use cases of cross-infrastructure AAI flows. These flows will serve as input for further refining and complementing where needed the AAI interoperability aspects of the AARC Blueprint Architecture. |
Due: | |||||||||
| AARC2-DJRA1.3 | VO Platforms for Research Collaborations | VOs make it possible for infrastructures to support larger user groups by providing a layer of abstraction between the users and the infrastructure. If VOs pool together users with common purpose/funding/applications, it makes it easier for the infrastructure to support through the VO, and for the users to obtain their resources through the VO. | (update link)doc |
Due: |
Guidelines
| ID | Title | Summary | Links | Status | ||||||
|---|---|---|---|---|---|---|---|---|---|---|
AARC-G026 (was AARC2-JRA1.1F) | Guidelines for expressing unique user identifiers across infrastructures (was Guidelines for uniquely identifying users across infrastructures) | A variety of different user identifiers in different formats is used by research infrastructures and e-infrastructures. The goal of this document is to define how the user identifiers should be expressed when transported across AARC BPA-compliant AAIs. Different strategies for generating these identifiers are also proposed. |
| |||||||
AARC-G032 (was AARC2-JRA1.3B) | Guidelines for registering OIDC Relying Parties in AAIs for international research collaboration | This document describes different ways to accomplish an OpenID Connect client registration, specifically providing guidance for International Research Collaborations that need to implement one of these systems. |
| |||||||
AARC-G036 (was AARC2-JRA1.4A) | Roles, responsibilities and security considerations for VOs | Virtual Organisations (VOs) have several roles and responsibilities; some are identified as community responsibilities, and others arise from relations to infrastructures (e.g. security contact, technical contact). Can we minimise the number of places that need this information, in order to improve maintainability and scalability? |
| |||||||
AARC-G037 (was AARC2-JRA1.4B) | Guidelines for combining group membership and role information in multi-AA environments | When combining information from several AAs, one needs to consider the different semantics, different levels of assurance, and different purposes of the AAs and their attributes. |
|
Upcoming / Inactive Drafts
Guidelines
...