Introduction
The purpose of the demonstrator is to show with a practical implementation how the group membership attributes or other attributes from multiple sources can be used in a federated environment to regulate access to services.
The use of COmanage, as an attribute authority, for managing the users’ attributes allows to regulate the authorization on services based on externally provided attributes. Such service can be entirely managed by the research community, independently from service providers or identity providers. The use of an attribute aggregator simplifies the configuration at both service provider and attribute authority level. Acting as an IdP proxy, the attribute aggregator is the only entity that needs to be configured in the service provider for authentication and authorization data provisioning.
Detailed description
A detailed description can be find in this wiki page.
The setup consist of:
- an IdP proxy on SimpleSAMLphp
- a COmanage server (configured as service provider) as aggregation service
- a cloud framework (OpenStack) as service provider.
It was used a set of dummy users registered in the testbed IdP. In COmanage it was created some collaborations (CO) which have a corresponding project into OpenStack in order to map properly the users.
There was no need to create local accounts on the cloud framework, ephemeral users are using instead: it was created a set of mapping rules that, depending on the entitlements provided by COmanage (ownership to the COs with a precise role), associate the external users to the right group defined into openstack, and each of them can access to as particuale OpernStack project with different rights (either admin or simple user).
Schema
TBA
... workflow
to show through a screenshots serie how the users are properly mapped to a particular project in OpenStack depending on the COs membership in COmanage
add also an explanation how the mapping rules work
| a) some research collaborations who want to access to the OpenStack services were created on a COmanage instance. In our case: | ||
| aarc-white.pilots.aarc-project.eu | aarc-yellow.pilots.aarc-project.eu | aarc-blue.pilots.aarc-project.eu |
|---|---|---|
 |  |  |
b) Each CO has got an admin who approves the membership requests c) There are some users registered d) Each CO has got a corresponding project into OpenStack, reserved to its members | ||
| 1. | ||
|---|---|---|
| 2. | Access OpenStack's Dashboard (Horizon) at https://am02.pilots.aarc-project.eu/horizon Select "External suthentication and login" and click on "Connect".
|  |
| 3. | Select your Identity Provider from the discovery page (WAYF). The institutional IdP to select (considered for demo purposes only) is: AARC DIY Identity Provider |  |
| 4. | Enter your login credentials to authenticate yourself with the IdP of your Home Organisation. We will show three cases: a) an user belonging to aarc-yellow CO with admin role b) an user belonging to aarc-yellow CO with no particular roles c) an user belonging to aarc-blue CO with admin role |  |
| 5a. | personal information consensus |  |
| 6a. | successfully access |  |
| 5b. | personal information consensus |  |
| 6b. | successfully access |  |
 | ||
 | ||