Difference between revisions of "Federated AAI Implementation"
Jump to navigation
Jump to search
(Created page with "= Technical implementations of the federated AAI scenario = This page deals with the implementation of the AAI scenario in the various services. For one, we need to look into ea...") |
|||
Line 1: | Line 1: | ||
This page deals with the implementation of the AAI scenario in the various services. | This page deals with the implementation of the AAI scenario in the various services. | ||
For one, we need to look into each of the middlewares and how to hook the authentication (X.509) and | For one, we need to look into each of the middlewares and how to hook the authentication (X.509) and |
Revision as of 14:57, 1 June 2012
This page deals with the implementation of the AAI scenario in the various services. For one, we need to look into each of the middlewares and how to hook the authentication (X.509) and authorization (XACML) into them. Before that, we need to ensure that this is even possible, although at least some work in these directions is surfacing for instance in OpenStack (ADD REFERENCES!).
VM Management
OpenStack
Responsible: BHa
- Authentication
- Keystone support for PKI scheduled for the Folsom release (2012-09-27), more specifically folsom-3 http://bit.ly/LKpeI2 (2012-08-16)
- Authorization
- May be possible with alternative authZ backends to Keystone