[
https://issues.apache.org/jira/browse/DIRSTUDIO-487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12713152#action_12713152
]
Stefan Seelmann commented on DIRSTUDIO-487:
-------------------------------------------
Thanks James for the update.
What a mess. Where does this null-byte come from? Is it default for a Domino
server or was this added by configuration?
Anyway, the question is, if and how Studio should handle this situation.
According to RFC 4514 and 2253 this is not valid. I don't know if this
null-byte has a special meaning.
We could just left-trim the namingcontexts value, then is becomes the empty
string. In that case a one-level search using the RootDSE as search base would
be performed.
James, could you please try to do such a one-level, just to see if some results
are returned?
> 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.
