This usually only needs editing for complex deployments
A single discovery service implementation can have multiple handlers. Each handler can have a different look and feel (as described inDSUIEdit) and can display the relevant data in different ways. This is all controlled by making changes to the
wayfconfig.xml file. This file consists of the following parts:
The default behavior is defined in the
<Default> element. The following attributes or elements can be changed:
A metadata source is often a description of a federation. The details on how to do add
<MetadataProvider> elements are given in DSAddMetadata.
The general mechanism for defining plugins is described in DsPlugIn.
One plugin is defined in the distribution. This plugin controls the cookie that is used to remember previous selections. The name and value format of the
_saml_idp cookie conforms to the Identity Provider Discovery Profile.
<Plugin> element has the following attributes:
<Plugin>, which allows the deployment of a handler which deletes any memory the user may have. (Default: false)
Each handler is defined via a
<DiscoveryServiceHandler> element. As well as the attributes and elements described for the Default configuration (and which, if specified override the default), each DiscoveryServiceHandler MUST have a location attribute.
The default web.xml specifies that "/WAYF" and "/*.wayf" are the possibilities for DiscoveryServices. If a URL matches the above, but does not match any location in a DiscoveryServiceHandler, then the first handler for which the default attribute is set true is invoked. The web.xml built into into the war file should not be changed unless you have to change the end points that it uses.
In addition the
<DiscoveryServiceHandler> may contain the following subelements:
<MetadataProvider>elements provide metadata to to this handler. If no
<Federation>elements are present, then all of the
<MetadataProvider>elements are used.
<Plugin>elements are associated with this handler.