Federated Cloud Federated AAI
|Overview||For users||For resource providers||Infrastructure status||Site-specific configuration||Architecture|
|Scenarios:||• Federated AAI||• Accounting||• VM Image Management||• Brokering||• IntraCloud Networking|
|• Monitoring||• VM Management||• Data Management||• Information Discovery||• Security|
Integrating authentication and authorisation across multiple resource providers
|Scenario Leader||DESY||Paul Millar|
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.
There are also various technologies that support translating Federated Identity to an X.509. In general, these allow a user to authenticate with some other technology (e.g., SAML), typically within a web portal, which then has an X.509 credential with which it can interact with EGI resources:
- STS is the Security Token Service (as defined in WS-Trust) allows translating one credential type to that of a different type.
- Per-user sub-proxy is a mechanism where a robot certificate can advertise a change of identity.
- Dan Kouřil is leader of VT Federated Identity Providers Assessment
- Contrail Project Requirements on Federation Management, Identity and Policy Management in Federations
- 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