Re: [VOTE] Release Apache LDAP API 2.0.2
Checked out and built the tag, the source package, checked the signature, checked the N&L files, all good to me. +1 Thanks Stefan ! On Sat, May 22, 2021 at 1:38 PM Stefan Seelmann wrote: > > Hi all, > > this is a vote for the release of the Apache LDAP API 2.0.2. > > This is a bug fix and maintenance release. The changes are listed here: > https://issues.apache.org/jira/projects/DIRAPI/versions/12348316 > > The git tag: > https://gitbox.apache.org/repos/asf?p=directory-ldap-api.git;a=tag;h=refs/tags/2.0.2 > https://github.com/apache/directory-ldap-api/tree/2.0.2 > > The source and binary distribution packages: > https://dist.apache.org/repos/dist/dev/directory/api/dist/2.0.2/ > > The staging repository: > https://repository.apache.org/content/repositories/orgapachedirectory-1196/ > > Please cast your votes: > [ ] +1 Release Apache LDAP API 2.0.2 > [ ] 0 abstain > [ ] -1 Do not release Apache LDAP API 2.0.2 > > Kind Regards, > Stefan > > - > To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org > For additional commands, e-mail: dev-h...@directory.apache.org > -- Regards, Cordialement, Emmanuel Lécharny www.iktek.com - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
Sponsoring the work on data corruption / Mavibot
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 sponsor this work? 2) where would the money need to be sent? 3) About how much time would be necessary from the moment financial resources are in? This information will allow me to make my case. Thank you Kind regards, Sam
Re: Urgent :Apache DS Replace JDBM with mavibot
Hi Alexander, On 5/22/21 6:32 PM, Alexander Zaretsky wrote: > Hello : I am experiencing corruption using Apache Directory Server 2.0.0 > M26 on windows server 2016. Unfortunately that's a known issue, please read our statement about the production readiness [1]. > I am trying to repair the JDBM backend : > > I modified the file > > c:\Program Files > (x86)\ApacheDS\instances\default\conf\wrapper-instance.conf adding the > following line at the end of the file wrapper.app.parameter.1=repair > > and restarting. > > I realize this is not a definite solution, so I want to use mavibot as a > backend for my Apache DS instead of JDBM > > I want to know how to make my apache DS work with mavibot instead of jdbm. The easiest way is to use Studio to create a Mavibot partition, see [2]. Once stored you can find the configuration in the config partition below ou=partitions,ads-directoryServiceId=default,ou=config However I can't tell you if the current version of Mavibot is stable enough or might cause similar or differnt problems. > I also want to know how to migrate my current JDBM entries to mavibot. I think the only way is to export and import the data via LDIF. Kind Regards, Stefan [1] https://directory.apache.org/apacheds/production-readiness.html [2] https://nightlies.apache.org/directory/studio/2.0.0.v20210213-M16/userguide/apacheds/gettingstarted_configuration_editor_partitions.html - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
Fwd: Urgent :Apache DS Replace JDBM with mavibot
FYA Mensaje reenviado Asunto: Urgent :Apache DS Replace JDBM with mavibot Fecha: Sat, 22 May 2021 11:32:49 -0500 De: Alexander Zaretsky Para: dev@directory.apache.org CC: us...@directory.apache.org Hello : I am experiencing corruption using Apache Directory Server 2.0.0 M26 on windows server 2016. I am trying to repair the JDBM backend : I modified the file c:\Program Files (x86)\ApacheDS\instances\default\conf\wrapper-instance.conf adding the following line at the end of the file wrapper.app.parameter.1=repair and restarting. I realize this is not a definite solution, so I want to use mavibot as a backend for my Apache DS instead of JDBM I want to know how to make my apache DS work with mavibot instead of jdbm. I also want to know how to migrate my current JDBM entries to mavibot. Thanks in advance -- Saludos, Regards Alexander Zaretsky CEO True Technology Solutions SAS <> - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Closed] (DIRSTUDIO-1053) P2 repository / update site for RCP product
[ https://issues.apache.org/jira/browse/DIRSTUDIO-1053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seelmann closed DIRSTUDIO-1053. -- Resolution: Won't Fix I don't remember why it's needed. > P2 repository / update site for RCP product > --- > > Key: DIRSTUDIO-1053 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1053 > Project: Directory Studio > Issue Type: Task >Reporter: Stefan Seelmann >Priority: Major > > Follow up for DIRSTUDIO-1023. The P2 repository for the Studio product needs > to be generated. Configuration is tricky because Eclipse dependencies should > not be included. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Updated] (DIRSTUDIO-1189) dom4j illegal reflective access with Java 11
[ https://issues.apache.org/jira/browse/DIRSTUDIO-1189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seelmann updated DIRSTUDIO-1189: --- Fix Version/s: (was: 2.0.0) 2.0.0-M17 > dom4j illegal reflective access with Java 11 > > > Key: DIRSTUDIO-1189 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1189 > Project: Directory Studio > Issue Type: Task >Reporter: Stefan Seelmann >Assignee: Stefan Seelmann >Priority: Major > Fix For: 2.0.0-M17 > > > When running Studio with Java 11 the following warning is printed, should be > investigated > WARNING: An illegal reflective access operation has occurred > WARNING: Illegal reflective access by org.dom4j.io.SAXContentHandler > (file:/.../directory-studio/product/target/products/org.apache.directory.studio.product/linux/gtk/x86_64/ApacheDirectoryStudio/plugins/org.dom4j_1.6.1.v20170815-1500.jar) > to method > com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser$LocatorProxy.getEncoding() > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Resolved] (DIRSTUDIO-1189) dom4j illegal reflective access with Java 11
[ https://issues.apache.org/jira/browse/DIRSTUDIO-1189?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seelmann resolved DIRSTUDIO-1189. Resolution: Fixed > dom4j illegal reflective access with Java 11 > > > Key: DIRSTUDIO-1189 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1189 > Project: Directory Studio > Issue Type: Task >Reporter: Stefan Seelmann >Assignee: Stefan Seelmann >Priority: Major > Fix For: 2.0.0-M17 > > > When running Studio with Java 11 the following warning is printed, should be > investigated > WARNING: An illegal reflective access operation has occurred > WARNING: Illegal reflective access by org.dom4j.io.SAXContentHandler > (file:/.../directory-studio/product/target/products/org.apache.directory.studio.product/linux/gtk/x86_64/ApacheDirectoryStudio/plugins/org.dom4j_1.6.1.v20170815-1500.jar) > to method > com.sun.org.apache.xerces.internal.parsers.AbstractSAXParser$LocatorProxy.getEncoding() > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Resolved] (DIRSTUDIO-1272) Remove Network Connections preferences page (socks proxy settings)
[ https://issues.apache.org/jira/browse/DIRSTUDIO-1272?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seelmann resolved DIRSTUDIO-1272. Resolution: Fixed > Remove Network Connections preferences page (socks proxy settings) > -- > > Key: DIRSTUDIO-1272 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1272 > Project: Directory Studio > Issue Type: Task > Components: studio-rcp >Affects Versions: 2.0.0-M16 >Reporter: Stefan Seelmann >Assignee: Stefan Seelmann >Priority: Major > Fix For: 2.0.0-M17 > > > We have several bug reports [1][2][3] that SOCKS proxy settings don't > work, however there is a preference page [4] in Studio which gives the > impression it's supported. > That preference page is provided by Eclipse. What is does is to set Java > system properties [5]. There are known limitations, e.g. socks > authentication and proxy bypass don't work [6]. There is no additional > code in Studio to support proxies, and also zero tests. > In the past with JNDI the basic settings of a SOCKS proxy worked because > it is handled by Java old blocking IO. > However after the JNDI removal we only support the LDAP API which uses > Mina and new IO where those system properties don't work [7]. > I'd suggest to remove that preference page and related documentation > because its presence gives users the impression it would work. > Remains the question if we should implement proxy support properly in > Studio. It's clearly possible, Mina even implements a proxy filter and > connector. However it's significant effort and requires changes in the > LDAP API and new UIs in Studio and proper unit/integration testing. On > the other side there are dedicated tools which provide transparent SOCKS > proxy support. So I have doubts if it makes sense to implement it in > Studio. > [1] https://issues.apache.org/jira/browse/DIRSTUDIO-501 > [2] https://issues.apache.org/jira/browse/DIRSTUDIO-846 > [3] https://issues.apache.org/jira/browse/DIRSTUDIO-1269 > [4] > https://nightlies.apache.org/directory/studio/2.0.0.v20210213-M16/userguide/apache_directory_studio/network_connections.html > [5] > https://docs.oracle.com/javase/8/docs/api/java/net/doc-files/net-properties.html > [6] https://bugs.eclipse.org/bugs/show_bug.cgi?id=291717 > [7] https://bugs.openjdk.java.net/browse/JDK-8199457 > Discussion one the mailing list: > https://lists.apache.org/thread.html/re4b0474a838a71428e3a624e3a52a55358a01fe72c9cb23ac23a0e30%40%3Cdev.directory.apache.org%3E -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Resolved] (DIRSTUDIO-1271) Oracle OUD 11.1.2.3 does not list any Naming Contexts in ldapbrowser with M16, previous releases are OK.
[ https://issues.apache.org/jira/browse/DIRSTUDIO-1271?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seelmann resolved DIRSTUDIO-1271. Resolution: Fixed > Oracle OUD 11.1.2.3 does not list any Naming Contexts in ldapbrowser with > M16, previous releases are OK. > > > Key: DIRSTUDIO-1271 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1271 > Project: Directory Studio > Issue Type: Bug > Components: studio-ldapbrowser >Affects Versions: 2.0.0-M16 > Environment: Windows with Oracle JDK 11 or Graal/JDK11 >Reporter: Mark Davis >Assignee: Stefan Seelmann >Priority: Major > Fix For: 2.0.0-M17 > > > Using M16, and connecting to Oracle OUD 11.1.2.3 shows Root DSE only, and all > contexts underneath are missing. I can see the available namingContexts in > the Root DSE entry. > Release M14 and before are fine. > A fast test with Forgerock/OpenDJ7.0.1 (derived from the same source, but > diverged) is OK. > -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Resolved] (DIRSTUDIO-1269) SOCKS proxy is not working
[ https://issues.apache.org/jira/browse/DIRSTUDIO-1269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seelmann resolved DIRSTUDIO-1269. Resolution: Won't Fix > SOCKS proxy is not working > -- > > Key: DIRSTUDIO-1269 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1269 > Project: Directory Studio > Issue Type: Bug >Affects Versions: 2.0.0-M16 > Environment: Windows 10. Apache Directory Studio installed via scoop >Reporter: Philip Brusten >Priority: Major > Fix For: 2.0.0-M17 > > Attachments: image-2021-03-01-10-44-13-793.png > > > When I configure to use SOCKS proxy (SSH-tunnel), the proxy is not used. > My connections eventually timeout. > Screenshot of config: > !image-2021-03-01-10-44-13-793.png! -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Updated] (DIRSTUDIO-1269) SOCKS proxy is not working
[ https://issues.apache.org/jira/browse/DIRSTUDIO-1269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seelmann updated DIRSTUDIO-1269: --- Fix Version/s: 2.0.0-M17 > SOCKS proxy is not working > -- > > Key: DIRSTUDIO-1269 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1269 > Project: Directory Studio > Issue Type: Bug >Affects Versions: 2.0.0-M16 > Environment: Windows 10. Apache Directory Studio installed via scoop >Reporter: Philip Brusten >Priority: Major > Fix For: 2.0.0-M17 > > Attachments: image-2021-03-01-10-44-13-793.png > > > When I configure to use SOCKS proxy (SSH-tunnel), the proxy is not used. > My connections eventually timeout. > Screenshot of config: > !image-2021-03-01-10-44-13-793.png! -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Resolved] (DIRSTUDIO-1275) I updated on my mac to m16. Now only the proxy servers show the directory tree.
[ https://issues.apache.org/jira/browse/DIRSTUDIO-1275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stefan Seelmann resolved DIRSTUDIO-1275. Resolution: Fixed > I updated on my mac to m16. Now only the proxy servers show the directory > tree. > > > Key: DIRSTUDIO-1275 > URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1275 > Project: Directory Studio > Issue Type: Bug >Affects Versions: 2.0.0-M16 > Environment: mac os big sur 11.2.3 > apache dir server 2.0.0.v20210213-M16 >Reporter: Cathryn Major >Assignee: Stefan Seelmann >Priority: Minor > Fix For: 2.0.0-M17 > > > In apache dir studio When I open a directory server the only thing it shows > is the Root DSE. I cannot fetch the dn. > The DSE shows two name contexts-one for changelog > dc=### (not showing acutal values for dc) > For the proxy connection the DSE shows DSE2 and the components underneath it. > And these only show the dc name context. -- This message was sent by Atlassian Jira (v8.3.4#803005) - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[VOTE] Release Apache LDAP API 2.0.2
Hi all, this is a vote for the release of the Apache LDAP API 2.0.2. This is a bug fix and maintenance release. The changes are listed here: https://issues.apache.org/jira/projects/DIRAPI/versions/12348316 The git tag: https://gitbox.apache.org/repos/asf?p=directory-ldap-api.git;a=tag;h=refs/tags/2.0.2 https://github.com/apache/directory-ldap-api/tree/2.0.2 The source and binary distribution packages: https://dist.apache.org/repos/dist/dev/directory/api/dist/2.0.2/ The staging repository: https://repository.apache.org/content/repositories/orgapachedirectory-1196/ Please cast your votes: [ ] +1 Release Apache LDAP API 2.0.2 [ ] 0 abstain [ ] -1 Do not release Apache LDAP API 2.0.2 Kind Regards, Stefan - To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org For additional commands, e-mail: dev-h...@directory.apache.org
[jira] [Resolved] (DIRAPI-372) Publish new Version on Maven Central to get rid of vulnerable dependency
[
https://issues.apache.org/jira/browse/DIRAPI-372?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Stefan Seelmann resolved DIRAPI-372.
Resolution: Fixed
The release is on its way.
> Publish new Version on Maven Central to get rid of vulnerable dependency
>
>
> Key: DIRAPI-372
> URL: https://issues.apache.org/jira/browse/DIRAPI-372
> Project: Directory Client API
> Issue Type: Wish
>Affects Versions: 2.0.1
>Reporter: Valentin Brandl
>Priority: Major
> Fix For: 2.0.2
>
>
> The current version {{2.0.1}} still depends on
> {{org.apache.servicemix.bundles:org.apache.servicemix.bundles.dom4j:2.1.1_1}},
> which has known vulnerabilities:
> https://nvd.nist.gov/vuln/detail/CVE-2020-10683
> The dom4j dependency has been [updated 12 month
> ago|https://github.com/apache/directory-ldap-api/commit/b323881665ca6b530112b2017b2641065b07]
> but since then, there hasn't been a new release.
> It would be nice to have a new version in maven central that removes this
> vulnerable dependency.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
-
To unsubscribe, e-mail: dev-unsubscr...@directory.apache.org
For additional commands, e-mail: dev-h...@directory.apache.org
