directory-users mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bill MacAllister <...@stanford.edu>
Subject Re: ADS 2.0 and LDAP Provider
Date Fri, 20 Jan 2012 20:12:14 GMT


--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


Mime
View raw message