2015 14:57
To: cas-user@lists.jasig.org
Subject: Re: [cas-user] designing a fallback authentication scheme
Hi Prasad,
I think that would be a good solution for what you are describing. I was under
the impression you were referring to a fallback scenario in case your own CAS
server was not
To:* cas-user@lists.jasig.org
> *Subject:* Re: [cas-user] 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 back
] 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 th
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
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 achieved
