thx for your answer,
I use LDAP service registry, which store the services (new functionality
since 3.1.2 ). I dont know how it is managed with JPA, but with ldap
serviceregistry, the ldap is not read until tomcat restart to get
service list.
So if you share one or more ldap with more than one cas, only the one
where you make the changes(or add) is up2date.
As far as i looked into the source, I think it is a problem which does
not depend on the store backend.
In the
"cas-server-core/src/main/java/org/jasig/cas/services/ServicesManager.java"
in the method "getAllServices" no reload from backend is done. So I
can't see how it can share services added or modified with the other
node of the cluser.
Is it correct or am I missing some things ?
sorry for my poor english,
MARTEAU Christophe
CICT
118, route de Narbonne
31000 Toulouse
Andrew Feller a écrit :
Marteau,
Which ServiceRegistry implementation are you using? In-memory or JPA? If
you are using JPA, then it is possible for you to replicate the database
being used between the two servers by whatever means the database provides.
Basically, it isn't a function of your LDAP server to contain service
registry information.
HTH,
A-
On 7/15/09 9:02 AM, "Marteau Christophe" <[email protected]> wrote:
hello,
I have two cas in a cluster.
I've got the serviceRegistry configured to store applications who are
allowed to use the CAS service into LDAP and it works. But when I add a
service, only one node is updated because the other dont read the ldap
until it restart.
Is there any cluster configuration like ticketRegistry to share it with
the other node ?
thx
--
You are currently subscribed to [email protected] as:
[email protected]
To unsubscribe, change settings or access archives, see
http://www.ja-sig.org/wiki/display/JSG/cas-user
