gt; (the administrators of CAS) control over which server was active without
> having to bug the administrator for the LB.
>
> -John
>
> -Original Message-
> From: Marvin Addison [mailto:marvin.addi...@gmail.com]
> Sent: Tuesday, October 04, 2011 8:26 AM
> To: cas-user@lis
rver was active without having to
bug the administrator for the LB.
-John
-Original Message-
From: Marvin Addison [mailto:marvin.addi...@gmail.com]
Sent: Tuesday, October 04, 2011 8:26 AM
To: cas-user@lists.jasig.org
Subject: Re: [cas-user] Login Ticket in CAS Cluster
> Thanks Scott.
> Thanks Scott. I'm guessing then to avoid clustering the HTTP session we'd
> need to use sticky sessions on our load balancer?
Correct. I should note that there used to be a capability in Spring
Web Flow 1.x where flow execution state could be stored client-side to
facilitate truly stateless cl
Thanks Andrew.
From: Tillinghast, Andrew P. [atill...@conncoll.edu]
Sent: 04 October 2011 13:37
To: cas-user@lists.jasig.org
Subject: Re: [cas-user] Login Ticket in CAS Cluster
LoginTicket is a session entity, unless you replicate the session the
LoginTicket
Thanks Scott. I'm guessing then to avoid clustering the HTTP session we'd need
to use sticky sessions on our load balancer?
From: Scott Battaglia [scott.battag...@gmail.com]
Sent: 04 October 2011 13:25
To: cas-user@lists.jasig.org
Subject: Re: [cas-u
LoginTicket is a session entity, unless you replicate the session the
LoginTicket will not pass between servers in your cluster.
TicketGrantingTicket and ServiceTicket are replicated between servers in all
the cluster configurations so that if a user logs in on CAS-1 and is validated
on CAS-2
You would need to cluster the HTTP session, which is where Spring Web Flow
holds the login tokens.
Cheers,
Scott
On Tue, Oct 4, 2011 at 6:06 AM, Kirk, Matt wrote:
> Hi,
>
> Can someone tell me what the CAS behaviour should be in a clustered
> environment WITHOUT Tomcat session replication or s
