This section describes the Centralized Discovery Service, which is primarily intended for use by identity federations and other large groups wishing to providing a backstop discovery service. Outside this scope, it is very limited. Individual service providers, in particular, are recommended to install the Embedded Discovery Service.
Before You Begin
The first question you should ask is whether you need to install the DiscoveryService. If you're working in a non-Java environment, you may find it easier to build a selection page in a more native fashion. The SP also supports the Embedded Discovery Service which is usually a better choice for SPs which need to implement discovery.
If you do decide to install this service, you'll need to collect the metadata sources that will contain the IdPs that users will select from. If you're planning to use SAML 2.0 or other protocols not supported by the old WAYF model, you may also need to provide metadata about your SPs to enable the DS to safely interact with the SP.
The Discovery Service will automatically handle both the legacy Shibboleth AuthnRequest message (so-called "WAYF mode") and the full Discovery Service Protocol.
No explicit configuration is required to select the right protocol.
The Shibboleth Discovery Service, version 1.2.1, is a standard Java web application.
endorseddirectory to the appropriate place on the web Server (for tomcat this is
install.sh(on Unix systems) or
install.bat(on Windows systems) as a suitably authorized user. This user must have the ability to create the Discovery Service home directory identified in the previous step.