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

[Kevin Foote]

> On May 29, 2015, at 9:01 AM, Cahill, Charles (GE Appliances) <Charles.Cahill at ge.com> wrote:
>  
>               I am having some major issues getting PagerDuty to talk to our Shibboleth IDP.
>               I am very confused about the fact that all PagerDuty asks for in its configurations is the
>               Shibboleth login page and cert info.  There is not metadata for me to retrieve and obviously
>               I am not installing the Shibboleth Service Provider in this case.  Does the IDP need to be set
>               To Anonymous Relying Party  and if so, I cannot find much documentation on how to get these      
>               guys to talk.   Any help would be greatly appreciated.

Hi Charles,


Many of these ‘newish’ SaaS solutions do the bare minimum of getting you squared away with a SAML2 exchange. For the most part they want you to 
take the parts of your idp-metadata.xml file and input them into their setup form. 

I’ve never messed with pagerduty so milage-may-very on the below but, they have docs and you can basically follow the OneLogin or Ping docs. 
(Follow the Ping doc)

Using Shib your SSO URL will be something to the effect of 

https://<yourIDP>/idp/profile/SAML2/POST/SSO

Your cert will be in your credentials directory or also found in your idp-metadata.xml file. You will most likely not have a SLO URL unless you have done something local. 

For the RP registration you can mock up the metadata on your end .. or look at the ping doc and I think that should explain more.. 


--------
thanks
 kevin.foote