You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by Bill MacAllister <wh...@stanford.edu> on 2012/01/20 01:34:40 UTC
ADS 2.0 and LDAP Provider
Using ADS 2.0 on my Debian/Wheezy system I get the following error
when I connect to our OpenLDAP directory servers using Apache Directory
LDAP Client API
Error while opening connection
- Missing schema location in RootDSE, using default schema.
Missing schema location in RootDSE, using default schema.
When I switch to JNDI the connection succeeds.
Bill
--
Bill MacAllister
Infrastructure Delivery Group, Stanford University
Re: ADS 2.0 and LDAP Provider
Posted by Bill MacAllister <wh...@stanford.edu>.
--On Friday, January 20, 2012 07:51:24 AM +0100 Emmanuel Lecharny <el...@gmail.com> wrote:
> On 1/20/12 1:34 AM, Bill MacAllister wrote:
>> Using ADS 2.0 on my Debian/Wheezy system I get the following error
>> when I connect to our OpenLDAP directory servers using Apache Directory
>> LDAP Client API
>>
>> Error while opening connection
>> - Missing schema location in RootDSE, using default schema.
>> Missing schema location in RootDSE, using default schema.
>>
>> When I switch to JNDI the connection succeeds.
> Hi,
>
> can you create a JIRA for this ? It's clearly a bug, and we would like to track it.
>
> Thanks !
Done. https://issues.apache.org/jira/browse/DIRSTUDIO-761
Bill
--
Bill MacAllister
Infrastructure Delivery Group, Stanford University
Re: ADS 2.0 and LDAP Provider
Posted by Pierre-Arnaud Marcelot <pa...@gmail.com>.
Le 20 janv. 2012 à 21:12, Bill MacAllister <wh...@stanford.edu> a écrit :
> --On Friday, January 20, 2012 08:20:33 PM +0100 Pierre-Arnaud Marcelot <pa...@marcelot.net> wrote:
>
>> On 20 janv. 2012, at 20:04, Bill MacAllister wrote:
>>
>>> --On Friday, January 20, 2012 08:01:24 AM +0100 Pierre-Arnaud Marcelot <pa...@marcelot.net> wrote:
>>>
>>>> Hi Biil, Emmanuel,
>>>>
>>>> On 20 janv. 2012, at 07:51, Emmanuel Lecharny wrote:
>>>>
>>>>> On 1/20/12 1:34 AM, Bill MacAllister wrote:
>>>>>> Using ADS 2.0 on my Debian/Wheezy system I get the following error
>>>>>> when I connect to our OpenLDAP directory servers using Apache Directory
>>>>>> LDAP Client API
>>>>>>
>>>>>> Error while opening connection
>>>>>> - Missing schema location in RootDSE, using default schema.
>>>>>> Missing schema location in RootDSE, using default schema.
>>>>>>
>>>>>> When I switch to JNDI the connection succeeds.
>>>>> Hi,
>>>>>
>>>>> can you create a JIRA for this ? It's clearly a bug, and we would like to track it.
>>>>
>>>> Can you also send us an LDIF file with the contents of your RootDSE, please?
>>>>
>>>
>>> Sure. Added it to the Jira ticket as well.
>>>
>>> % ldapsearch -x -h ldap -b '' -s base +
>>> # extended LDIF
>>> #
>>> # LDAPv3
>>> # base <> with scope baseObject
>>> # filter: (objectclass=*)
>>> # requesting: +
>>> #
>>>
>>> #
>>> dn:
>>> structuralObjectClass: OpenLDAProotDSE
>>> configContext: cn=config
>>> namingContexts: dc=stanford,dc=edu
>>> monitorContext: cn=Monitor
>>> supportedControl: 2.16.840.1.113730.3.4.18
>>> supportedControl: 2.16.840.1.113730.3.4.2
>>> supportedControl: 1.3.6.1.4.1.4203.1.10.1
>>> supportedControl: 1.2.840.113556.1.4.319
>>> supportedControl: 1.2.826.0.1.3344810.2.3
>>> supportedControl: 1.3.6.1.1.13.2
>>> supportedControl: 1.3.6.1.1.13.1
>>> supportedControl: 1.3.6.1.1.12
>>> supportedExtension: 1.3.6.1.4.1.1466.20037
>>> supportedExtension: 1.3.6.1.4.1.4203.1.11.1
>>> supportedExtension: 1.3.6.1.4.1.4203.1.11.3
>>> supportedExtension: 1.3.6.1.1.8
>>> supportedFeatures: 1.3.6.1.1.14
>>> supportedFeatures: 1.3.6.1.4.1.4203.1.5.1
>>> supportedFeatures: 1.3.6.1.4.1.4203.1.5.2
>>> supportedFeatures: 1.3.6.1.4.1.4203.1.5.3
>>> supportedFeatures: 1.3.6.1.4.1.4203.1.5.4
>>> supportedFeatures: 1.3.6.1.4.1.4203.1.5.5
>>> supportedLDAPVersion: 3
>>> supportedSASLMechanisms: GSSAPI
>>> entryDN:
>>> subschemaSubentry: cn=Subschema
>>
>> Thanks!
>>
>> BTW, is this issue a direct consequence of the other issue you're
>> having with the GSSAPI bind with the Apache Directory LDAP API?
>>
>> Do you have first the "javax.security.auth.login.LoginException:
>> Could not load configuration from SCDynamicStore" error, and then,
>> this other one?
>
> This issue is completely separate. I am seeing this on my Debian
> desktop system. The SCDynamicStore error is specific to Mac OS X.
Ok, thanks. Sorry, I didn't notice you mentioned it.
By any chance, is the server available online and could I try to debug
the issue on it?
Regards,
Pierre-Arnaud
> Bill
>
>
> --
>
> Bill MacAllister
> Infrastructure Delivery Group, Stanford University
>
Re: ADS 2.0 and LDAP Provider
Posted by Bill MacAllister <wh...@stanford.edu>.
--On Friday, January 20, 2012 08:20:33 PM +0100 Pierre-Arnaud Marcelot <pa...@marcelot.net> wrote:
> On 20 janv. 2012, at 20:04, Bill MacAllister wrote:
>
>> --On Friday, January 20, 2012 08:01:24 AM +0100 Pierre-Arnaud Marcelot <pa...@marcelot.net> wrote:
>>
>>> Hi Biil, Emmanuel,
>>>
>>> On 20 janv. 2012, at 07:51, Emmanuel Lecharny wrote:
>>>
>>>> On 1/20/12 1:34 AM, Bill MacAllister wrote:
>>>>> Using ADS 2.0 on my Debian/Wheezy system I get the following error
>>>>> when I connect to our OpenLDAP directory servers using Apache Directory
>>>>> LDAP Client API
>>>>>
>>>>> Error while opening connection
>>>>> - Missing schema location in RootDSE, using default schema.
>>>>> Missing schema location in RootDSE, using default schema.
>>>>>
>>>>> When I switch to JNDI the connection succeeds.
>>>> Hi,
>>>>
>>>> can you create a JIRA for this ? It's clearly a bug, and we would like to track it.
>>>
>>> Can you also send us an LDIF file with the contents of your RootDSE, please?
>>>
>>
>> Sure. Added it to the Jira ticket as well.
>>
>> % ldapsearch -x -h ldap -b '' -s base +
>> # extended LDIF
>> #
>> # LDAPv3
>> # base <> with scope baseObject
>> # filter: (objectclass=*)
>> # requesting: +
>> #
>>
>> #
>> dn:
>> structuralObjectClass: OpenLDAProotDSE
>> configContext: cn=config
>> namingContexts: dc=stanford,dc=edu
>> monitorContext: cn=Monitor
>> supportedControl: 2.16.840.1.113730.3.4.18
>> supportedControl: 2.16.840.1.113730.3.4.2
>> supportedControl: 1.3.6.1.4.1.4203.1.10.1
>> supportedControl: 1.2.840.113556.1.4.319
>> supportedControl: 1.2.826.0.1.3344810.2.3
>> supportedControl: 1.3.6.1.1.13.2
>> supportedControl: 1.3.6.1.1.13.1
>> supportedControl: 1.3.6.1.1.12
>> supportedExtension: 1.3.6.1.4.1.1466.20037
>> supportedExtension: 1.3.6.1.4.1.4203.1.11.1
>> supportedExtension: 1.3.6.1.4.1.4203.1.11.3
>> supportedExtension: 1.3.6.1.1.8
>> supportedFeatures: 1.3.6.1.1.14
>> supportedFeatures: 1.3.6.1.4.1.4203.1.5.1
>> supportedFeatures: 1.3.6.1.4.1.4203.1.5.2
>> supportedFeatures: 1.3.6.1.4.1.4203.1.5.3
>> supportedFeatures: 1.3.6.1.4.1.4203.1.5.4
>> supportedFeatures: 1.3.6.1.4.1.4203.1.5.5
>> supportedLDAPVersion: 3
>> supportedSASLMechanisms: GSSAPI
>> entryDN:
>> subschemaSubentry: cn=Subschema
>
> Thanks!
>
> BTW, is this issue a direct consequence of the other issue you're
> having with the GSSAPI bind with the Apache Directory LDAP API?
>
> Do you have first the "javax.security.auth.login.LoginException:
> Could not load configuration from SCDynamicStore" error, and then,
> this other one?
This issue is completely separate. I am seeing this on my Debian
desktop system. The SCDynamicStore error is specific to Mac OS X.
Bill
--
Bill MacAllister
Infrastructure Delivery Group, Stanford University
Re: ADS 2.0 and LDAP Provider
Posted by Pierre-Arnaud Marcelot <pa...@marcelot.net>.
On 20 janv. 2012, at 20:04, Bill MacAllister wrote:
> --On Friday, January 20, 2012 08:01:24 AM +0100 Pierre-Arnaud Marcelot <pa...@marcelot.net> wrote:
>
>> Hi Biil, Emmanuel,
>>
>> On 20 janv. 2012, at 07:51, Emmanuel Lecharny wrote:
>>
>>> On 1/20/12 1:34 AM, Bill MacAllister wrote:
>>>> Using ADS 2.0 on my Debian/Wheezy system I get the following error
>>>> when I connect to our OpenLDAP directory servers using Apache Directory
>>>> LDAP Client API
>>>>
>>>> Error while opening connection
>>>> - Missing schema location in RootDSE, using default schema.
>>>> Missing schema location in RootDSE, using default schema.
>>>>
>>>> When I switch to JNDI the connection succeeds.
>>> Hi,
>>>
>>> can you create a JIRA for this ? It's clearly a bug, and we would like to track it.
>>
>> Can you also send us an LDIF file with the contents of your RootDSE, please?
>>
>
> Sure. Added it to the Jira ticket as well.
>
> % ldapsearch -x -h ldap -b '' -s base +
> # extended LDIF
> #
> # LDAPv3
> # base <> with scope baseObject
> # filter: (objectclass=*)
> # requesting: +
> #
>
> #
> dn:
> structuralObjectClass: OpenLDAProotDSE
> configContext: cn=config
> namingContexts: dc=stanford,dc=edu
> monitorContext: cn=Monitor
> supportedControl: 2.16.840.1.113730.3.4.18
> supportedControl: 2.16.840.1.113730.3.4.2
> supportedControl: 1.3.6.1.4.1.4203.1.10.1
> supportedControl: 1.2.840.113556.1.4.319
> supportedControl: 1.2.826.0.1.3344810.2.3
> supportedControl: 1.3.6.1.1.13.2
> supportedControl: 1.3.6.1.1.13.1
> supportedControl: 1.3.6.1.1.12
> supportedExtension: 1.3.6.1.4.1.1466.20037
> supportedExtension: 1.3.6.1.4.1.4203.1.11.1
> supportedExtension: 1.3.6.1.4.1.4203.1.11.3
> supportedExtension: 1.3.6.1.1.8
> supportedFeatures: 1.3.6.1.1.14
> supportedFeatures: 1.3.6.1.4.1.4203.1.5.1
> supportedFeatures: 1.3.6.1.4.1.4203.1.5.2
> supportedFeatures: 1.3.6.1.4.1.4203.1.5.3
> supportedFeatures: 1.3.6.1.4.1.4203.1.5.4
> supportedFeatures: 1.3.6.1.4.1.4203.1.5.5
> supportedLDAPVersion: 3
> supportedSASLMechanisms: GSSAPI
> entryDN:
> subschemaSubentry: cn=Subschema
Thanks!
BTW, is this issue a direct consequence of the other issue you're having with the GSSAPI bind with the Apache Directory LDAP API?
Do you have first the "javax.security.auth.login.LoginException: Could not load configuration from SCDynamicStore" error, and then, this other one?
Regards,
Pierre-Arnaud
> Bill
>
> --
>
> Bill MacAllister
> Infrastructure Delivery Group, Stanford University
>
Re: ADS 2.0 and LDAP Provider
Posted by Bill MacAllister <wh...@stanford.edu>.
--On Friday, January 20, 2012 08:01:24 AM +0100 Pierre-Arnaud Marcelot <pa...@marcelot.net> wrote:
> Hi Biil, Emmanuel,
>
> On 20 janv. 2012, at 07:51, Emmanuel Lecharny wrote:
>
>> On 1/20/12 1:34 AM, Bill MacAllister wrote:
>>> Using ADS 2.0 on my Debian/Wheezy system I get the following error
>>> when I connect to our OpenLDAP directory servers using Apache Directory
>>> LDAP Client API
>>>
>>> Error while opening connection
>>> - Missing schema location in RootDSE, using default schema.
>>> Missing schema location in RootDSE, using default schema.
>>>
>>> When I switch to JNDI the connection succeeds.
>> Hi,
>>
>> can you create a JIRA for this ? It's clearly a bug, and we would like to track it.
>
> Can you also send us an LDIF file with the contents of your RootDSE, please?
>
Sure. Added it to the Jira ticket as well.
% ldapsearch -x -h ldap -b '' -s base +
# extended LDIF
#
# LDAPv3
# base <> with scope baseObject
# filter: (objectclass=*)
# requesting: +
#
#
dn:
structuralObjectClass: OpenLDAProotDSE
configContext: cn=config
namingContexts: dc=stanford,dc=edu
monitorContext: cn=Monitor
supportedControl: 2.16.840.1.113730.3.4.18
supportedControl: 2.16.840.1.113730.3.4.2
supportedControl: 1.3.6.1.4.1.4203.1.10.1
supportedControl: 1.2.840.113556.1.4.319
supportedControl: 1.2.826.0.1.3344810.2.3
supportedControl: 1.3.6.1.1.13.2
supportedControl: 1.3.6.1.1.13.1
supportedControl: 1.3.6.1.1.12
supportedExtension: 1.3.6.1.4.1.1466.20037
supportedExtension: 1.3.6.1.4.1.4203.1.11.1
supportedExtension: 1.3.6.1.4.1.4203.1.11.3
supportedExtension: 1.3.6.1.1.8
supportedFeatures: 1.3.6.1.1.14
supportedFeatures: 1.3.6.1.4.1.4203.1.5.1
supportedFeatures: 1.3.6.1.4.1.4203.1.5.2
supportedFeatures: 1.3.6.1.4.1.4203.1.5.3
supportedFeatures: 1.3.6.1.4.1.4203.1.5.4
supportedFeatures: 1.3.6.1.4.1.4203.1.5.5
supportedLDAPVersion: 3
supportedSASLMechanisms: GSSAPI
entryDN:
subschemaSubentry: cn=Subschema
Bill
--
Bill MacAllister
Infrastructure Delivery Group, Stanford University
Re: ADS 2.0 and LDAP Provider
Posted by Pierre-Arnaud Marcelot <pa...@marcelot.net>.
Hi Biil, Emmanuel,
On 20 janv. 2012, at 07:51, Emmanuel Lecharny wrote:
> On 1/20/12 1:34 AM, Bill MacAllister wrote:
>> Using ADS 2.0 on my Debian/Wheezy system I get the following error
>> when I connect to our OpenLDAP directory servers using Apache Directory
>> LDAP Client API
>>
>> Error while opening connection
>> - Missing schema location in RootDSE, using default schema.
>> Missing schema location in RootDSE, using default schema.
>>
>> When I switch to JNDI the connection succeeds.
> Hi,
>
> can you create a JIRA for this ? It's clearly a bug, and we would like to track it.
Can you also send us an LDIF file with the contents of your RootDSE, please?
Thanks,
Pierre-Arnaud
> Thanks !
>
>
> --
> Regards,
> Cordialement,
> Emmanuel Lécharny
> www.iktek.com
>
Re: ADS 2.0 and LDAP Provider
Posted by Emmanuel Lecharny <el...@gmail.com>.
On 1/20/12 1:34 AM, Bill MacAllister wrote:
> Using ADS 2.0 on my Debian/Wheezy system I get the following error
> when I connect to our OpenLDAP directory servers using Apache Directory
> LDAP Client API
>
> Error while opening connection
> - Missing schema location in RootDSE, using default schema.
> Missing schema location in RootDSE, using default schema.
>
> When I switch to JNDI the connection succeeds.
Hi,
can you create a JIRA for this ? It's clearly a bug, and we would like
to track it.
Thanks !
--
Regards,
Cordialement,
Emmanuel Lécharny
www.iktek.com