You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Emmanuel Lecharny (JIRA)" <ji...@apache.org> on 2018/08/11 05:15:00 UTC
[jira] [Commented] (DIRSTUDIO-1187) Disable JNDI connection
provider for Java 9+
[ https://issues.apache.org/jira/browse/DIRSTUDIO-1187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16577056#comment-16577056 ]
Emmanuel Lecharny commented on DIRSTUDIO-1187:
----------------------------------------------
We have kept the JNDI provider because we wanted to be sure we have a workaround if the LDAP API was faulty. It's been years since we are using teh LDAP API as a default provider, and we haven't had any trouble so far that required to use JNDI to get Studio working.
It's about time to get rid of JNDI completely in Studio.
> Disable JNDI connection provider for Java 9+
> --------------------------------------------
>
> Key: DIRSTUDIO-1187
> URL: https://issues.apache.org/jira/browse/DIRSTUDIO-1187
> Project: Directory Studio
> Issue Type: Task
> Reporter: Stefan Seelmann
> Assignee: Stefan Seelmann
> Priority: Major
> Fix For: 2.0.0-M14
>
>
> Behaviour of JNDI has been changed since Java 9. Especially LdapContext.reconnect() now creates a new physical connection. In Studio the "Check Authentication" used the old behaviour, it no longer works since Java 9. Instead of refactoring JNDIConnectionProvider let's disable it for Java 9+ and long term remove the JNDI network provider.
> Related changes:
> * https://bugs.openjdk.java.net/browse/JDK-8059009
> * http://hg.openjdk.java.net/jdk9/jdk9/jdk/rev/021b47694183
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)