...

1. Introduction

This page serves as a reference for the requirements gathered in DJRA1.1.

2. Requirements

2.1 (From: DJRA1.1 Section  5.1) Architectural and Technical Requirements:

R1 User and Service Provider friendliness  

...

Source: TERENA AAA, ELIXIR  

2.2. (From: DJRA1.1 Section 5.2) Policies and Best Practises  

R_P_1  Policy harmonisation  

...

Type: Serviceability/Supportability  

Source: EUDAT  

3. Grouping

This is a try to group the above requirements by different parameters

3.1 By Type

Usability

R1 User and Service Provider friendliness

...

R_P_7  Best practises for terms and conditions  

3.2 By Category

Guest Identities / Levels of Assurance

...

R2  Homeless users 

R3  Different Levels of Assurance 

...

R17  Integration with e-­Government infrastructures 

User Identification

 R8  Persistent user identifiers  

 R9  Unique user identities  

 R10  User-­managed identity information Source:  

...

Attributes: Groups and Authorisation

 R4  Community-­based authorisation  

 R5  Flexible and scalable attribute release policies  

 R12  User groups and roles  

 R_P_5  Semantically harmonised identity attributes  

Attributes: Release

R6  Attribute aggregation / Account linking 

R_P_3  Sufficient attribute release

Technology requirements

...

R7  Federation solutions based on open and standards-­based technologies  

 

R14  Browser & non-­browser based federated access  

 

R15  Delegation

Privacy, legal issues, and policies

R10  User-­managed identity information Source:  

R18  Effective accounting    

R_P_1  Policy harmonisation    

R_P_2  Federated incident report handling  

R_P_7  Best practises for terms and conditions 

Training

 R1 User and Service Provider friendliness  

 R_P_4  Awareness about R&E federations  

 R_P_6  Simplified process for joining identity federations  The bureaucracy involved in joining identity federations should be reduced