...
- Aggregating the attributes provided by the IdP and the attribute authorities the IdP Proxy acts as a single point of access for the Service Providers,and this makes the configuration for the SP easier
- Easy to add new attribute authority tools or new IdPs to the pilot, without the need to re-configure any endpoint besides the proxy
- On a production enviroment, the proxy can control the attributes and entitlements that are provided to the services
- For the authorization, services expect to receive certain attributes and entitlements with values in a given format
- Uniform attributes semantic and syntax across multiple communities/infrastructures will never happen
- Funnelling all AuthN AuthZ information through an IdP/SP proxy allows to rename/edit/control the attributes
- Idp Proxy can provide the group information in a different syntax than stored the one used by the communities, making easier for the
On the Service Provider side, we can test the user authentication and authorization implementation on a widely deployed cloud framework by using federated identities:
In the service provider Federated AAI has been used in the following configuration:
- Ephemeral users: the usern is not pre-configured in the SP, but usernames are created using the user UID provided by the Idp
- The
- it is not necessary creating local accounts for the users; ephemeral ones will be used
- the access to the resources is regulated by the entitlements released by the IdP proxy and provided by one of the attribute authorities. Users are mapped into groups pre-configured in the service provider.
The current status of this work has been presented at the general AARC meeting in Utrecht in May 2016. See this Slide presentation for more details. SA1.2 Pilots. Updates
...