| Table of Contents |
|---|
| Tip | ||
|---|---|---|
| ||
The purpose of the AARC Blueprint Architecture (BPA) is to provide set of interoperable architectural building blocks for software architects and technical decision makers, who are designing and implementing access management solutions for international research collaborations.This is the wiki space of the Working Group in the Architecture Area of the AARC Community and AEGIS. Participation in the working group is open to individuals who are interested in following and contributing to the evolution of the AARC Blueprint Architecture and its supporting Guideline documents. Discussions about the ongoing work of the WG take place in the aarc-architecture mailing list. The group holds a weekly call every other Monday at 14:00 CE(ST) |
| Section | |||||
|---|---|---|---|---|---|
|
...
|
...
|
Active Draft Document
Documents
Guidelines
| ID | Title | Summary | Links | Status |
|---|---|---|---|---|
| AARC- |
Supersedes: AARC-G001 (June 13, 2017)
Other identifiers:
AARC-JRA1.4A)
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]
| Status | ||||
|---|---|---|---|---|
|
| Status | ||||
|---|---|---|---|---|
|
AARC-G003
Other idenftifiers:
AARC-JRA1.4B
| Status | ||||
|---|---|---|---|---|
|
AARC-G004
Other idenftifiers:
AARC-JRA1.4C
| Status | ||||
|---|---|---|---|---|
|
AARC-G005
Other idenftifiers:
AARC-JRA1.4D
| Status | ||||
|---|---|---|---|---|
|
AARC-G006
Other idenftifiers:
AARC-JRA1.4E
Best practices for managing authorisation
| Status | ||||
|---|---|---|---|---|
|
AARC-G007
Other idenftifiers:
AARC-JRA1.4F
| Status | ||||
|---|---|---|---|---|
|
AARC-G008
Other idenftifiers:
AARC-JRA1.4G
| Status | ||||
|---|---|---|---|---|
|
AARC-G009
Other idenftifiers:
AARC-JRA1.4H
| Status | ||||
|---|---|---|---|---|
|
AARC-G010
Other idenftifiers:
AARC-JRA1.4I
| Status | ||||
|---|---|---|---|---|
|
AARC-G021
(was AARC2-JRA1.1A)
| Status | ||||
|---|---|---|---|---|
|
| Status | ||||
|---|---|---|---|---|
|
| Status | ||||
|---|---|---|---|---|
|
| Status | ||||
|---|---|---|---|---|
|
AARC-G029
(was AARC2-JRA1.2C)
| Status | ||||
|---|---|---|---|---|
|
AARC-G031
(was AARC2-JRA1.3A)
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.
| Status | ||||
|---|---|---|---|---|
|
| Status | ||||
|---|---|---|---|---|
|
Deliverables
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.
Guidelines
| Status | ||||
|---|---|---|---|---|
|
AARC-G025
(AARC2-JRA1.1E)
| G052 | OAuth 2.0 Proxied Token Introspection | This specification extends the OAuth 2.0 Token Introspection (RFC7662) method to allow conveying meta-information about a token from an Authorization Server (AS) to the protected resource even when there is no direct trust relationship between the protected resource and the token issuer. The method defined in this specification, termed "proxied" token introspection, requires access tokens to be presented in JWT format containing the iss claim for identifying the issuer of the token. Proxied token introspection assumes that the AS which is trusted by the protected resource has established a trust relationship with the AS which has issued the token that needs to be validated. | Google doc |
| ||||||
| AARC-G056 | AARC profile for expressing community identity attributes | This document defines a profile for expressing the attributes of a researcher’s digital identity. The profile contains a common list of attributes and definitions based on existing standards and best practises in research & education. The attributes include identifiers, profile information, and community attributes such as group membership and role information. | Google doc |
| ||||||
| AARC-I058 | Methods for establishing trust between OAuth 2.0 Authorization Servers | This document explores different approaches for establishing trust among entities such as OAuth 2.0 Authorization Servers (AS) and Resource Servers (RS) residing in distinct domains. These interactions are facilitated through trusted third parties referred to as Trust Anchors, which are entities issuing authoritative statements about entities that participate in an identity federation. | Google doc |
| ||||||
| AARC-G073 | Guidelines for refreshing tokens between proxies | This document explores the refresh token flow in a scenario where client applications interact with resource servers through interconnected OpenID Providers (OIDC). Specifically, it focuses on the case where an AARC-compliant Infrastructure Proxy [AARC-G045] acts as an intermediary between the client and a Community AAI. To address challenges related to refresh token handling in this configuration, the document specifies a secure refresh token flow that leverages introspection to ensure the validity of refresh tokens before issuing new access tokens. The document describes the flows for both obtaining and using refresh tokens. | Google doc |
| ||||||
| AARC-G080 | AARC Blueprint Architecture 2025 | 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-2019. | Google doc (Initial Revision) |
| ||||||
| AARC-G081 | Recommendations for Token Lifetimes | This document provides an overview over various types of tokens, or more generally, about assertions used to identify and authorise users. We analyse the different properties of tokens and categorise available authorisation patterns to give recommendations about the life times of tokens associated with specific properties and authorisation levels. The document is between policy and architecture working group | Google doc |
|
Upcoming / Inactive Drafts
Guidelines
| ID | Title | Summary | Links | Status | ||||
|---|---|---|---|---|---|---|---|---|
| AARC-G058 | Establishing trust between OAuth 2.0 Authorization Servers | Specification for establishing trust among OAuth Proxies (based on AARC-I058) |
| |||||
| AARC-G079 | AARC Community-based Access Entity Category | This document provides guidelines for using the Community-based Access Entity Category to support the release of attributes to Service Providers that have a proven need to receive a set of community-managed information about their users in order to effectively provide their service to the users. | Google doc |
| ||||
| AARC-G059 | Guidelines for expressing affiliation information | The goal of this document is to define how affiliation information should be expressed when transported across AARC BPA-compliant AAIs. Two different types of affiliation have been identified, namely Affiliation within the Home Organisation, such as a university, research institution or private company; and Affiliation within the Community, such as cross-organisation collaborations. Both affiliation types should be communicated to the service providers that rely on affiliation information in order to control access to resources. |
...
| Will supersede AARC-G025 |
|
...
|
...
AARC-I047
(was AARC2-JRA1.2A)
...
...
| Status | ||||
|---|---|---|---|---|
|
...
This document defines a generic browser-based protocol for conveying - to services - hints about the IdPs or IdP-SP-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 either narrowing down the number of possible/IdPs to choose from or by making the actual selection process fully transparent.
...
...
| Status | ||||
|---|---|---|---|---|
|
Waiting for feedback from voPerson schema (see voPerson issue#40) | ||||||||
| AARC-G060 | A framework for IdP hinting | Google doc |
| |||||
| AARC-G064 | A specification for hinting which IdPs to show in discovery | Google doc |
| |||||
| AARC-G053 | Specification for expressing user authentication via REFEDS R&S and/or Sirtfi compliant authentication providers | Google doc |
| |||||
| AARC-G054 | Specification for expressing authenticating authorities | Google doc |
|
...
AARC-I028 (was AARC2-JRA1.2B) | Best practices for integrating OpenID Connect / OAuth2 based end services | Capture what OIDC-based services need to understand, which schemes to follow in order to benefit from federated identities, that currently are exclusively in the SAML world. This will probably include pointers to documents that specify mappings between SAML and OIDC expression of attributes, entitlements or claims. OIDC/OAuth2 client registration is covered in AARC-G032 |
|
...
|
...
Upcoming / Inactive Drafts
Guidelines
| ||||||||||||||||||
| AARC-G038 AARC2-JRA1.4C | Best practises for scalable account (de)provisioning of VO members | Best practises for scalable account provisioning, management, and deprovisioning, particularly from the perspective of the standard protocols used to manage accounts (such as LDAP, VOOT, SCIM, etc.) | doc |
| ID | Title | Summary | Links | Status||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
AARC-G032 (was AARC2-JRA1.3B) | Guidelines for registering OIDC Relying Parties in AAIs | for internationalfor 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-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-G036 (was AARC2-JRA1.4A) | Roles, responsibilities and security considerations for VOs | DROPPED. Most of the content is now in DJRA1.3; it was proposed to gather the remaining information into a document describing how roles and the requirements on roles be managed (e.g. "there must always be a security contact"); however, we have decided that we will not have enough time to do justice to the topic. 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. |
| |||||||||||||||
AARC-G030 (AARC2-JRA1.2D) | Requirements and Implementations for Authentication Freshness (was: Guidelines for step-up authentication via forced reauthentication) | This document describes mechanisms for forcing a user to perform an additional login (reauthentication) in order to ensure that the user who is accessing a protected resource is the same person who initially authenticated at the start of the session. Forced reauthentication can therefore provide additional protection for sensitive resources. |
| |||||||||||||||
| AARC2-JRA1.1B | Guidelines for the discovery of authoritative attribute providers across different operational domains |
| ||||||||||||||||
| AARC2-JRA1.1C | Guidelines for handling user registration and user consent for releasing attributes across different operational domains |
| ||||||||||||||||
| AARC2-JRA1.1D | Guidelines for federated access to non-web services across different operational domains |
| ||||||||||||||||
| AARC2-JRA1.3C | Guidelines for AAI interoperability with non-R&E Identity Providers in support of international research collaboration |
| ||||||||||||||||
| AARC2-JRA1.3D | Guidelines for AAI interoperability with eIDAS Identity Providers in support of international research collaboration |
| ||||||||||||||||
| AARC2-JRA1.3E | AAI tools & technologies enabling OIDC for international research collaboration |
| ||||||||||||||||
| AARC2-JRA1.4D | Guidelines for implementing, operating and using VO platforms | it was suggested this incorporate anything from JRA1.4A not included in DJRA1.3 plus guidance on evaluating and selecting a proxy platform. However, as we have too many documents already and not enough time to do them justice, JRA1 have decided to drop this document. However, EOSC Hub is currently (as of March 2019) putting together an evaluation form. It was suggested at the F2F in April 2019 that this document be resurrected? |
|