You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by Michael Barkdoll <ma...@gmail.com> on 2019/04/24 20:45:48 UTC

Maven repo out of date

Hi,

I'm trying to fix a bug that I'm experiencing in my Apache guacamole
deployment that relies upon Apache Directory api-all:

https://mvnrepository.com/artifact/org.apache.directory.api/api-all

pom.xml:
        <!-- Apache Directory LDAP API -->
        <dependency>
            <groupId>com.novell.ldap</groupId>
            <artifactId>jldap</artifactId>
            <version>4.3</version>
            <groupId>org.apache.directory.api</groupId>
            <artifactId>api-all</artifactId>
            <version>2.0.0.AM2</version>
            <exclusions>
                <exclusion>
                    <groupId>org.slf4j</groupId>
                    <artifactId>slf4j-api</artifactId>
                </exclusion>
            </exclusions>
        </dependency>

This is due to possibly bug:
https://issues.apache.org/jira/browse/DIRSTUDIO-1197?page=com.atlassian.jira.plugin.system.issuetabpanels%3Aall-tabpanel

Which has existed in the code base since August 18, 2017.  Can someone
please help me push out an update for this to the above mentioned repo or
tell me how I can compile it from source and insert the dependency in the
pom.xml from apache guacamole shown above.

Thanks so much for your help.  I've been working on this project all year
and now I notice some of the time the ldap authentication is bugged due to
this issue and I have a presentation next Wednesday.  Please help, this is
for the good of all cs students everywhere. :)

I tried to build from github:
https://github.com/apache/directory-studio

The ./build.sh script ended in an error for me though and I'm not certain
how to take the built files from it and insert them directly into the
pom.xml.

Re: Maven repo out of date

Posted by Emmanuel Lecharny <el...@apache.org>.
I won’t be able to look at what’s going bad, sadly, I’m away from my
computer this week :-/

Le ven. 26 avr. 2019 à 02:25, Michael Barkdoll <ma...@gmail.com> a
écrit :

