...
| 1. | Access to CTA Science Gateway to perform scientific analysis of CTA DATA |
|
| 2. | The user is redirected to the Discovery Service embedded into the SAtoSA proxy |
|
| 3. | User select an IdP and login with his own credential |
|
| 4. | User submit a petition to CTA Administrator to enroll to the collaboration |
|
| 5. | The user should wait for the approval from the CTA Administrator |
|
Access to CTA SP with an approved CO person
| 1. | Access to CTA Science Gateway to perform scientific analysis of CTA DATA |
|
| 2. | The user is redirected to the Discovery Service embedded into the SAtoSA proxy |
|
| 3. | User select an IdP and login with his own credential |
|
| 4. | Overview of attributes being shared (to authenticate and perhaps authorize). |
|
| 5. | The user is successful redirected to CTA Analysis tools |
|
CTA Administrator approve user petition
| 1. | CTA Administrator access to COmanage registry to approve CO petition |
|
| 2. | CTA Administrator view CO Petition and click "Approve" to confirm user self-signup to the collaboration |
|
| 4. | CTA Administrator add the user to the proper Groups |
|
CTA Administrator links identities
| 1. | User ask to CTA Administrator to link a CTA identity with a non CTA identities | |
| 2. | CTA Administrator access to COmanage registry |
|
| 3. | CTA Administrator select to relink the non CTA Organizational Identities |
|
| 4. | CTA Administrator select the User CTA Identity to link with |
|
| 5. | Now the 2 Oranizational Identities are linked in the same CO Person |
|
Further information
Given the positive result of the pilot, CTA is evaluating the possibility of moving this pilot from the experimental phase to production, maintaining it and offering this service to the whole community
Further information
Last part contain a list of information, link or anything related to the pilot that was not mentioned in ahead seciton.