...
A priority for WLCG was not to reinvent the wheel, following the FIM4R recommendation to re-use shared components. Two solutions have been identified as possibilities and are currently undergoing developments; EGI-Check-in and INDIGO IAM. Both solutions have multiple reasons for enhancing their services and as such the decision was made to continue with the two options in parallel. The EGI-Check-in pilot is being driven by AARC, with RCAuth integration covered as a collaboration between the developers behind EGI-Check-In and INDIGO IAM.
The goal is to provide a self-contained AAI pilot solution that enables token based authentication and authorisation for WLCG. The two pilot services will be developed in parallel, assessed and a recommendation made to the community. Such a solution will be of wider benefit to user communities also looking to move away from x509 based authentication and authorisation, and developments in INDIGO IAM and EGI-Check-in will be relevant for a larger audience.
...
The components are as follows:
| Component | Description | Why did we choose it? | Link |
|---|---|---|---|
| RCAuth | Token Translation. Used to generate x509 certificates for access to legacy services | EU wide, sustainable infrastructure component | https://rcauth.eu |
| VOMS | Attribute Authority & Membership Management. Legacy authorisation database for WLCG, must be integrated for backwards compatibility | Pre-existing. Backwards compatibility | https://italiangrid.github.io/voms/ |
| CERN HR DB | Attribute Authority. CERN's source of identity vetting information | Pre-existing. Backwards compatibility | N/A |
| INDIGO-IAM | One option for the proxy and membership management component | Implements multiple components, easier maintenance. Product used by other communities. | https://www.indigo-datacloud.eu/identity-and-access-management |
| EGI-Check-in | The second option for the proxy and membership management component | Implements multiple components, easier maintenance. Product used by other communities. | https://www.egi.eu/services/check-in/ |
Architecture
The architecture includes every component of the AARC BPA.
...
AARC BPA version:
Use Cases
(TBC, screenshots will be available in December) Videos for the AARC supported pilot for EGI-Check-in are available at link
User links x509 certificate with federated credentials
| Step |
|---|
| Screenshots |
|---|
| User registers with the system using a federated account |
 | |
| User associates x509 user certificate with their account |
|
User submits a physics job
| Step | Screenshot (TBC) |
|---|---|
| User |
| follows registration flow above | |
| User requests token from command line |
| (Device Code Flow) |
|
| User submits a |
| job in the normal way |
Demo EGI Check-in videos
The various functionalities provided by EGI Check-in are available through mini videos demonstrating the below functionalities/flows:
- Trying to add a non-WLCG experiment member into the system
- Adding a WLCG Experiment member into the system( Create the user, obtain an RCAuth certificate, register into VOMS)
- Group management
- HRDB periodic syncing
- Invite multiple people via email from an administrator's account
- SSH key authentication for RCAuth proxy retrieval
- Token exchange and device code
Visit the following link to view.
Further information
AARC's specific role in this pilot is to coordinate the efforts, ensure that AARC recommendations are considered and to support the enhancement of EGI-Check-in.
Was BPA useful to achieve this results? how?
About sustainability:
will this pilot survive after AARC?WLCG is looking at two existing AAI solutions that are broadly in line with the BPA already.
Sustainability? The aim of this pilot is to provide a recommendation for WLCG to deploy a BPA compliant AAI. This will be physically hosted at CERN. The pilot is directly useful in providing prototypes, proof of concept, and demonstrations.