> Sorry, my docker hub build link was invalid. I've updated it on this email
> to [1] which has a link to the build output from github commit
> source bd9ae3f  which should verify that it was built from the latest
> github repository.  In [2] you can see the ldap extension
> uses 2.0.0.AM3-SNAPSHOT in referenced in the pom.xml to supply Mina 2.1.2.
> Please let me know if I can provide additional information.
>
> [1]  https://hub.docker.com/r/shotoflove/guacamole-ldap/builds
> [2]
> https://github.com/michaelbarkdoll/guacamole-client/blob/jira/234/extensions/guacamole-auth-ldap/pom.xml
>
> Michael Barkdoll
>
>
> On Thu, Apr 25, 2019 at 6:57 PM Michael Barkdoll <ma...@gmail.com>
> wrote:
>
>> Hi Emmanuel,
>>
>> Yes, I built my Apache Guacamole github repo [1] last night using
>> DockerHub [2] before uploading the error reports in the PR [3].  The
>> container built from [2] uses a modified Dockerfile that git cloned the
>> directory-ldap-api github repo [4], so it was built using Mina version
>> 2.1.2, is there additional information that I can provide by adding
>> anything to the source code?
>>
>> [1] https://github.com/michaelbarkdoll/guacamole-client/tree/jira/234
>> [2]
>> https://cloud.docker.com/u/shotoflove/repository/docker/shotoflove/guacamole-ldap
>> [3] https://github.com/apache/guacamole-client/pull/345
>> [4] https://github.com/apache/directory-ldap-api
>>
>> Michael Barkdoll
>>
>>
>> On Thu, Apr 25, 2019 at 2:32 AM Emmanuel Lecharny <el...@apache.org>
>> wrote:
>>
>>> Actually, the pb is that the ldap api version you use is using a Mina
>>> version that us buggy, leading to this NPE. I think it has been fixed with
>>> Mina 2.1.2 that I released last friday, just check you are building the API
>>> with this version.
>>>
>>> Le jeu. 25 avr. 2019 à 09:22, Michael Barkdoll <ma...@gmail.com> a
>>> écrit :
>>>
>>>> Thanks, Stefan, that helped a lot!!!
>>>>
>>>> We'll my error with the 2.0.0.AM3-SNAPSHOT appears to be:
>>>>
>>>> [http-nio-8080-exec-9] ERROR o.a.d.l.c.api.LdapNetworkConnection -
>>>> ERR_04122_SSL_CONTEXT_INIT_FAILURE Failed to initialize the SSL context
>>>> vdi_guacamole2.1.iytle5jay8ee@swarm-3    |
>>>> java.lang.NullPointerException: null
>>>>
>>>> The complete error log is in my PR issue [1].  Anyway, I get this isn't
>>>> your issue now and mostly just wanted to thank you for pointing me in the
>>>> right direction.
>>>>
>>>> [1] https://github.com/apache/guacamole-client/pull/345
>>>>
>>>> *Michael Allen Barkdoll*
>>>>
>>>>
>>>>
>>>> On Wed, Apr 24, 2019 at 11:49 PM Stefan Seelmann <
>>>> mail@stefan-seelmann.de> wrote:
>>>>
>>>>> Hi Michael,
>>>>>
>>>>> On 4/24/19 10:45 PM, Michael Barkdoll wrote:
>>>>> > Hi,
>>>>> >
>>>>> > I'm trying to fix a bug that I'm experiencing in my Apache guacamole
>>>>> > deployment that relies upon Apache Directory api-all:
>>>>> >
>>>>> > https://mvnrepository.com/artifact/org.apache.directory.api/api-all
>>>>> >
>>>>> > pom.xml:
>>>>> >         <!-- Apache Directory LDAP API -->
>>>>> >         <dependency>
>>>>> >             <groupId>com.novell.ldap</groupId>
>>>>> >             <artifactId>jldap</artifactId>
>>>>> >             <version>4.3</version>
>>>>> >             <groupId>org.apache.directory.api</groupId>
>>>>> >             <artifactId>api-all</artifactId>
>>>>> >             <version>2.0.0.AM2</version>
>>>>> >             <exclusions>
>>>>> >                 <exclusion>
>>>>> >                     <groupId>org.slf4j</groupId>
>>>>> >                     <artifactId>slf4j-api</artifactId>
>>>>> >                 </exclusion>
>>>>> >             </exclusions>
>>>>> >         </dependency>
>>>>> >
>>>>> > This is due to possibly bug:
>>>>> >
>>>>> https://issues.apache.org/jira/browse/DIRSTUDIO-1197?page=com.atlassian.jira.plugin.system.issuetabpanels%3Aall-tabpanel
>>>>> >
>>>>> > Which has existed in the code base since August 18, 2017.  Can
>>>>> someone
>>>>> > please help me push out an update for this to the above mentioned
>>>>> repo or
>>>>> > tell me how I can compile it from source and insert the dependency
>>>>> in the
>>>>> > pom.xml from apache guacamole shown above.
>>>>>
>>>>> So you want to use the LDAP API in Gacamole project, nice :). But the
>>>>> Jira you refer to was about wrong usage of the LDAP API within Studio
>>>>> which was fixed by changing one parameter (the connection timeout).
>>>>>
>>>>> To clarify: Apache LDAP API is a Java library. Apache Directory Studio
>>>>> is the LDAP browser GUI application which uses the LDAP API library (as
>>>>> you do in Guacamole).
>>>>>
>>>>> The default timeout of the LDAP API (even in version 2.0.0.AM2) is 30
>>>>> seconds (30000ms), unless you configured something else.
>>>>>
>>>>> I assume your problem is about PR [1], right? So the error
>>>>> ERR_04122_SSL_CONTEXT_INIT_FAILURE which means the SSL/TLS cannot be
>>>>> established may have different root causes, not necessarily caused by a
>>>>> connection timeout, especially it happens when the server certificate
>>>>> is
>>>>> not valid. Unfortunately in LDAP API 2.0.0.AM2 the root cause is not
>>>>> reported in the error. This has been improved in master [2] but is not
>>>>> yet released.
>>>>>
>>>>> In the meanwhile you can build the current master: Checkout sources [3]
>>>>> and build with "mvn clean install -DskipTests", the artifacts are
>>>>> installed to your local Maven repo (~/.m2/repository), then change the
>>>>> version to "2.0.0.AM3-SNAPSHOT".
>>>>>
>>>>> > I tried to build from github:
>>>>> > https://github.com/apache/directory-studio
>>>>> >
>>>>> > The ./build.sh script ended in an error for me though and I'm not
>>>>> certain
>>>>> > how to take the built files from it and insert them directly into the
>>>>> > pom.xml.
>>>>>
>>>>> As said above, this would build Studio, not the LDAP API.
>>>>>
>>>>> Kind Regards,
>>>>> Stefan
>>>>>
>>>>> [1] https://github.com/apache/guacamole-client/pull/345
>>>>> [2] https://issues.apache.org/jira/browse/DIRAPI-330
>>>>> [3] https://github.com/apache/directory-ldap-api
>>>>>
>>>> --
>>> Regards,
>>> Cordialement,
>>> Emmanuel Lécharny
>>> www.iktek.com
>>>
>> --
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com

