Issues getting PagerDuty which uses SAML 2.0 to talk to Shibboleth IDP.

[Cahill, Charles (GE Appliances)]

It looks to me like the IDP is trying to post the handler info on port 80 instead of 443.

That would be a problem I believe.

-----Original Message-----
From: users [mailto:users-bounces at shibboleth.net] On Behalf Of Cantor, Scott
Sent: Thursday, July 09, 2015 2:32 PM
To: Shib Users
Subject: Re: Issues getting PagerDuty which uses SAML 2.0 to talk to Shibboleth IDP.

On 7/9/15, 2:26 PM, "users on behalf of Cahill, Charles (GE Appliances)" <users-bounces at shibboleth.net on behalf of Charles.Cahill at ge.com> wrote:

>This handler is in place in handler.xml

Then I have no idea what to tell you. I couldn't imagine you'd changed it, but that's what the error means. If something upstream were in the way of the requests to that path, the error wouldn't be in the IdP log. Maybe there's a weird character embedded on one end or the other.

-- Scott

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