This page describes how to make use of the eduTEAMS Discovery Service for your Service Provider (SP).

Discovery Service Configuration

There are multiple options how an SP can make use of the Discovery Service. The simplest one is to just redirect users to the Discovery Service URL, which we call "central discovery".

Use Central Discovery

For this very basic adoption using the eduTEAMS Discovery Service as central discovery service, everything an SP needs to know is the URL that the discovery service uses to serve SAML2 IdP discovery requests. Consult the documentation of the SAML SP product you are using on how to apply Discovery Service URL. If you are for example using the Shibboleth SP, consult the Shibboleth documentation or in case of SimpleSAMLphp the SimpleSAMLphp documentation on this topic. Generic information on the SAML2 IdP Discovery Service protocol are available in the Identity Provider Discovery Service Protocol and Profile.

...

The disadvantage of using a central discovery service is that users are redirected to another host, which has a different look and feel. Also, some users might be confused that they were sent away from the service they intended to use.

Screencast to configure Discovery Service with Sibboleth SP

The above steps are also illustrated by the screencast "eduTEAMS Discovery Service in 2 Minutes" that shows how to do this in 2 minutes with a Shibboleth SP.

Embedded Discovery

For an improved user experience and usability it is, however, recommended to go beyond the basic adoption and take advantage of the IdP filtering features and the embedded discovery. By combining these two features, a SP is able to offer an embedded discovery listing of IdPs that shows only the relevant IdPs for its user base.

...

More details on how to use this on the Embedded Discovery feature.

Filtering the IdPs shown in the list of IdPs

By default the eduTEAMS Discovery Service lists all the eduGAIN IdPs.

...