<p>I have made some tests myself using latest chrome and, at least with its default cookie settings, it removed the cookie after closing it. Google was not much help on the matter either other than an old thread where they say it is not possible for securities reason.<br>
I know that due to the open nature of Shibboleth I could literally just change the code but I was thinking more along the lines of something simpler like extending the username/password login handler. I thought the idp_session cookie code was at Shibboleth's core but maybe I need to look at the code again.</p>
<div class="gmail_quote">On Aug 5, 2013 10:39 PM, "Nate Klingenstein" <<a href="mailto:ndk@internet2.edu">ndk@internet2.edu</a>> wrote:<br type="attribution"><blockquote class="gmail_quote" style="margin:0 0 0 .8ex;border-left:1px #ccc solid;padding-left:1ex">
Byte,<br>
<br>
> Is it possible to use persistent cookies with Shibboleth IDP (by default or custom code)<br>
<br>
I don't think it's possible by configuring the distribution using the username/password login handler, but you can do anything you want with custom code, obviously.<br>
<br>
> to keep the user logged in even after closing the browser?<br>
<br>
Just set a duration in the user's idp_session cookie(custom code) and make sure that user session objects are persisted for an equally long time in the IdP authentication handler and session manager(and sticky load balancer if used).<br>
<br>
You could also just use a custom login handler and handle all user login state there.<br>
<br>
That, or ask your users to use a "modern" browser that persists all session cookies anyway… ;D<br>
<br>
Thanks,<br>
Nate.<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>