We would like the ability to configure Crowd to deal with a cluster of LDAP instances. Current thinking was to have one write LDAP server and multiple read only servers. Currently Crowd stores directory config in the database which makes it difficult to specify different LDAP instances.
The option currently considered is to provide one read only LDAP per instance of Crowd. This would require the ability to externalise the directory config.
- causes
-
CWD-3333 Incremental sync does not work when using file-based directory configuration
- Closed
- details
-
CWD-3032 Create an acceptance test suite for Crowd running with a file-based directory configuration
- Closed
-
CWD-3033 Produce directory configuration files from the current database-based directory configuration
- Closed
- duplicates
-
CWD-2891 Externalised Crowd Config
- Closed
- is related to
-
CWD-3901 Manual and scheduled backup fails when using file-based directory configuration
- Closed
-
CWD-422 Directory Failover option for an application
- Closed
-
CWD-1484 Allow multiple LDAP backends to be specified, with connection timeout
- Closed
-
CWD-3052 Use file change notification for configuration files
- Closed
-
CWD-3417 Sort directories when using directories.properties
- Closed
-
KRAK-334 Loading...
- relates to
-
CWD-2891 Externalised Crowd Config
- Closed
- Testing discovered
-
CWD-3031 Stacktrace is displayed if updating a directory fails
- Closed