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-06-01 18:27]:
> I am able to authenticate just fine, but continue to get “No Relying
> Party” as seen in below logs not sure why Anonymous relying party is
> not kicking in, as I have no entityID listed in my metatdata for the
> pagerduty URI.  The only information PagerDuty asks for is the Cert,
> and lDP login URI if you just select SAML2.0 option.

Instead of sending profile data about your subjects to any SP in the
world that asks your IDP for it (by adding usable SAML profiles to the
anonymous relying party) you should create minimal SAML SP metadata
for the service, based on what you have.

You get the correct entityID from your process log, or by grabbing it
from the browser during a login attempt (easiest with Mozilla Firefox
and the SAML tracer extension). From their docs it seems the entityID
is always "your-account.pagerduty.com" and the ACS URL for HTTP-POST
is then https:// + entityID + /sso/saml/consume, which would make the
a minimal entity descriptor like this:

  <EntityDescriptor entityID="general-electric.pagerduty.com">
    <SPSSODescriptor protocolSupportEnumeration="urn:oasis:names:tc:SAML:2.0:protocol">
      <AssertionConsumerService Binding="urn:oasis:names:tc:SAML:2.0:bindings:HTTP-POST"
        Location="https://general-electric.pagerduty.com/sso/saml/consume" index="0"/>
    </SPSSODescriptor>
  </EntityDescriptor>

And configure attribute resolving and release for this like for any
other SP in your locally managed metadata.

Kevin already tried to answer the info they wanted from your IDP.
-peter