You are viewing a plain text version of this content. The canonical link for it is here.
Posted to server-dev@james.apache.org by "René Cordier (Jira)" <se...@james.apache.org> on 2023/07/21 04:45:00 UTC
[jira] [Resolved] (JAMES-3928) ReadOnlyUsersRepository: Master slave set up
[ https://issues.apache.org/jira/browse/JAMES-3928?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
René Cordier resolved JAMES-3928.
---------------------------------
Resolution: Fixed
[https://github.com/apache/james-project/pull/1649] has been merged and contributed to that
> ReadOnlyUsersRepository: Master slave set up
> --------------------------------------------
>
> Key: JAMES-3928
> URL: https://issues.apache.org/jira/browse/JAMES-3928
> Project: James Server
> Issue Type: New Feature
> Components: ldap, UsersStore & UsersRepository
> Affects Versions: master
> Reporter: Benoit Tellier
> Priority: Major
> Fix For: 3.9.0
>
> Time Spent: 50m
> Remaining Estimate: 0h
>
> h3. Why?
> High availability requires connecting to several servers.
> Today James LDAP connection is single point.
> To have HA for LDAP component we need to support connecting to several LDAP server.
> h3. How?
> In usersreporitory.xml configuration set a list of fallback ldap URLs.
> Use it to instanciate a LDAPConnectionPool based on a FailoverServerSet. Other connection options (bind DN, SSL, more?) needs to be preserved.
> h3. Acceptace criteria
> In a test, start ldap1 ldap2.
> Configure the ldap users repository with ldap1 as prmary, fallback to ldap2.
> Switch off ldap1, ensure that data gets retrieved from LDAP2.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
---------------------------------------------------------------------
To unsubscribe, e-mail: server-dev-unsubscribe@james.apache.org
For additional commands, e-mail: server-dev-help@james.apache.org