Changes between Version 1 and Version 2 of ServiceProviderFederation/Discovery


Ignore:
Timestamp:
12/09/11 14:33:21 (12 years ago)
Author:
willem.elbers@mpi.nl
Comment:

--

Legend:

Unmodified
Added
Removed
Modified
  • ServiceProviderFederation/Discovery

    v1 v2  
    1 See: http://discojuice.org/
     1= CLARIN Central Discovery Service =
    22
    3 Implemented at the catalog.clarin.eu SPs, like the component registry:
     3The CLARIN central discovery service is based on !DiscoJuice (version 1.0), see: http://discojuice.org/.
    44
     5The goal is to provide an easy to use discovery service for all CLARIN service providers. By using the same discovery service users do not have to re-login or re-select their IDP when switching between service providers. A drawback of the central discovery service is the fact that it introduce a single point of failure (SPOF). Currently we are looking into ways to make this central discovery service high availability.
     6
     7= Status =
     8
     9The CLARIN central discojuice WAYF service is currently operating as a beta service.
     10
     11Currently used at the catalog.clarin.eu SPs, like the component registry:
    512http://catalog.clarin.eu/ds/ComponentRegistry/ (click on login)
     13
     14= Roadmap =
     15
     16* We plan to release version 1 of the CLARIN central discojuice WAYF service around Christmas 2011.
     17* Look into high availability options.
     18* Upgrade to !DiscoJuice 2.0
     19
     20= Configuration =
     21
     22How to use discojuice as your shibboleth WAYF?
     23
     24 1. Get access to a discojuice WAYF:
     25  a. Host discojuice yourself (see http://discojuice.org for installation instructions).
     26  b. Use an external hosted discojuice WAYF service (http://catalog.clarin.eu/discojuice/idp.html provided by CLARIN).   
     27 2. Configure a login endpoint in your SP configuration to use the discojuice WAYF service ( either 1a or 1b ), see the next section for more details.
     28 3. Use this new login endpoint
     29
     30=== !DiscoJuice login endpoint ===
     31
     32In order to use discojuice as the WAYF service, a session initiator needs to be configured in the SPs 'shibboleth2.xml' configuration file. The 'Location' attribute specifies the login endpoint you can use to append to your handler url (/Shibboleth.sso by default) to start a shibboleth session. The 'URL' attribute of the session initiator of type 'SAMLDS' should point to the discojuice installation you want to use.
     33
     34A restart of the SP is required after changing the 'shibboleth2.xml' configuration file.
     35
     36Example using the CLARIN provided discojuice WAYF:
     37{{{
     38<SessionInitiator type="Chaining" Location="/DiscoJuice" id="DiscoJuice" relayState="cookie">
     39     <SessionInitiator type="SAML2" defaultACSIndex="1" acsByIndex="false" template="bindingTemplate.html"/>
     40     <SessionInitiator type="Shib1" defaultACSIndex="5"/>
     41     <SessionInitiator type="SAMLDS" URL="http://catalog.clarin.eu/discojuice/idp.html"/>
     42 </SessionInitiator>
     43}}}
     44