Users should never see error messages from the EDS. The messages described here are nearly always symptomatic of misconfiguration.
fatal.divMissing
Text: <div> specified as "insertAtDiv" could not be located in the HTML
The html page hosting the EDS has to include a named <div> and that name should be passed to the EDS code.
<div id="idpSelect">
This error indicates that name supplied in the idp_config.js file does not exist.
fatal.noData
Text: Metadata download returned no data.
This error indicates that the XMLHttpRequest get returned no data at all. It it more likely to be browser deficiency than a configuration one.
fatal.loadFailed
Text: Failed to download metadata from 'SourceURL'
This indicates that the JSON source could not be located at the supplied location. This will usually mean an incorrectly specified dataSource.
fatal.noXMLHttpRequest
Text: Browser does not support XMLHttpRequest, unable to load IdP selection data
This error indicates that the browser is not sufficiently modern.
fatal.wrongProtocol
Text: Policy supplied to DS was not "urn:oasis:names:tc:SAML:profiles:SSO:idpdiscovery-protocol:single"
The EDS only supports the default protocol version of the IdP Discovery Protocol. The SP is trying to use a different version.
fatal.wrongEntityId
Text: entityId supplied by SP did not match configuration.
If myEntityId is specified in idpselect_config.js then the EDS comparies this value with the entity ID supplied as part of the IdP Discovery Protocol and throws this error if they do not match.
fatal.noparms
Text: No parameters to discovery session and no defaultReturn parameter configured
Unless myEntityId and defaultReturn is supplied in the idpselect_config.js, then the EDS needs to be approached using the IdP Discovery Protocol. This error is thrown in case where neither is true.
fatal.noReturnURL
Text: No URL return parameter provided
Some of the Discovery Protocol was supplied to the EDS, but this did not include a return address.