The goal of this pilot is to onboard the CTA community on federated identity in a larger, broader meaning - moving from a stand-alone solution based on IdP to a fully federated one as a possible long term goal. In the meanwhile, short terms goals for the pilot are the implmentation of the TIER-like components ( COMANAGE, GROUPER) and a IDP/SP proxy to work in a synergic way for the CTA AAI.
Identity linking between the IDs of the current standalone CTA IDP and the eduGAIN ones are a relevant goal for this pilot.
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?
Main objective of this section is to report detailed informations about pilot.
Some questions:
How this pilot works
Reason to prefer this pilot instead of other existing tool
Detailed Scope
others
This section will contain a lists of components used for this pilot and why they were chosen instead of others
It is not required to add a detailed description for each component, but 2 important parts are:
An example:
CTA Pilot use different components to achieve its goal:
| Name | Link | Description | Why |
|---|---|---|---|
| Grouper | https://www.internet2.edu/products-services/trust-identity/grouper/ | Grouper is an enterprise access management system designed for the highly distributed management environment and heterogeneous information technology environment common to universities. Operating a central access management system that supports both central and distributed IT reduces risk. | |
| COmanage | |||
| SaToSa |
This section will provide 2 important parts:
Graphic representations of pilot architecture
Graphic representations of workflow
This section should explain how this pilot works through use cases (at least 2).
(Here's a valid example LINK)
Last part contain a list of information, link or anything related to the pilot that was not mentioned in ahead seciton.