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

[Peter Schober]

a* Cahill, Charles (GE Appliances) <Charles.Cahill at ge.com> [2015-06-01 20:56]:
> I understand it and have added it to my "gealidp.xml" metadata file.
> 
> Which currently contains multiple Entity Desriptors.
> 
> I am still getting the Relying Party not found error though in the
> logs for my container.

Container logs are not sufficient. The Shibboleth IDP will write its
own detailed log files, by default to $IDP_HOME/logs/idp-process.log

That's where you'd take the entityID for the SP from (or from the
browser). I've said that before, of course.
If that is unclear or you have questions you'll need to ask. Otherwise
this will go on in circles. If you're absolutely certain the entityID
you used on your bespoke EntityDescriptor matches what's in the log
for that SP, verbatim, bit for bit, then the metadata likely isn't
read.
Check the IDP's log for any WARN or ERROR messages. E.g. if the
metadata isn't valid the IDP will also ignore it (along with other SPs
in that metadata document).
-peter