...
...
| 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 | Google doc | 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 |
| ID | Title | Summary | Links | Status |
|---|
AARC2-JRA1.1A | Guideline on the exchange of specific assurance information between Infrastructures | Increasingly Research Infrastructures and generic e-Infrastructures compose an 'effective' assurance profile derived from several sources. The assurance elements may come from an institutional identity provider (IdP), from community-provided information sources, from step-up authentication services, and from controls placed upon the user, the community, or the Infrastructure Proxy through either policy or technical enforcement. Knowledge about the upstream source of either identity or authenticator can also influence the risk perception of the Infrastructure and result in a modification of the assurance level, e.g. because it has involved a social identity provider or perhaps a government e-ID. The granularity of this composite assurance profile is attuned to the risk assessment specific to the Infrastructure or Infrastructures, and is often both more fine-grained and more specific than what can reasonably be expressed by generic IdPs or consumed by generic service providers. Yet it is desirable to exchange as complete as possible the assurance assertion obtained between Infrastructures, so that assurance elements need not be re-asserted or re-computed by a recipient Infrastructure or Infrastructure service provider. This document describes the assurance profiles that are recommended to be used by the e-Infrastructures and research infrastructures AAI platforms to exchange user authentication information between infrastructures. | Wiki
doc
| 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.1E | Guidelines for the exchange of affiliation information between infrastructures | This document describes the semantics associated with the use of the affiliation attributes eduPersonAffiliation and/or eduPersonScopedAffiliation when these are asserted by an Infrastructure Proxy when communiting to connected service providers and other Infrastructure Proxies. | Wiki
doc
| Status |
|---|
| colour | Yellow |
|---|
| title | IN PROGRESS |
|---|
|
| | AARC2-JRA1.1F | Guidelines for uniquely identifying users across infrastructures | A variety of different user identifiers in different formats is used by research infrastructures and e-infrastructures for the identification of users. This guideline defines how user identifiers should be shared between infrastructures in order to address inconsistencies in user identification practises. To this end, the document provides guidelines for expressing the identifier of a user for cross-infrastructure access to resources. Identification of users within the boundaries of a single infrastructure is out side of scope of this document. | Wiki doc | |
AARC2-JRA1.2A | Guidelines for scalable and consistent authorisation across multi-SP environments | Managing authorisation at each SP individually does not scale (although in some case it might be required). So, how to do it? Provide guidelines on how one can manage authorisation across multiple SPs, possibly operated by different entities. For some cases centrally managed entitlements (conveying group/role membership for example) might be more than enough. | Wiki old doc New doc: see above | | Status |
|---|
| colour | Grey |
|---|
| title | Stopped |
|---|
Moved to DJRA1.2
AARC2-JRA1.2B | Requirements and guidelines for federated access to OIDC-based services in the context of research collaboration
(was: 1. Requirements and guidelines for SPs using alternative mechanisms and protocols for federated access. 2 OIDC Based Services in research) | 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. |
There is some overlap with AARC2-JRA1.3.B "Guidelines for registering OIDC Relying Parties in AAIs for international research collaboration"colourYellow | on hold | 2CAuthentication-assurance-elevation requirements and guidelines for SPs in the context of international research collaboration
(was: 1. Step-up authentication requirements and guidelines for SPs, renamed in A holistic view on Assurance elevation) | This document collects use-cases and requirements from the communities to describe the current state of the field.
The goal is to also derive a common pattern to guide future implementations of Step-up authentication.
| 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 | |
AARC-G032 (was AARC2-JRA1.3B) |
Wiki old doc new doc | | Status |
|---|
| colour | Red |
|---|
| title | Closing soon |
|---|
|
| | 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. | Wiki doc | | Status |
|---|
| colour | Yellow |
|---|
| title | IN PROGRESS |
|---|
|
|
AARC2-JRA1.3A | Guidelines for evaluating the combined assurance of linked identities
(was: Guidelines for account linking & LoA elevation in cross-sector AAIs) | Wiki doc | | Status |
|---|
| colour | Yellow |
|---|
| title | IN PROGRESS |
|---|
|
| AARC2-JRA1.3B | Guidelines for registering OIDC Relying Parties in AAIs |
for international research collaboration| 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. | Wiki doc | |
colour | YellowIN PROGRESSAARC2JRA1.3CGuidelines for AAI interoperability with non-R&E Identity Providers in support of international research collaboration | 3DGuidelines 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.4A4A) | 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? | Wiki doc | |
colourYellow| title | IN PROGRESS |
|---|
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. | Wiki Doc | |
startedAARC2JRA1.4CGuidelines for scalable account (de)provisioning of VO members | 4DGuidelines for implementing, operating and using VO platforms | ...
...
...
...
...
...
...
...
...
...
...
...
...
