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

[Cantor, Scott]

On 7/17/15, 6:47 PM, "Cantor, Scott" <cantor.2 at osu.edu> wrote:
>
>Why do you have endpoints in the metadata that are specific to a Shibboleth SP? There's no chance this is a Shibboleth SP.

Putting 2 and 2 together, I'm going to guess that the reason the metadata's wrong *and* has endpoints that make no sense is that you didn't actually create metadata for this SP, you copied metadata from an example for Shibboleth and just used it unchanged. You can't do that.

The endpoint it's asking for is obviously the one it expects to use, so you need to create an AssertionConsumerService element with that location and the proper binding constant and get rid of all the ones you left from the example that's not applicable.

And to head off the next round, that's not enough. If the SP has a decryption key, then you need to put it in the metadata appropriately for the IdP to consume. If it doesn't, which is likely, then you need to turn off encryption, probably by creating or extending a RelyingParty override in the IdP configuration. [1]

-- Scott

[1] https://wiki.shibboleth.net/confluence/display/SHIB2/IdPXMLSigEnc