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

[Peter Schober]

* Cahill, Charles (GE Appliances) <Charles.Cahill at ge.com> [2015-07-20 05:05]:
> Everything seems to be working at this point. I have a login page,
> can login to the IDP and get authenticated.  Looks like all of the
> header info is passed as far as I can tell in SAML tracer and I get
> no errors, but then I get the following
> 
> "NetworkError: 400 Bad Request - https://ge-appliances.pagerduty.com/sso/saml/consume"
> 
> Any ideas why it sends me back to this instead of on into the application?

That's the (assumed, from their SAML 2.0 Authentication Request
message) endpoint they want the SAML response to be sent to.

Why doing that causes the above error you'll need to ask the vendor.
Be sure to provide them with the info from SAML Tracer, that will show
what kind of SAML message you sent, and where.

Since this error is not from the Shibboleth software and only happens
after authenticating at your IDP this one you will have to debug
yourself.
-peter