Re: Maven repo out of date

Posted by Michael Barkdoll <ma...@gmail.com>.
Sorry, my docker hub build link was invalid. I've updated it on this email
to [1] which has a link to the build output from github commit
source bd9ae3f  which should verify that it was built from the latest
github repository.  In [2] you can see the ldap extension
uses 2.0.0.AM3-SNAPSHOT in referenced in the pom.xml to supply Mina 2.1.2.
Please let me know if I can provide additional information.

[1]  https://hub.docker.com/r/shotoflove/guacamole-ldap/builds
[2]
https://github.com/michaelbarkdoll/guacamole-client/blob/jira/234/extensions/guacamole-auth-ldap/pom.xml

Michael Barkdoll


On Thu, Apr 25, 2019 at 6:57 PM Michael Barkdoll <ma...@gmail.com>
wrote:

> Hi Emmanuel,
>
> Yes, I built my Apache Guacamole github repo [1] last night using
> DockerHub [2] before uploading the error reports in the PR [3].  The
> container built from [2] uses a modified Dockerfile that git cloned the
> directory-ldap-api github repo [4], so it was built using Mina version
> 2.1.2, is there additional information that I can provide by adding
> anything to the source code?
>
> [1] https://github.com/michaelbarkdoll/guacamole-client/tree/jira/234
> [2]
> https://cloud.docker.com/u/shotoflove/repository/docker/shotoflove/guacamole-ldap
> [3] https://github.com/apache/guacamole-client/pull/345
> [4] https://github.com/apache/directory-ldap-api
>
> Michael Barkdoll
>
>
> On Thu, Apr 25, 2019 at 2:32 AM Emmanuel Lecharny <el...@apache.org>
> wrote:
>
>> Actually, the pb is that the ldap api version you use is using a Mina
>> version that us buggy, leading to this NPE. I think it has been fixed with
>> Mina 2.1.2 that I released last friday, just check you are building the API
>> with this version.
>>
>> Le jeu. 25 avr. 2019 à 09:22, Michael Barkdoll <ma...@gmail.com> a
>> écrit :
>>
>>> Thanks, Stefan, that helped a lot!!!
>>>
>>> We'll my error with the 2.0.0.AM3-SNAPSHOT appears to be:
>>>
>>> [http-nio-8080-exec-9] ERROR o.a.d.l.c.api.LdapNetworkConnection -
>>> ERR_04122_SSL_CONTEXT_INIT_FAILURE Failed to initialize the SSL context
>>> vdi_guacamole2.1.iytle5jay8ee@swarm-3    |
>>> java.lang.NullPointerException: null
>>>
>>> The complete error log is in my PR issue [1].  Anyway, I get this isn't
>>> your issue now and mostly just wanted to thank you for pointing me in the
>>> right direction.
>>>
>>> [1] https://github.com/apache/guacamole-client/pull/345
>>>
>>> *Michael Allen Barkdoll*
>>>
>>>
>>>
>>> On Wed, Apr 24, 2019 at 11:49 PM Stefan Seelmann <
>>> mail@stefan-seelmann.de> wrote:
>>>
>>>> Hi Michael,
>>>>
>>>> On 4/24/19 10:45 PM, Michael Barkdoll wrote:
>>>> > Hi,
>>>> >
>>>> > I'm trying to fix a bug that I'm experiencing in my Apache guacamole
>>>> > deployment that relies upon Apache Directory api-all:
>>>> >
>>>> > https://mvnrepository.com/artifact/org.apache.directory.api/api-all
>>>> >
>>>> > pom.xml:
>>>> >         <!-- Apache Directory LDAP API -->
>>>> >         <dependency>
>>>> >             <groupId>com.novell.ldap</groupId>
>>>> >             <artifactId>jldap</artifactId>
>>>> >             <version>4.3</version>
>>>> >             <groupId>org.apache.directory.api</groupId>
>>>> >             <artifactId>api-all</artifactId>
>>>> >             <version>2.0.0.AM2</version>
>>>> >             <exclusions>
>>>> >                 <exclusion>
>>>> >                     <groupId>org.slf4j</groupId>
>>>> >                     <artifactId>slf4j-api</artifactId>
>>>> >                 </exclusion>
>>>> >             </exclusions>
>>>> >         </dependency>
>>>> >
>>>> > This is due to possibly bug:
>>>> >
>>>> https://issues.apache.org/jira/browse/DIRSTUDIO-1197?page=com.atlassian.jira.plugin.system.issuetabpanels%3Aall-tabpanel
>>>> >
>>>> > Which has existed in the code base since August 18, 2017.  Can someone
>>>> > please help me push out an update for this to the above mentioned
>>>> repo or
>>>> > tell me how I can compile it from source and insert the dependency in
>>>> the
>>>> > pom.xml from apache guacamole shown above.
>>>>
>>>> So you want to use the LDAP API in Gacamole project, nice :). But the
>>>> Jira you refer to was about wrong usage of the LDAP API within Studio
>>>> which was fixed by changing one parameter (the connection timeout).
>>>>
>>>> To clarify: Apache LDAP API is a Java library. Apache Directory Studio
>>>> is the LDAP browser GUI application which uses the LDAP API library (as
>>>> you do in Guacamole).
>>>>
>>>> The default timeout of the LDAP API (even in version 2.0.0.AM2) is 30
>>>> seconds (30000ms), unless you configured something else.
>>>>
>>>> I assume your problem is about PR [1], right? So the error
>>>> ERR_04122_SSL_CONTEXT_INIT_FAILURE which means the SSL/TLS cannot be
>>>> established may have different root causes, not necessarily caused by a
>>>> connection timeout, especially it happens when the server certificate is
>>>> not valid. Unfortunately in LDAP API 2.0.0.AM2 the root cause is not
>>>> reported in the error. This has been improved in master [2] but is not
>>>> yet released.
>>>>
>>>> In the meanwhile you can build the current master: Checkout sources [3]
>>>> and build with "mvn clean install -DskipTests", the artifacts are
>>>> installed to your local Maven repo (~/.m2/repository), then change the
>>>> version to "2.0.0.AM3-SNAPSHOT".
>>>>
>>>> > I tried to build from github:
>>>> > https://github.com/apache/directory-studio
>>>> >
>>>> > The ./build.sh script ended in an error for me though and I'm not
>>>> certain
>>>> > how to take the built files from it and insert them directly into the
>>>> > pom.xml.
>>>>
>>>> As said above, this would build Studio, not the LDAP API.
>>>>
>>>> Kind Regards,
>>>> Stefan
>>>>
>>>> [1] https://github.com/apache/guacamole-client/pull/345
>>>> [2] https://issues.apache.org/jira/browse/DIRAPI-330
>>>> [3] https://github.com/apache/directory-ldap-api
>>>>
>>> --
>> Regards,
>> Cordialement,
>> Emmanuel Lécharny
>> www.iktek.com
>>
>

