...
| ID | Title | Summary | Links | Status | ||||||
|---|---|---|---|---|---|---|---|---|---|---|
AARC-I047 (was 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). This document provides 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 |
| ||||||
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-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 |
| ||||||||
AARC-G028 (was 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" |
| |||||||
| 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.4C | Guidelines for scalable account (de)provisioning of VO members | We propose to cover scalable account provisioning, management, and deprovisioning, particularly from the perspective of the standard protocols used to manage accounts (such as LDAP, VOOT, SCIM, etc.) |
| |||||||
| AARC2-JRA1.4D | Guidelines for implementing, operating and using VO platforms | DROPPED 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. |
|