Discovery Service Configuration

The eduTEAMS Discovery Service URL serves to discovery requests of the SPs.

eduTEAMS Discovery Service URL

https://discovery.eduteams.org/wayf.php

The protocol is described in Identity Provider Discovery Service Protocol and Profile. On how to apply the Discovery Service URL in your product you should consult the documentation of the product itself, in most cases Shibboleth SP documentation or SimpleSAMLphp documentation.

Filtering IdPs

By default eduTEAMS Discovery Service lists all the eduGAIN IdPs for a eduGAIN SP using the service. SP may reduce the list by Filtering IdPs.

Embedded discovery.

Discovery may be used also in embedded fashion. For that to work authentication needs to be triggered from a page that includes javascript that provides the functionality. Here we provide examples for Shibboleth SP and SimpleSAMLphp.

Shibboleth SP

This example relies on having eduTEAMS discovery set as default login handler discovery service.

file:/etc/shibboleth/shibboleth2.xml

<SSO
    discoveryProtocol="SAMLDS" 
    discoveryURL="https://discovery.eduteams.org/wayf.php">
    SAML2 SAML1 
</SSO>

If you use the discovery in embedded fashion you need to include javascript in head element on the page triggering the authentication,

Including javascript

<head>
    <!-- HTML elements -->
    <script type="text/javascript" src="https://discovery.eduteams.org/ds.js"></script>
    <!-- HTML elements -->
</head>

and then display the element itself that triggers the authentication as defined in default handler.

Login element

<a href="/Shibboleth.sso/Login" onclick="startOverlay(event)">Log in</a>

As a result the discovery is shown in embedded fashion.

SimpleSAMLphp

This example relies on having eduTEAMS discovery set as default sp discovery service.

authsources.php

'default-sp' => array(
    'saml:SP',
    'entityID' => 'https://sp.example.com/simplesaml/',
    'idp' => NULL,
    'discoURL' => 'https://discovery.eduteams.org/wayf.php',
    'privatekey' => 'example.key'
),