...
[13:40:34 CDT(-0500)] <sjungling> and the when the load balancer tried to re-balance traffic across the remaining two servers, it knocked another one out
[13:44:23 CDT(-0500)] <mmoayyed> Hi Eric; just wanted to confirm: person directory 1.5.1 was just released?
[13:48:27 CDT(-0500)] <EricDalquist> yes
[13:50:46 CDT(-0500)] <mmoayyed> great. CAS is on 1.5.0-RC6. I am going to try and upgrade the dependency for the next release. Any particular changes? release notes?
[13:51:02 CDT(-0500)] <EricDalquist> 1.5.1 was just some logging changes
[13:51:08 CDT(-0500)] <EricDalquist> I can't remember what all was in 1.5.0
[13:54:25 CDT(-0500)] <sjungling> is there a default application session timeout for v4? or is that tied to the container (e.g. Tomcat's) session timeout?
[14:09:29 CDT(-0500)] <EricDalquist> uportal just uses the container's session timeout
[14:14:45 CDT(-0500)] <sjungling> beauty
[14:14:53 CDT(-0500)] <sjungling> what i suspected
[14:16:02 CDT(-0500)] <EricDalquist> the only exception is if you set the org.jasig.portal.PortalSessionManager.unauthenticatedUserSessionTimeout property in portal.properties
[14:16:16 CDT(-0500)] <EricDalquist> if that is set to something other than 0 that overrides the session timeout for guest sessions
[14:16:32 CDT(-0500)] <EricDalquist> like you could set it to 300 so that guest users only have a 5 minute timeout
[14:17:48 CDT(-0500)] <sjungling> kk
[14:17:55 CDT(-0500)] <sjungling> i'm mostly interested in auth'd users
[14:18:16 CDT(-0500)] <sjungling> so if we disable the SingleSignOut message from CAS, sound like they'll lose their Portal session anyway through Tomcats session expiration
[14:18:53 CDT(-0500)] <EricDalquist> yeah