Re: Maven repo out of date

Posted by Michael Barkdoll <ma...@gmail.com>.
Hi Emmanuel,

Yes, I built my Apache Guacamole github repo [1] last night using DockerHub
[2] before uploading the error reports in the PR [3].  The container built
from [2] uses a modified Dockerfile that git cloned the directory-ldap-api
github repo [4], so it was built using Mina version 2.1.2, is there
additional information that I can provide by adding anything to the source
code?

[1] https://github.com/michaelbarkdoll/guacamole-client/tree/jira/234
[2]
https://cloud.docker.com/u/shotoflove/repository/docker/shotoflove/guacamole-ldap
[3] https://github.com/apache/guacamole-client/pull/345
[4] https://github.com/apache/directory-ldap-api

Michael Barkdoll


On Thu, Apr 25, 2019 at 2:32 AM Emmanuel Lecharny <el...@apache.org>
wrote:

> Actually, the pb is that the ldap api version you use is using a Mina
> version that us buggy, leading to this NPE. I think it has been fixed with
> Mina 2.1.2 that I released last friday, just check you are building the API
> with this version.
>
> Le jeu. 25 avr. 2019 à 09:22, Michael Barkdoll <ma...@gmail.com> a
> écrit :
>
>> Thanks, Stefan, that helped a lot!!!
>>
>> We'll my error with the 2.0.0.AM3-SNAPSHOT appears to be:
>>
>> [http-nio-8080-exec-9] ERROR o.a.d.l.c.api.LdapNetworkConnection -
>> ERR_04122_SSL_CONTEXT_INIT_FAILURE Failed to initialize the SSL context
>> vdi_guacamole2.1.iytle5jay8ee@swarm-3    |
>> java.lang.NullPointerException: null
>>
>> The complete error log is in my PR issue [1].  Anyway, I get this isn't
>> your issue now and mostly just wanted to thank you for pointing me in the
>> right direction.
>>
>> [1] https://github.com/apache/guacamole-client/pull/345
>>
>> *Michael Allen Barkdoll*
>>
>>
>>
>> On Wed, Apr 24, 2019 at 11:49 PM Stefan Seelmann <ma...@stefan-seelmann.de>
>> wrote:
>>
>>> Hi Michael,
>>>
>>> On 4/24/19 10:45 PM, Michael Barkdoll wrote:
>>> > Hi,
>>> >
>>> > I'm trying to fix a bug that I'm experiencing in my Apache guacamole
>>> > deployment that relies upon Apache Directory api-all:
>>> >
>>> > https://mvnrepository.com/artifact/org.apache.directory.api/api-all
>>> >
>>> > pom.xml:
>>> >         <!-- Apache Directory LDAP API -->
>>> >         <dependency>
>>> >             <groupId>com.novell.ldap</groupId>
>>> >             <artifactId>jldap</artifactId>
>>> >             <version>4.3</version>
>>> >             <groupId>org.apache.directory.api</groupId>
>>> >             <artifactId>api-all</artifactId>
>>> >             <version>2.0.0.AM2</version>
>>> >             <exclusions>
>>> >                 <exclusion>
>>> >                     <groupId>org.slf4j</groupId>
>>> >                     <artifactId>slf4j-api</artifactId>
>>> >                 </exclusion>
>>> >             </exclusions>
>>> >         </dependency>
>>> >
>>> > This is due to possibly bug:
>>> >
>>> https://issues.apache.org/jira/browse/DIRSTUDIO-1197?page=com.atlassian.jira.plugin.system.issuetabpanels%3Aall-tabpanel
>>> >
>>> > Which has existed in the code base since August 18, 2017.  Can someone
>>> > please help me push out an update for this to the above mentioned repo
>>> or
>>> > tell me how I can compile it from source and insert the dependency in
>>> the
>>> > pom.xml from apache guacamole shown above.
>>>
>>> So you want to use the LDAP API in Gacamole project, nice :). But the
>>> Jira you refer to was about wrong usage of the LDAP API within Studio
>>> which was fixed by changing one parameter (the connection timeout).
>>>
>>> To clarify: Apache LDAP API is a Java library. Apache Directory Studio
>>> is the LDAP browser GUI application which uses the LDAP API library (as
>>> you do in Guacamole).
>>>
>>> The default timeout of the LDAP API (even in version 2.0.0.AM2) is 30
>>> seconds (30000ms), unless you configured something else.
>>>
>>> I assume your problem is about PR [1], right? So the error
>>> ERR_04122_SSL_CONTEXT_INIT_FAILURE which means the SSL/TLS cannot be
>>> established may have different root causes, not necessarily caused by a
>>> connection timeout, especially it happens when the server certificate is
>>> not valid. Unfortunately in LDAP API 2.0.0.AM2 the root cause is not
>>> reported in the error. This has been improved in master [2] but is not
>>> yet released.
>>>
>>> In the meanwhile you can build the current master: Checkout sources [3]
>>> and build with "mvn clean install -DskipTests", the artifacts are
>>> installed to your local Maven repo (~/.m2/repository), then change the
>>> version to "2.0.0.AM3-SNAPSHOT".
>>>
>>> > I tried to build from github:
>>> > https://github.com/apache/directory-studio
>>> >
>>> > The ./build.sh script ended in an error for me though and I'm not
>>> certain
>>> > how to take the built files from it and insert them directly into the
>>> > pom.xml.
>>>
>>> As said above, this would build Studio, not the LDAP API.
>>>
>>> Kind Regards,
>>> Stefan
>>>
>>> [1] https://github.com/apache/guacamole-client/pull/345
>>> [2] https://issues.apache.org/jira/browse/DIRAPI-330
>>> [3] https://github.com/apache/directory-ldap-api
>>>
>> --
> Regards,
> Cordialement,
> Emmanuel Lécharny
> www.iktek.com
>

