Big news! The community will be moving to a new platform April 21. Read more.
Big news! The community will be moving to a new platform April 21. Read more.
Knowledge Partner Knowledge Partner
Knowledge Partner
642 views

Apache Studio question

Many of us are using Apache Directory Studio as their preferred LDAP
browser/editor. Studio comes with two LDAP providers as possible backends: the
Java standard JNDI and the Apache LDAP API.
With the next release of Studio, support for Java 9+ will be added, but this
breaks JNDI as some of the APIs changed between 8 and 9. So when running with
Java 9+ Studio will only support the Apache LDAP API and it's planned to remove
JNDI support completely.

A few years back I ran into some errors with the LDAP API and from then on only
used JNDI in Studio, so I suspect removing JNDI may cause trouble for us (I
doubt there is much testing against Edirectory done by the developers).

So my question to all of you: which provider do you use and how stable is it?
What is your experience with the Apache LDAP API against Edirectory during the
last two years or so (Apache Studio 2.0.0-M12/13 timeframe)?

The provider in use can be found in each connection's properties, the default
provider in Prefs - Apache Studio - Connections.

--
http://www.is4it.de/en/solution/identity-access-management/

(If you find this post helpful, please click on the star below.)
______________________________________________
https://www.is4it.de/identity-access-management
Labels (1)
0 Likes
5 Replies
Knowledge Partner Knowledge Partner
Knowledge Partner

Hi Lothar,

I use ADS2-M13.
All my connections configured to use Apache Directory LDAP API and I doesn't have any to connect to different LDAP servers (eDir/AD/ITIM) with Simple Authentication method.
GSSAPI (Kerberos) authentication method doesn't work.

Connections based on JNDI provider doesn't work at all.
0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

al_b;2485631 wrote:
Connections based on JNDI provider doesn't work at all.

Are you using Java 8 or 9+?
______________________________________________
https://www.is4it.de/identity-access-management
0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

In my setup my openSUSE laptop uses Java 8, and I have a fairly even split of JNDI an Apache providers for eDirectory as well as other things (ApacheDS, Unbound/Ping DS, etc.). They all seem to work.

I remember when the Apache provider came out that I had some issues, but it's been a long time since I've noticed those.

What are your issues?


--
Good luck.

If you find this post helpful and are logged into the web interface,
show your appreciation and click on the star below.

If you want to send me a private message, please let me know in the
forum as I do not use the web interface often.
0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

ab wrote:

> In my setup my openSUSE laptop uses Java 8, and I have a fairly even
> split of JNDI an Apache providers for eDirectory as well as other things
> (ApacheDS, Unbound/Ping DS, etc.). They all seem to work.
>
> I remember when the Apache provider came out that I had some issues, but
> it's been a long time since I've noticed those.
>
> What are your issues?


No current issues, since I did not use the Apache API for quite a while. Was
just wondering if we should try to keep JNDI around for Java 9+ to avoid issues
I have not seen due to sticking with JNDI. Sounds like that's not necessary,
though.

--
http://www.is4it.de/en/solution/identity-access-management/

(If you find this post helpful, please click on the star below.)
______________________________________________
https://www.is4it.de/identity-access-management
0 Likes
Knowledge Partner Knowledge Partner
Knowledge Partner

lhaeger;2485829 wrote:
Are you using Java 8 or 9+?

Currently ADS use Java 8

C:\Program Files\Java\jre1.8.0_181\bin\server\jvm.dll
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.