Hi, Dario. Let us check this part of doc. I'll get back to you shortly.

Hello, Any updates? Thanks.

Hi, Dario. We are testing the cluster setup at the moment. You can check updated documentation again, please note it now says that you must not to start OpenLDAP service after you've added `EXTRA_SLAPD_ARGS="-F /opt/symas/etc/openldap/slapd.d"` string yourself - Cluster Manager will start it for you while setting both nodes for replication (if you intend to use mirrored setup with 2 consumers). It will create the `slap.d` directory with all needed contents. You also should be aware that configuring oxAuth key rotation most likely a mandatory step too (it's currently not marked as such, and we are reviewing architecture at the moment). It needs to be configured after replication is set and tested (all done in Cluster Manager's web UI). Finally, please note that current version only officially supports servers running Gluu CE 3.0.1 (you specified 3.0.2 in your first post). Support for current packages will be added upon release, so currently it's only suitable for a basic test setup.

Hi Aliaksandr, Sorry for my late reply, I was in vacations ;-) and thanks for your answers. I will test the clustering this week with 3.0.1 and keep you inform. Just three more questions about that : The documentation only talks about LDAP replication. For files replications ( eg : customs pages ), I assume that we need to use tools like csync2? Should all instances of the cluster ( providers and consumers ) need to have the same FQDN provided during gluu installation? Is it possible to install a consumer without Open LDAP ( eg: only oxAuth and JCE are installed )? and by using /etc/gluu/conf/ox-ldap.properties to link the consumer to one provider's Open LDAP . Regards

Hi, Dario. Please note Cluster Manager has been updated recently. You should install the newer version. It should also support 3.0.2 Gluu CE packages now. >The documentation only talks about LDAP replication. For files replications ( eg : customs pages ), I assume that we need to use tools like csync2? Cluster Manager only deals with setting LDAP replication. So if you need to make some files syncronised between nodes, some additional tools may need to be used. Though in case of custom pages, I'm not sure you need to go that far, as they are mostly one-time changes, so may be it's easier to just apply updates at both nodes manually. >Should all instances of the cluster ( providers and consumers ) need to have the same FQDN provided during gluu installation? Gluu CE isn't aware it runs in cluster. It's still "perceives" itself as a regular standalone package. So each of the instances should share the same DNS name (the one that will be used by Relying Parties to send user for authentication at, that's the name you provide to `setup.py`), that's correct. Still, aside from this, each node needs to have a unique DNS name (like, `node1.domain.com` and `node2.domain.com`) - you'll provide those when generating new certificates for OpenLDAP and when setting LDAP replication. >Is it possible to install a consumer without Open LDAP ( eg: only oxAuth and JCE are installed )? and by using /etc/gluu/conf/ox-ldap.properties to link the consumer to one provider's Open LDAP . Unless it's not in docs, it's not supported officially. You are free to experiment, of course.

Thanks Aliaksandr!