No peer endpoint available to which to send SAML response

[Dave Vernon]

>Your entityId does not need to go in the <SSO> section. The IdPs entityId goes there.

That actually is the entity ID for the IdP.  (IdP is expode.lcaat.ca and SP is lms.lcaat.ca)

>Your web server is not responding how you think it is.
I know Scott hasn't had a crack to reply to the last message to him, but any advice on what to look for there?



________________________________________
From: users-bounces at shibboleth.net [users-bounces at shibboleth.net] on behalf of Kevin Foote [kpfoote at uoregon.edu]
Sent: Wednesday, October 01, 2014 7:23 PM
To: Shib Users
Subject: Re: No peer endpoint available to which to send SAML response

On Oct 1, 2014, at 4:04 PM, Dave Vernon <dvernon at loyalistcollege.com> wrote:
> In shibboleth2.xml on the SP server I have this:
> <ApplicationDefaults entityID="https://explode.lcaat.ca/idp/shibboleth"
> and further down
> <SSO entityID="https://explode.lcaat.ca/idp/shibboleth"
>                 discoveryProtocol="SAMLDS" discoveryURL="https://ds.example.org/DS/WAYF">
>              SAML2 SAML1
>            </SSO>

Your entityId does not need to go in the <SSO> section. The IdPs entityId goes there.

> I want to call out the discovery URL there.  From what I understand, since I am only dealing with 1 IdP I don't need to define that?  Is that correct?

You should not need the DS unless you are using a/the discovery service.
(Unless you need it that is)

> Item #3:
> The webserver itself is the part that is most familiar to me,

Like Scott said this is the main part you need to get straight.
Your web server is not responding how you thin it is.


--------
thanks
 kevin.foote
--
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net