Versions Compared

Old Version 7

changes.mady.by.user Rod Widdowson

Saved on

compared with

New Version 8

changes.mady.by.user Rod Widdowson

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Clear up dcoumentation in respect of case sdsj-79

...

This error is most usually caused by a malformed URL. This in turn is usually caused by an invalid specification of a file name in a <MetadataProvider> element. The

Note

Under windows, the correct format is

...

file:\\\c:\dir\subdir\file.ext

Couldn't find endpoint URL in metadata

...

Code Block
<DiscoveryResponse
  xmlns="urn:oasis:names:tc:SAML:profiles:SSO:idp-discovery-protocol"
  Binding="urn:oasis:names:tc:SAML:profiles:SSO:idp-discovery-protocol"
  Location="https://host.domain/Shibboleth.sso/DS"
  index="1"/>

Note that the Discovery service needs to have access to the metadata for the SP that it discovering for as well as the metadata for all the IdPs.

edu.internet2.middleware.shibboleth.wayf.plugins.provider.BindingFilter: badly formatted binding

...