Re: Maven repo out of date

Posted by Emmanuel Lecharny <el...@apache.org>.
Actually, the pb is that the ldap api version you use is using a Mina
version that us buggy, leading to this NPE. I think it has been fixed with
Mina 2.1.2 that I released last friday, just check you are building the API
with this version.

Le jeu. 25 avr. 2019 à 09:22, Michael Barkdoll <ma...@gmail.com> a
écrit :

> Thanks, Stefan, that helped a lot!!!
>
> We'll my error with the 2.0.0.AM3-SNAPSHOT appears to be:
>
> [http-nio-8080-exec-9] ERROR o.a.d.l.c.api.LdapNetworkConnection -
> ERR_04122_SSL_CONTEXT_INIT_FAILURE Failed to initialize the SSL context
> vdi_guacamole2.1.iytle5jay8ee@swarm-3    |
> java.lang.NullPointerException: null
>
> The complete error log is in my PR issue [1].  Anyway, I get this isn't
> your issue now and mostly just wanted to thank you for pointing me in the
> right direction.
>
> [1] https://github.com/apache/guacamole-client/pull/345
>
> *Michael Allen Barkdoll*
>
>
>
> On Wed, Apr 24, 2019 at 11:49 PM Stefan Seelmann <ma...@stefan-seelmann.de>
> wrote:
>
>> Hi Michael,
>>
>> On 4/24/19 10:45 PM, Michael Barkdoll wrote:
>> > Hi,
>> >
>> > I'm trying to fix a bug that I'm experiencing in my Apache guacamole
>> > deployment that relies upon Apache Directory api-all:
>> >
>> > https://mvnrepository.com/artifact/org.apache.directory.api/api-all
>> >
>> > pom.xml:
>> >         <!-- Apache Directory LDAP API -->
>> >         <dependency>
>> >             <groupId>com.novell.ldap</groupId>
>> >             <artifactId>jldap</artifactId>
>> >             <version>4.3</version>
>> >             <groupId>org.apache.directory.api</groupId>
>> >             <artifactId>api-all</artifactId>
>> >             <version>2.0.0.AM2</version>
>> >             <exclusions>
>> >                 <exclusion>
>> >                     <groupId>org.slf4j</groupId>
>> >                     <artifactId>slf4j-api</artifactId>
>> >                 </exclusion>
>> >             </exclusions>
>> >         </dependency>
>> >
>> > This is due to possibly bug:
>> >
>> https://issues.apache.org/jira/browse/DIRSTUDIO-1197?page=com.atlassian.jira.plugin.system.issuetabpanels%3Aall-tabpanel
>> >
>> > Which has existed in the code base since August 18, 2017.  Can someone
>> > please help me push out an update for this to the above mentioned repo
>> or
>> > tell me how I can compile it from source and insert the dependency in
>> the
>> > pom.xml from apache guacamole shown above.
>>
>> So you want to use the LDAP API in Gacamole project, nice :). But the
>> Jira you refer to was about wrong usage of the LDAP API within Studio
>> which was fixed by changing one parameter (the connection timeout).
>>
>> To clarify: Apache LDAP API is a Java library. Apache Directory Studio
>> is the LDAP browser GUI application which uses the LDAP API library (as
>> you do in Guacamole).
>>
>> The default timeout of the LDAP API (even in version 2.0.0.AM2) is 30
>> seconds (30000ms), unless you configured something else.
>>
>> I assume your problem is about PR [1], right? So the error
>> ERR_04122_SSL_CONTEXT_INIT_FAILURE which means the SSL/TLS cannot be
>> established may have different root causes, not necessarily caused by a
>> connection timeout, especially it happens when the server certificate is
>> not valid. Unfortunately in LDAP API 2.0.0.AM2 the root cause is not
>> reported in the error. This has been improved in master [2] but is not
>> yet released.
>>
>> In the meanwhile you can build the current master: Checkout sources [3]
>> and build with "mvn clean install -DskipTests", the artifacts are
>> installed to your local Maven repo (~/.m2/repository), then change the
>> version to "2.0.0.AM3-SNAPSHOT".
>>
>> > I tried to build from github:
>> > https://github.com/apache/directory-studio
>> >
>> > The ./build.sh script ended in an error for me though and I'm not
>> certain
>> > how to take the built files from it and insert them directly into the
>> > pom.xml.
>>
>> As said above, this would build Studio, not the LDAP API.
>>
>> Kind Regards,
>> Stefan
>>
>> [1] https://github.com/apache/guacamole-client/pull/345
>> [2] https://issues.apache.org/jira/browse/DIRAPI-330
>> [3] https://github.com/apache/directory-ldap-api
>>
> --
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com

