Error after succeeded authentication

Peter Schober peter.schober at univie.ac.at
Tue Jul 9 05:58:12 EDT 2013


* Gilles Badouet <badouetg at uni.coventry.ac.uk> [2013-07-09 11:41]:
> 10:04:59.061 - WARN
> [org.opensaml.saml2.binding.AuthnResponseEndpointSelector:206] -
> Relying party 'https://ans.247lib.com/shibboleth' requested the
> response to be returned to endpoint with ACS URL
> 'https://ans.247lib.com/Shibboleth.sso/SAML2/POST'  and binding
> 'urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST' however no
> endpoint, with that URL and using a supported binding,  can be found
> in the relying party's metadata

> 10:04:59.061 - ERROR
> [edu.internet2.middleware.shibboleth.idp.profile.AbstractSAMLProfileHandler:447]
> - No return endpoint available for relying party
> https://ans.247lib.com/shibboleth

That means just that: The IdP cannot find the requested endpoint in
metadata for this SP. How exactly did you add the SP's metadata to the
IdP?
https://wiki.shibboleth.net/confluence/display/SHIB2/IdPMetadataProvider

If you don't have a federation that manages IdP and SP metadata for
you it's easiest to add file based metadata to relying-party.xml and
use that for all local (or self-managed) SPs, e.g.

  <metadata:MetadataProvider id="localSPs" xsi:type="metadata:FilesystemMetadataProvider"
   metadataFile="/opt/shibboleth-idp/metadata/local-sps.xml" maxRefreshDelay="PT15M" />

This will also pick up any changes you make to this file after 15
minutes max.

> The related error message on shibd.log is:
> 
> 
> 2013-07-09 09:57:57 ERROR XMLTooling.ParserPool : fatal error on line 0, column 0, message: unable to connect socket for URL 'https://amlib.co.uk/idp/profile/Metadata/SAML'
> 
> 2013-07-09 09:57:57 ERROR OpenSAML.MetadataProvider.XML : error while loading resource (https://amlib.co.uk/idp/profile/Metadata/SAML): XML error(s) during parsing, check log for specifics

The SP failed to connect to the IdP to grab its metadata from that
URL. In short: Don't do that. Instead transfer the IdP's metadata to
the SP securely once and use file based metadata at the SP, like in
the distributed default configuration:

 <MetadataProvider type="XML" file="idp-metadata.xml"/>

Put the IdP's metadata into /etc/shibboleth and name it
"idp-metadata.xml" (or whatever, but then also adjust the file name
above).
-peter


More information about the users mailing list