[jira] [Created] (JAMES-3928) ReadOnlyUsersRepository: Master slave set up
Benoit Tellier created JAMES-3928: - Summary: 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 Fix For: 3.9.0 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-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[BUILD-FAILURE]: Job 'james/ApacheJames/master [master] [1082]'
BUILD-FAILURE: Job 'james/ApacheJames/master [master] [1082]': Check console output at "https://ci-builds.apache.org/job/james/job/ApacheJames/job/master/1082/";>james/ApacheJames/master [master] [1082]" - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[jira] [Created] (JAMES-3929) Upgrade opensearch-java client
René Cordier created JAMES-3929: --- Summary: Upgrade opensearch-java client Key: JAMES-3929 URL: https://issues.apache.org/jira/browse/JAMES-3929 Project: James Server Issue Type: Improvement Reporter: René Cordier Fix For: 3.9.0 We should upgrade and fix code accordingly the opensearch-java client from 2.1.0 to its latest version, 2.6.0. Also, referring to the official doc: [https://opensearch.org/docs/latest/clients/java/] It seems the opensearch-java client now has its own http client transport. We need to try to refactor the code to use this instead of the transport client privded by the opensearch-rest-client dependency, which would allow us to drop it. Then we need to do some performance tests to measure if such adoption has any impact or not. If the tests are conclusive enough, we should adopt it and drop the opensearch-rest-client dependency once and for all. -- This message was sent by Atlassian Jira (v8.20.10#820010) - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
[BUILD-STABLE]: Job 'james/ApacheJames/master [master] [1083]'
BUILD-STABLE: Job 'james/ApacheJames/master [master] [1083]': Is back to normal. - To unsubscribe, e-mail: server-dev-unsubscr...@james.apache.org For additional commands, e-mail: server-dev-h...@james.apache.org
