Hi,
I agree with Jérôme, the simplest and most robust solution is to have 2
(or in our case 4) CAS servers running in a cluster with a multi-master
LDAP backend. Put a load-balancer in front of your CAS servers and
you're done.
Okay, on second thought... Maybe not the simplest, but it is very
indicating if CAS
is enabled or not. And present the appropriate login form.
Do you think there is an better alternative?
Regards,
Prasad
*From:*Stephan Arts [mailto:sa...@cosmos.esa.int]
*Sent:* 06 February 2015 13:37
*To:* cas-user@lists.jasig.org
*Subject:* Re: [cas-user] designing
] designing a fallback authentication scheme
Hi,
I agree with Jérôme, the simplest and most robust solution is to have 2 (or in
our case 4) CAS servers running in a cluster with a multi-master LDAP backend.
Put a load-balancer in front of your CAS servers and you're done.
Okay, on second thought
Hi,
I would not recommend to implement such a fallback mechanism on client
side: it would be pretty complicated and you would lose all the benefits of
a centralized authentication server (security, one link to the
authentication source).
Why not a failover with two CAS servers? It can be
Hi All,
we are using CAS authentication to implement SSO model. we are using the JSR
196 for the extending the JAAS authorization. As part of this we are also
implementing a fall back mechanism in situations where CAS is not available. in
situations where CAS is not available, we want to
