If available, add pilot logo
Pilot Description
Some questions to answer:
What are the goals of this pilot?Why is it in AARC project?
How this pilot will improve AARC community?
Why should I use this pilot instead of other solutions?
The goal of this pilot is to provide a non-invasive solution to simplify access to CTA services from eduGAIN and the CTA community.
CTA pilot should provide a solution to CTA administrator that does not upset the mechanisms in use, because they are well known.
With this pilot, new features will be introduced:
- Self service registration under administrator approval
- Account linking solution, under administrator approval
- Simple integration and transparency to any future CTA service.
Identity linking between the IDs of the current standalone CTA IdP and the eduGAIN ones are a relevant goal for this pilot.
A long term goal of this pilot is to move CTA community from a stand-alone solution based on IdP to a fully federated one.
This pilot perfectly fits with AARC's goals:
- It helps to solve issues related to authentication from different IdPs but logically related to the same scientific community
- The proposed solution uses only existing technologies, without the need to creating new ones
- It does not change the global approach for the CTA community
Even if this pilot proposes a solution for the CTA community, its components high flexibility allow to change configuration, so every scientific reality that needs this solution can adapt it to their community, to fit their needs of authentication and authorization.
This part describes pilot's test phase, emphasizing progress and results.
The main objective is that a reader can easily understand the benefits achieved by using this pilot. Some examples or brief use cases are recommended.
Some questions to be answered:
Have you achieved your goals?
Any planned improvements for future releases?
