Issues getting PagerDuty which uses SAML 2.0 to talk to Shibboleth IDP.
Cahill, Charles (GE Appliances)
Charles.Cahill at ge.com
Thu Jul 9 14:26:00 EDT 2015
This handler is in place in handler.xml
<ph:ProfileHandler xsi:type="ph:SAML2SSO" inboundBinding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST"
outboundBindingEnumeration="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST-SimpleSign
urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST
urn:oasis:names:tc:SAML:2.0:bindings:HTTP-Artifact">
<ph:RequestPath>/SAML2/POST/SSO</ph:RequestPath>
</ph:ProfileHandler>
-----Original Message-----
From: users [mailto:users-bounces at shibboleth.net] On Behalf Of Cahill, Charles (GE Appliances)
Sent: Thursday, July 09, 2015 2:24 PM
To: Shib Users
Subject: RE: Issues getting PagerDuty which uses SAML 2.0 to talk to Shibboleth IDP.
The handler.xml file seems to work fine for Apache Shibboleth integrations.
It just doesn't seem to be working for this 3rd party integration ?
-----Original Message-----
From: users [mailto:users-bounces at shibboleth.net] On Behalf Of Cantor, Scott
Sent: Thursday, July 09, 2015 2:20 PM
To: Shib Users
Subject: Re: Issues getting PagerDuty which uses SAML 2.0 to talk to Shibboleth IDP.
On 7/9/15, 2:15 PM, "users on behalf of Cahill, Charles (GE Appliances)" <users-bounces at shibboleth.net on behalf of Charles.Cahill at ge.com> wrote:
>Finally, a different error :)
>
>Thank you Peter, you are the man.
>
>It is still now working, but this is finally some progress. I was giving Pager Duty the wrong Login URL as you stated.
>The new Error states this
You seem to have modified handler.xml for some reason and broken the IdP, so I guess...don't do that? I don't know of any other way you could get that error.
You also have some kind of broken style sheet reference in the error page I think.
-- Scott
--
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net
--
To unsubscribe from this list send an email to users-unsubscribe at shibboleth.net
More information about the users
mailing list