CAS Proxy and clustering client application

[Scott Battaglia]

Have you looked into providing a clustered backend for the
ProxyGrantingTicketStorage?  The default is an in-memory map local to a
machine. But you could write a DB store, etc.

The only limitation is that more advanced configurations such as the
ProxyGrantingTicketStorage currently require Spring configuration (for
better or worse).

-Scott

-Scott Battaglia
PGP Public Key Id: 0x383733AA
LinkedIn: http://www.linkedin.com/in/scottbattaglia


On Thu, Oct 16, 2008 at 4:17 AM, Mathieu ROUSSELLE <
mathieu.rousselle at niji.fr> wrote:

>  Hi everyone !
>
>
>
> I am working on the way to put a casified application on a clustered
> environment.
>
>
>
> To sum up, the actual infrastructure is :
>
> -          A CAS server
>
> -          A service server
>
> -          Another service server accessed through Proxy mechanism.
>
>
>
> The target infrastructure is :
>
> -          A CAS server
>
> -          A cluster of service server accessed through a network load
> balancer configured with session affinity.
>
> -          Another service server accessed through Proxy mechanism.
>
>
>
> I have seen some tutorial on how to run a CAS server on a cluster, but I
> have found no information on how to run Casified application on a cluster.
>
>
>
> The issue is : what to do with the PGT callback url ?
>
> If user1 is served by server1 through the load balancer, it is not sure
> that cas-server will send back the PGT to server1.
>
>
>
> 1.       I have seen that we can specify several callback url, but I'm not
> sure that each server of the cluster will be reachable from the Internet.
>
> 2.       Do I have to use session replication mechanism ?
>
>
>
> Thanks,
>
>
>
> Mathieu
>
> _______________________________________________
> Yale CAS mailing list
> cas at tp.its.yale.edu
> http://tp.its.yale.edu/mailman/listinfo/cas
>
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://tp.its.yale.edu/pipermail/cas/attachments/20081016/9049705a/attachment.html