<div dir="ltr">Thanks Scott.<div><br></div><div>If I understand what you mean, I'd need to have a SAML Request come in first to specify which profile handler to be used which in turn goes to the login handler but then my question would be, how does the Unsolicited SSO profile works and can I implement a handler in a similar way (So that no request is required, the user simply goes to the login page and is logged in with a SAML Response sent back)?</div>
<div><br></div><div>My guess would be that I need to implement a custom profile handler instead of a login handler then (or maybe even both)?</div></div><div class="gmail_extra"><br><br><div class="gmail_quote">On 25 July 2013 18:15, Cantor, Scott <span dir="ltr"><<a href="mailto:cantor.2@osu.edu" target="_blank">cantor.2@osu.edu</a>></span> wrote:<br>
<blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex"><div class="im">On 7/25/13 12:03 PM, "Byte Flinger" <<a href="mailto:byteflinger@gmail.com">byteflinger@gmail.com</a>> wrote:<br>
<br>
>I have tried to create a very simple LoginHandler which would simply log<br>
>the user in if he just goes to the right page, regardless of given input<br>
>(for test purposes) but it seems the authentication engine still requires<br>
>an existing cookie<br>
><br>
>I keep getting "LoginContext key cookie was not present in request" from<br>
>HttpServletHelper.<br>
<br>
</div>That isn't the session cookie, it's a precondition of using the IdP at<br>
all. You cannot take the user into the middle of the flow. You must start<br>
at a profile endpoint, and that will send the user through the AuthnEngine<br>
and into whatever login handler is configured. There is no way to change<br>
that requirement.<br>
<div class="im"><br>
>I am probably missing something though I am not sure what. I have browsed<br>
>through several login handler implementations and Shibboleth's own source<br>
>code but I keep ending up on the fact that it requires that the user has<br>
>a cookie setup on his browser.<br>
<br>
</div>It does, a login context cookie set by a profile handler. That isn't the<br>
session cookie and has nothing to do with "bypassing" authentication.<br>
<div class="HOEnZb"><div class="h5"><br>
-- Scott<br>
<br>
<br>
--<br>
To unsubscribe from this list send an email to <a href="mailto:users-unsubscribe@shibboleth.net">users-unsubscribe@shibboleth.net</a><br>
</div></div></blockquote></div><br></div>