Re: LDAP API v1

2021-05-26 Thread Shawn McKinney
> On May 26, 2021, at 3:27 PM, Emmanuel Lécharny wrote: > > OTOH, migrating to 2.0 should not take a lot of time. A couple of days, maybe > ? Has been on my todo list for some time. As I recall the only tricky spot was the openldap accelerator client’s extended operations. Is there a

Re: LDAP API v1

2021-05-26 Thread Emmanuel Lécharny
On 26/05/2021 18:59, Shawn McKinney wrote: On May 26, 2021, at 11:46 AM, Stefan Seelmann wrote: I wonder if we still maintain the LDAP API v1? The last release of 1.0.3 was more then 2 years ago in April 2019. On the website we still list it. Hi Stefan, Unfortunately, fortress still

Re: Sponsoring the work on data corruption / Mavibot

2021-05-26 Thread Emmanuel Lécharny
Hi, On 22/05/2021 22:43, Samuel wrote: Hello, I may be able to convince my company to sponsor the work on data corruption / Mavibot, the goal would be to get ApacheDS production-ready from a stability point of view. I have a couple of questions: 1) How much money would be needed to

Re: LDAP API v1

2021-05-26 Thread Shawn McKinney
> On May 26, 2021, at 11:46 AM, Stefan Seelmann wrote: > > I wonder if we still maintain the LDAP API v1? The last release of 1.0.3 > was more then 2 years ago in April 2019. > > On the website we still list it. > Hi Stefan, Unfortunately, fortress still uses it. > Moreover, in both the

LDAP API v1

2021-05-26 Thread Stefan Seelmann
Hi, I wonder if we still maintain the LDAP API v1? The last release of 1.0.3 was more then 2 years ago in April 2019. On the website we still list it. Moreover, in both the navigation bar and the LDAP API landing page v1 appears before v2 so it seems we rank it higher. Should we completely

[GitHub] [directory-kerby] TimoScheuer opened a new pull request #104: search subtree to be able to use identities provisioned by other tool…

2021-05-26 Thread GitBox
TimoScheuer opened a new pull request #104: URL: https://github.com/apache/directory-kerby/pull/104 …s into child organizational unit and be more specific according to search class (use krb5principal) Two changes are done: 1. the LDAP class used can be more specific to allow