For configuration instructions for COmanage Registry v0.9.4 and earlier, see Configuring the Shibboleth Embedded Discovery Service Plugin (0.9.x).
If you have chosen to use a SAML2 service provider (SP) for authentication to the Registry and you expect users to want to use more than one login server (identity provider or IdP), you will most likely want to use a SAML2 discovery service to help users choose which IdP to use for login.
COmanage Registry includes a Shibboleth Embedded Discovery Service (EDS) that you may choose to use as the discovery service. Customization is via Platform > CMP Enrollment Configurations. The default COmanage EDS assumes the discovery service feed is available at
/Shibboleth.sso/DiscoFeed. For more information on the EDS, see the EDS documentation.
The discovery service URL is
If you are using a Shibboleth Native Service Provider (SP) you can configure the SP to use the discovery service by configuring the discoveryProtocol and discoveryURL attributes for the <SSO> element. For example