[ 
https://issues.apache.org/jira/browse/DIRSTUDIO-487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12713173#action_12713173
 ] 

James Brown commented on DIRSTUDIO-487:
---------------------------------------

Stefan-

I am not an expert on domino, but as I now understand it this single null-byte 
value for namingcontexts is a bug that is supposed to be remedied at some 
point.  This appears to be aan issue with at least Lotus Domino R5.x, R6.x and 
R7.0.x.

performaing a one level search works, no issue.

ldapsearch -h <host> -x -b "" -s one "objectclass=*"

# extended LDIF
#
# LDAPv3
# base <> with scope one
# filter: objectclass=*
# requesting: ALL
#

# Administration Requests
dn: CN=Administration Requests
cn: Administration Requests
mail: administration_requests%[email protected]
maildomain: domain
objectclass: dominoServerMailInDatabase
objectclass: top

# BE
dn: C=BE
c: BE
objectclass: country
objectclass: top

...
...

# search result
search: 2
result: 0 Success

# numResponses: 19
# numEntries: 18


> empty namingcontexts causes javax.naming.InvalidNameException: Bad DN
> ---------------------------------------------------------------------
>
>                 Key: DIRSTUDIO-487
>                 URL: https://issues.apache.org/jira/browse/DIRSTUDIO-487
>             Project: Directory Studio
>          Issue Type: Improvement
>    Affects Versions: 1.4.0
>         Environment: Domino 7, Exchange 5.5
>            Reporter: James Brown
>            Priority: Minor
>
> When attempting to connect to domino server with an empty namingcontexts, 
> using option to get base DNs from Root DSE (or leaving as empty), an error is 
> generated and DIT does not display.
> Problem Occurred popup when fetching Base DNs:
> Error while fetching base DNs
>  - Can't set Base DN entry
>  - Bad DN : 
> javax.naming.InvalidNameException: Bad DN : 
> Modification Logs when connecting:
> #!RESULT ERROR
> #!CONNECTION ldap://10.x.x.x:389
> #!DATE 2009-04-24T12:04:10.247
> #!ERROR [LDAP: error code 89 - No given DN]
> dn: 
> changetype: modify
> add: namingcontexts
> namingcontexts: o=mydomain
> -
> And Domino Root DSE:
> objectClass: top
> namingcontexts: 
> subschemasubentry: cn=schema
> supportedextension: 1.3.6.1.4.1.1466.20037
> supportedextension: LanguageCodes
> supportedldapversion: 2
> supportedldapversion: 3
> supportedschemamechanisms: EXTERNAL
> vendorname: IBM Lotus Software
> vendorversion: Release 7.0.2

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.

Reply via email to