Is this a metadata error?

[David Gersic]

I'm working here with an external vendor that I've not worked with before. We and they are both InCommon members. Other InCommon SPs work fine, so I *think* that means that my IdP is working correctly.

On the client end, I get:

Error Message: No peer endpoint available to which to send SAML response


In the Shibboleth IdP process.log file, I see this as:

10:48:14.721 - INFO [edu.vt.middleware.ldap.jaas.JaasAuthenticator:176] - Authentication succeeded for dn: uid=xxxxxxxxxx,ou=people,dc=niu,dc=edu

10:48:14.731 - INFO [Shibboleth-Access:74] - 20130523T154814Z|131.156.12.42|idp.niu.edu:443|/profile/SAML2/Redirect/SSO|

10:48:14.732 - WARN [org.opensaml.saml2.binding.AuthnResponseEndpointSelector:206] - Relying party 'https://niu.universitytickets.com/shibboleth-sp' requested the response to be returned to endpoint with ACS URL 'https://niu.universitytickets.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:48:14.733 - ERROR [edu.internet2.middleware.shibboleth.idp.profile.AbstractSAMLProfileHandler:429] - No return endpoint available for relying party https://niu.universitytickets.com/shibboleth-sp

Looking in the InCommon metadata, last updated 22 May 2013 at 4:50pm, I see an entity descriptor that is probably the one we're using:

<EntityDescriptor entityID="https://niu.universitytickets.com/shibboleth-sp" ...

in which I see:

    <md:AssertionConsumerService xmlns:md="urn:oasis:names:tc:SAML:2.0:metadata"
 Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST" Location="https://NIU.
UniversityTickets.com/Shibboleth.sso/SAML2/POST" index="1"/>

I could be wrong, but I think that's where this is going wrong. The metadata should have "https://niu.universitytickets.com" in it, not "https://NIU.UniversityTickets.com".

Right?