Error after authentication: No peer endpoint available to which to send SAML response

[Peter Schober]

* Andrej Gregorka <Andrej.Gregorka at ixtlan-team.si> [2015-04-13 16:47]:
> <samlp:AuthnRequest
>     AssertionConsumerServiceURL="https://netshib.ixtlan-dev.si/Shibboleth.sso/SAML2/POST"
>     Destination="https://netshib.ixtlan-dev.si:8443/idp/profile/SAML2/Redirect/SSO"
>     ID="_5137de30e536fce539345aacbba9ffe0"
>     IssueInstant="2015-04-13T14:24:33Z"
>     ProtocolBinding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST"
>     Version="2.0" xmlns:samlp="urn:oasis:names:tc:SAML:2.0:protocol">
>     <saml:Issuer xmlns:saml="urn:oasis:names:tc:SAML:2.0:assertion">https://netshib.ixtlan-dev.si:8443/idp/shibboleth</saml:Issuer>
>     <samlp:NameIDPolicy AllowCreate="1"/>
> </samlp:AuthnRequest>

The Issuer of the AuthnRequest (i.e., the SAML SP) calls itself
https://netshib.ixtlan-dev.si:8443/idp/shibboleth which would hint at
a misconfigured SP, thinking its name is that of the IDP.

Unrelated to that error but there's also no reason to include port
numbers in entityIDs, these are just names to uniquely identify an
entity. (If you changed the entityID you'd have to change the metadata
each party has on record for that entity, too, of course.)
-peter