<p>Thanks for the tip. I'll do some digging and tests and see what I can find out.</p>
<p>I should also mention that by "removed the cookie" I meant that I went to the SP logged in on Shibboleth IDP, closed the browser and went to the SP again and it got me into Shibboleth login page again so I assume Chrome removed the cookie.</p>
<div class="gmail_quote">On Aug 5, 2013 11:48 PM, "Cantor, Scott" <<a href="mailto:cantor.2@osu.edu">cantor.2@osu.edu</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
On 8/5/13 5:45 PM, "Cantor, Scott" <<a href="mailto:cantor.2@osu.edu">cantor.2@osu.edu</a>> wrote:<br>
><br>
>>I'll look into what I can do with the username password servlet provided<br>
>>by Shibboleth.<br>
><br>
>You'll get nowhere, that has nothing to do with the session cookie in any<br>
>way.<br>
<br>
I believe the request you'd have to filter, *probably*, is the<br>
/idp/AuthnEngine path. That may be true even when it selects the previous<br>
session handler, but I really don't know exactly when it will set the<br>
cookie in all cases.<br>
<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>
</blockquote></div>