Difference between revisions of "Fedcloud-tf:WorkGroups: Federated AAI"
Jump to navigation
Jump to search
Line 38: | Line 38: | ||
*[[Federated AAI Ideas]] | *[[Federated AAI Ideas]] | ||
*[[Federated AAI Requirements]] | *[[Federated AAI Requirements]] | ||
*[[Federated AAI Survey of Credential Services]] | |||
<br> | <br> |
Revision as of 09:46, 7 January 2014
Main | Roadmap and Innovation | Technology | For Users | For Resource Providers | Media |
Integrating authentication and authorisation across multiple resource providers
Leader: Bjoern Hagemeier, FZJ
Collaborators
Role | Institution | Name |
---|---|---|
Scenario leader | 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 wich 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