Re: Maven repo out of date

Posted by Michael Barkdoll <ma...@gmail.com>.
Thanks, Stefan, that helped a lot!!!

We'll my error with the 2.0.0.AM3-SNAPSHOT appears to be:

[http-nio-8080-exec-9] ERROR o.a.d.l.c.api.LdapNetworkConnection -
ERR_04122_SSL_CONTEXT_INIT_FAILURE Failed to initialize the SSL context
vdi_guacamole2.1.iytle5jay8ee@swarm-3    | java.lang.NullPointerException:
null

The complete error log is in my PR issue [1].  Anyway, I get this isn't
your issue now and mostly just wanted to thank you for pointing me in the
right direction.

[1] https://github.com/apache/guacamole-client/pull/345

*Michael Allen Barkdoll*



On Wed, Apr 24, 2019 at 11:49 PM Stefan Seelmann <ma...@stefan-seelmann.de>
wrote:

> Hi Michael,
>
> On 4/24/19 10:45 PM, Michael Barkdoll wrote:
> > Hi,
> >
> > I'm trying to fix a bug that I'm experiencing in my Apache guacamole
> > deployment that relies upon Apache Directory api-all:
> >
> > https://mvnrepository.com/artifact/org.apache.directory.api/api-all
> >
> > pom.xml:
> >         <!-- Apache Directory LDAP API -->
> >         <dependency>
> >             <groupId>com.novell.ldap</groupId>
> >             <artifactId>jldap</artifactId>
> >             <version>4.3</version>
> >             <groupId>org.apache.directory.api</groupId>
> >             <artifactId>api-all</artifactId>
> >             <version>2.0.0.AM2</version>
> >             <exclusions>
> >                 <exclusion>
> >                     <groupId>org.slf4j</groupId>
> >                     <artifactId>slf4j-api</artifactId>
> >                 </exclusion>
> >             </exclusions>
> >         </dependency>
> >
> > This is due to possibly bug:
> >
> https://issues.apache.org/jira/browse/DIRSTUDIO-1197?page=com.atlassian.jira.plugin.system.issuetabpanels%3Aall-tabpanel
> >
> > Which has existed in the code base since August 18, 2017.  Can someone
> > please help me push out an update for this to the above mentioned repo or
> > tell me how I can compile it from source and insert the dependency in the
> > pom.xml from apache guacamole shown above.
>
> So you want to use the LDAP API in Gacamole project, nice :). But the
> Jira you refer to was about wrong usage of the LDAP API within Studio
> which was fixed by changing one parameter (the connection timeout).
>
> To clarify: Apache LDAP API is a Java library. Apache Directory Studio
> is the LDAP browser GUI application which uses the LDAP API library (as
> you do in Guacamole).
>
> The default timeout of the LDAP API (even in version 2.0.0.AM2) is 30
> seconds (30000ms), unless you configured something else.
>
> I assume your problem is about PR [1], right? So the error
> ERR_04122_SSL_CONTEXT_INIT_FAILURE which means the SSL/TLS cannot be
> established may have different root causes, not necessarily caused by a
> connection timeout, especially it happens when the server certificate is
> not valid. Unfortunately in LDAP API 2.0.0.AM2 the root cause is not
> reported in the error. This has been improved in master [2] but is not
> yet released.
>
> In the meanwhile you can build the current master: Checkout sources [3]
> and build with "mvn clean install -DskipTests", the artifacts are
> installed to your local Maven repo (~/.m2/repository), then change the
> version to "2.0.0.AM3-SNAPSHOT".
>
> > I tried to build from github:
> > https://github.com/apache/directory-studio
> >
> > The ./build.sh script ended in an error for me though and I'm not certain
> > how to take the built files from it and insert them directly into the
> > pom.xml.
>
> As said above, this would build Studio, not the LDAP API.
>
> Kind Regards,
> Stefan
>
> [1] https://github.com/apache/guacamole-client/pull/345
> [2] https://issues.apache.org/jira/browse/DIRAPI-330
> [3] https://github.com/apache/directory-ldap-api
>

