Page tree

Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: mostly clarifications, typos

Installing the Centralized Discovery Service

Note

This section describes the Centralized Discovery Service, which is primarily aimed at intended for use by identity federations and other large groups wishing to providing a backstop service for Federation and other metadata aggregating and distributing agencesdiscovery service. Outside this scope, it is very limited. Service Providers Individual service providers, in particular, are recommended to install the Embedded Discovery Service.

...

If you do decide to install itthis service, you'll primarily 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 SP(s) SPs to enable the DS to safely interact with the SP.

Which

...

Protocol?

The Discovery Service will automatically select between handle both the legacy Shibboleth AuthnRequest message (so-called "WAYF -Mode" (in which it intercepts and handles a legacy Shibboleth AuthnRequest messagemode") and the full Discovery Service Protocol.

No explicit configuration is required to select the right protocol is needed.

Performing the Install

The Shibboleth Discovery Service, version 1.2.1, is a standard Java web application.

  1. Download and decompress the Discovery Service package from the Shibboleth Download site.
  2. Change into the newly created distribution directory.
  3. Endorse Xerces and Xalan by copying the contents of the endorsed directory  directory to the appropriate place on the web Server (for tomcat this is $TOMCAT_ROOT\common\endorsed).
  4. Run either install.sh (on Unix systems) or install.bat (on Windows systems) as a suitably authorized user user. This user must have the ability to create the Discovery Service home directory identified in the previous step.
  5. Configure the Discovery Service to point to the metadata sources you identified above as described here.
  6. Deploy the Discovery Service .WAR file, located in the Discovery Service's Home directory.
  7. Further Configuration configuration is described here.