Shibboleth IdP 3 - Stale Session

James Gross JamesGross at
Wed May 6 14:58:31 EDT 2015

I think I got it figured out. The servers are behind a load balancer with a
low sticky session timeout. I believe the users were getting directed to
one back-end server and waiting beyond the persistence timeout. Their
subsequent post with the credentials would have a chance of being directed
to a different back-end server that would not have the SWF/Jetty session.

*James Gross* | Enterprise Application and CMS Developer (Enterprise Web

UNC Charlotte | Information Technology Services

9201 University City Blvd. | Charlotte, NC 28223

Phone: 704-687-0298 | Office: Kennedy 301-C39

jgross15 at |

If you are not the intended recipient of this transmission or a person
responsible for delivering it to the intended recipient, any disclosure,
copying, distribution, or other use of any of the information in this
transmission is strictly prohibited. If you have received this transmission
in error, please notify me immediately by reply e-mail or by telephone at
704-687-0298. Thank you.

On Wed, May 6, 2015 at 2:24 PM, Cantor, Scott <cantor.2 at> wrote:

> On 5/6/15, 5:43 PM, "James Gross" <JamesGross at> wrote:
> >
> >Thanks for the reply. I haven't adjusted the default values for the
> >container (Jetty 9), but now I'm wondering if it might be related to
> >having Apache in front of Jetty (using mod_proxy).
> It shouldn't. The default is 30, I just checked, it's in
> JETTY_HOME/etc/webdefault.xml
> -- Scott
> --
> To unsubscribe from this list send an email to
> users-unsubscribe at
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the users mailing list