Fedcloud-tf:WorkGroups: Federated AAI

Main

Roadmap and Innovation

Technology

For Users

For Resource Providers

Media

Workbenches:

Open issues

Scenario 1 VM Management

Scenario 2 Data Management

Scenario 3 Information Systems

Scenario 4 Accounting

Scenario 5 Monitoring

Scenario 6 Notification

Scenario 7 Federated AAI

Scenario 8 VM Image Management

Scenario 9 Brokering

Scenario 10 Contextualisation

Scenario 11 Security

Integrating authentication and authorisation across multiple resource providers

Leader: Bjoern Hagemeier, FZJ

Collaborators

Role	Institution	Name
Scenario Leader	DESY	Paul Millar
Collaborator	FZJ	Bjoern Hagemeier
Collaborator	CESNET	Dan Kouřil

Scope

We have already defined that user authentication should be based on X.509 certificates rather than usernames and passwords or other credential material. Nevertheless, depending on the type of federation intended, this may not even be a real requirement. Any service should rely on an identity provider that is in charge of the type of credentials used for authentication.

For the technical implementations of this scenario, please go to Federated AAI Implementation.

A quick overview of AAI support in technologies and providers, as well as the specific settings for FCTF can be found at Federated AAI Integration Status.

Quick links

• Federated AAI Roadmap
• Federated AAI Integration Status
• Federated AAI Configuration
• Federated AAI Implementation (merge with Configuration?)
• Federated AAI Ideas
• Federated AAI Requirements
• Federated AAI Survey of Credential Services

Liaisons

• Dan Kouřil is leader of VT Federated Identity Providers Assessment
• Contrail Project Requirements on Federation Management, Identity and Policy Management in Federations