No Peer Endpoint...

[Paul Hethmon]

Look at the SP metadata file you load at the IdP. You will find it does
not have that endpoint in it. Also note that the ACS endpoints have to
match on both binding and URL. So you need one in the file with:

binding:  urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST
acs url:  https://sp.zzz.com/Shibboleth.sso/SAML2/POST

Paul

On 4/5/13 8:35 AM, "Dominic Forrest" <dom.forrest at gmail.com> wrote:

>==> idp-process.log <==
>23:45:05.995 - INFO [Shibboleth-Access:74] -
>20130404T224505Z|192.168.3.12|idp.zzz.com:443|/profile/SAML2/Redirect/SSO|
>23:45:05.996 - WARN
>[org.opensaml.saml2.binding.AuthnResponseEndpointSelector:206] - Relying
>party 'https://sp.zzz.com' requested the response to be returned to
>endpoint with ACS URL 'https://sp.zzz.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
>23:45:05.997 - ERROR
>[edu.internet2.middleware.shibboleth.idp.profile.AbstractSAMLProfileHandle
>r:429] - No return endpoint available for relying party https://sp.zzz.com
>
>so it is clear I have a metadata error which I believe to be on the SP?
>