Table of Contents |
---|
Participants
Panel | ||||
---|---|---|---|---|
| ||||
|
Panel | |||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||
|
Panel | ||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||
|
Activity Overview
Panel | ||
---|---|---|
| ||
This T&I work package continues the work on IdP discovery as it was started in GN4-2 in the eduTEAMS and IdP Discovery subtask. It gathers requirements, and works with the RA21 initiative towards an implementation that can become a service in the GEANT project. At the same time it helps handing over the existing eduTEAM Discovery Service to the new (GN4-3 WP5 T1) eduGAIN service. |
Panel | ||
---|---|---|
| ||
There are two primary goals:
|
...
Panel | ||
---|---|---|
| ||
See eduTEAMS DSX Discovery documentation pages: Discovery Service Earlier discussion from Licia: "Dear all, Last week in Milan I had a chat with Slavek about CESNET discovery service. We agreed that we it would make more sense to look at a discovery service in the context of eduGAIN. Slavek and I agreed that the current pilot with CESNET service was not really advertised so it's difficult to gather inputs on the satisfaction of the services that used it. In agreement with Marina, we will fund another pilot with CESNET discovery with defined goals where we will ask for inputs and/or requests for new features. The pilot will have a limited duration of about 6 months. The pilot, in agreement with Niels, should go under the incubator and after the defined period we should assess the usability and satisfaction and see which features should be implemented. We have planned a similar pilot also for RA21. I will ping Slavek privately to define further details." |
Activity Details
Panel | ||
---|---|---|
| ||
The current eduTEAMS DSX Discovery Service (will be renamed to eduGAIN was initially called eduTEAMS Discovery Service most likely) is operated on httphttps://discoverydsx.eduteamsedugain.org (several physically distributed servers) and a test instance on httphttps://dsdsx-test.eduteamsedugain.org/. Its software is the CESNET SAML2 Discovery Service implementation (PHP). Even though the service is not considered yet a production service according to the GEANT PLM (because it is neither part of the eduTEAMS or nor eduGAIN service currently), the service has been operated as managed service on the same production hardware by CESNET that CESNET uses for their own production Discovery Service. The three main features that distinguish this implementation from others are:
The Discovery Service documentation (for SP administrators) is on the GEANT wiki. The RA21 prototype Discovery Service (special branch based on pyFF, python) has been developed by Leif Johansson (SUNET) with and for the RA21 project. A prototype of the user interface is available on the pyFF nightly instance. It demonstrates an example user interface that was invested quite some work in together with RA21 UI experts and that was mostly created with the RA21 target services (login on publisher web sites) in mind. |
...
Panel | ||
---|---|---|
| ||
The eduTEAMS DSX Discovery service (to be renamed and moved) already has a Privacy Policy. Its implementation (by CESNET) is already very privacy aware compared to other discovery service implementations. |
...
Panel | ||
---|---|---|
| ||
This activity is successfully finished when:
Please describe here the set of criteria that the product must meet in order to be considered finished. <Enter here> |
Panel | ||
---|---|---|
| ||
The discovery pilot will be handed over to T1 eduGAIN for the purpose of making it a production service Most likely, the RA21 work continued in this cycle will not be complete. Ideally, this cycle is followed by another cycle with similar staff member and a better understanding of the RA21 service. |
...
Activity Results
Panel | ||
---|---|---|
| ||
Please provide pointers to completed and intermediary results of this activity |
Meetings
Date | Activity | Owner | Minutes |
---|---|---|---|
Feb 14, 2017 | Kickoff meeting | ||
...