Re: Maven repo out of date

Posted by Stefan Seelmann <ma...@stefan-seelmann.de>.
Hi Michael,

On 4/24/19 10:45 PM, Michael Barkdoll wrote:
> Hi,
> 
> I'm trying to fix a bug that I'm experiencing in my Apache guacamole
> deployment that relies upon Apache Directory api-all:
> 
> https://mvnrepository.com/artifact/org.apache.directory.api/api-all
> 
> pom.xml:
>         <!-- Apache Directory LDAP API -->
>         <dependency>
>             <groupId>com.novell.ldap</groupId>
>             <artifactId>jldap</artifactId>
>             <version>4.3</version>
>             <groupId>org.apache.directory.api</groupId>
>             <artifactId>api-all</artifactId>
>             <version>2.0.0.AM2</version>
>             <exclusions>
>                 <exclusion>
>                     <groupId>org.slf4j</groupId>
>                     <artifactId>slf4j-api</artifactId>
>                 </exclusion>
>             </exclusions>
>         </dependency>
> 
> This is due to possibly bug:
> https://issues.apache.org/jira/browse/DIRSTUDIO-1197?page=com.atlassian.jira.plugin.system.issuetabpanels%3Aall-tabpanel
> 
> Which has existed in the code base since August 18, 2017.  Can someone
> please help me push out an update for this to the above mentioned repo or
> tell me how I can compile it from source and insert the dependency in the
> pom.xml from apache guacamole shown above.

