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

[Cahill, Charles (GE Appliances)]

So I have made all of the changes Peter recommended in this thread.

http://shibboleth.net/pipermail/users/2015-June/021856.html

I still seem to be getting the below error:
15:25:32.777 [http-bio-8080-exec-10] DEBUG e.i.m.s.i.a.p.UsernamePasswordLoginServlet - Successfully authenticated user xxxxxxxx
15:25:32.778 [http-bio-8080-exec-10] DEBUG e.i.m.s.i.authn.AuthenticationEngine - Returning control to authentication engine
15:25:32.778 [http-bio-8080-exec-10] DEBUG e.i.m.s.idp.util.HttpServletHelper - LoginContext key cookie was not present in request
15:25:32.778 [http-bio-8080-exec-10] WARN  e.i.m.s.i.authn.AuthenticationEngine - No login context available, unable to return to authentication engine
15:25:32.892 [http-bio-8080-exec-10] DEBUG e.i.m.s.idp.util.HttpServletHelper - LoginContext key cookie was not present in request
15:25:32.892 [http-bio-8080-exec-10] DEBUG e.i.m.s.idp.ui.ServiceContactTag - No relying party, nothing to display

May I inquire again into what the login URL is that I would be giving the 3rd party PagerDuty application or how it should be formatted?
I currently gave them this   https://{$myidp}/idp/Authn/UserPassword<https://%7b$myidp%7d/idp/Authn/UserPassword>


-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://shibboleth.net/pipermail/users/attachments/20150611/0ea55816/attachment-0001.html>