Pilot Description

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.

Pilot goals

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?

Description

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

Components

This section will contain a lists of components used for this pilot.

It is not required to add a detailed description for each component, but 2 important parts are:

1. Add Link to component web page
2. Add a short description to explain its function (not more than 1 raw)

An example:

• Component A - Service provider
• Component B - Bring order to chaos
• Component C - Hide my precious treasure

Architecture

This section will provide 2 important parts:

• Graphic representations of pilot architecture

• Graphic representations of workflow

• Lists of all components of related pilot and why they were chosen instead of others

Pilot include different services, those are:

• Grouper
• COmanage
• SaToSa

Use Cases

This section should explain how this pilot works through use cases (at least 2).