So you want to use the LDAP API in Gacamole project, nice :). But the
Jira you refer to was about wrong usage of the LDAP API within Studio
which was fixed by changing one parameter (the connection timeout).

To clarify: Apache LDAP API is a Java library. Apache Directory Studio
is the LDAP browser GUI application which uses the LDAP API library (as
you do in Guacamole).

The default timeout of the LDAP API (even in version 2.0.0.AM2) is 30
seconds (30000ms), unless you configured something else.

I assume your problem is about PR [1], right? So the error
ERR_04122_SSL_CONTEXT_INIT_FAILURE which means the SSL/TLS cannot be
established may have different root causes, not necessarily caused by a
connection timeout, especially it happens when the server certificate is
not valid. Unfortunately in LDAP API 2.0.0.AM2 the root cause is not
reported in the error. This has been improved in master [2] but is not
yet released.

In the meanwhile you can build the current master: Checkout sources [3]
and build with "mvn clean install -DskipTests", the artifacts are
installed to your local Maven repo (~/.m2/repository), then change the
version to "2.0.0.AM3-SNAPSHOT".

> I tried to build from github:
> https://github.com/apache/directory-studio
> 
> The ./build.sh script ended in an error for me though and I'm not certain
> how to take the built files from it and insert them directly into the
> pom.xml.

As said above, this would build Studio, not the LDAP API.

Kind Regards,
Stefan

[1] https://github.com/apache/guacamole-client/pull/345
[2] https://issues.apache.org/jira/browse/DIRAPI-330
[3] https://github.com/apache/directory-ldap-api