You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "James Brown (JIRA)" <ji...@apache.org> on 2009/04/24 23:39:30 UTC
[jira] Created: (DIRSTUDIO-487) empty namingcontexts causes
javax.naming.InvalidNameException: Bad DN
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.
[jira] Commented: (DIRSTUDIO-487) empty namingcontexts causes
javax.naming.InvalidNameException: Bad DN
Posted by "Stefan Seelmann (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Commented: (DIRSTUDIO-487) empty namingcontexts causes
javax.naming.InvalidNameException: Bad DN
Posted by "James Brown (JIRA)" <ji...@apache.org>.
[ 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%domain@domain.com
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.
[jira] Updated: (DIRSTUDIO-487) Empty namingcontexts causes
javax.naming.InvalidNameException: Bad DN
Posted by "Pierre-Arnaud Marcelot (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSTUDIO-487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pierre-Arnaud Marcelot updated DIRSTUDIO-487:
---------------------------------------------
Summary: Empty namingcontexts causes javax.naming.InvalidNameException: Bad DN (was: empty namingcontexts causes javax.naming.InvalidNameException: Bad DN)
> 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
> Components: studio-ldapbrowser
> Affects Versions: 1.4.0
> Environment: Domino 7, Exchange 5.5
> Reporter: James Brown
> Assignee: Stefan Seelmann
> Priority: Minor
> Fix For: 1.5.0
>
>
> 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.
[jira] Commented: (DIRSTUDIO-487) empty namingcontexts causes
javax.naming.InvalidNameException: Bad DN
Posted by "James Brown (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSTUDIO-487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12713106#action_12713106 ]
James Brown commented on DIRSTUDIO-487:
---------------------------------------
Stefan-
Thanks for investigating.
Using a different version of ldapsych, it does appear that this is using a single null-byte value for namingcontexts.
dn:
objectclass: top
subschemasubentry: cn=schema
namingcontexts:: AA==
supportedextension: 1.3.6.1.4.1.1466.20037
supportedextension: LanguageCodes
supportedsaslmechanisms: EXTERNAL
supportedldapversion: 3
supportedldapversion: 2
vendorname: IBM Lotus Software
vendorversion: Release 7.0.2
> 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.
[jira] Commented: (DIRSTUDIO-487) empty namingcontexts causes
javax.naming.InvalidNameException: Bad DN
Posted by "James Brown (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSTUDIO-487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12713111#action_12713111 ]
James Brown commented on DIRSTUDIO-487:
---------------------------------------
sorry, should read ...using a different version of ldapsearch....
> 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.
[jira] Commented: (DIRSTUDIO-487) empty namingcontexts causes
javax.naming.InvalidNameException: Bad DN
Posted by "Stefan Seelmann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSTUDIO-487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12712593#action_12712593 ]
Stefan Seelmann commented on DIRSTUDIO-487:
-------------------------------------------
Hi James,
thanks for your report.
I checked the code. Your reported error "Can't set Base DN entry" is only thrown in one case: if the namingContext is _not_ empty, but the DN can't be parsed, I just added the code snippet below. I was able to reproduce your error by setting namingContext to the space or newline character. Could you please check if the namingcontexts of the domino server is really empty or if there is some whitespace? Nevertheless it makes sense to trim() the value in the code...
--------------------------------------------------------------------------------------------------
if ( !"".equals( namingContext ) ) //$NON-NLS-1$
{
try
{
LdapDN dn = new LdapDN( namingContext );
...
}
catch ( InvalidNameException e )
{
monitor.reportError( BrowserCoreMessages.model__error_setting_base_dn, e );
}
}
--------------------------------------------------------------------------------------------------
> 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.
[jira] Resolved: (DIRSTUDIO-487) empty namingcontexts causes
javax.naming.InvalidNameException: Bad DN
Posted by "Stefan Seelmann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSTUDIO-487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Stefan Seelmann resolved DIRSTUDIO-487.
---------------------------------------
Resolution: Fixed
Fix Version/s: 1.5.0
Assignee: Stefan Seelmann
Fixed in trunk:
http://svn.apache.org/viewvc?rev=778898&view=rev
> 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
> Assignee: Stefan Seelmann
> Priority: Minor
> Fix For: 1.5.0
>
>
> 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.
[jira] Commented: (DIRSTUDIO-487) empty namingcontexts causes
javax.naming.InvalidNameException: Bad DN
Posted by "Stefan Seelmann (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSTUDIO-487?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12713219#action_12713219 ]
Stefan Seelmann commented on DIRSTUDIO-487:
-------------------------------------------
I also found some refernces, looks like this bug exists very long:
http://www.openldap.org/lists/openldap-software/200202/msg00541.html
http://www.web2ldap.de/compability.html
I think the simplest solution is to check if the namingcontexts string ends with an \NUL and if so just remove it.
> 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.
[jira] Updated: (DIRSTUDIO-487) empty namingcontexts causes
javax.naming.InvalidNameException: Bad DN
Posted by "Pierre-Arnaud Marcelot (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSTUDIO-487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pierre-Arnaud Marcelot updated DIRSTUDIO-487:
---------------------------------------------
Component/s: studio-ldapbrowser
> 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
> Components: studio-ldapbrowser
> Affects Versions: 1.4.0
> Environment: Domino 7, Exchange 5.5
> Reporter: James Brown
> Assignee: Stefan Seelmann
> Priority: Minor
> Fix For: 1.5.0
>
>
> 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.
[jira] Closed: (DIRSTUDIO-487) Empty namingcontexts causes
javax.naming.InvalidNameException: Bad DN
Posted by "Pierre-Arnaud Marcelot (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSTUDIO-487?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Pierre-Arnaud Marcelot closed DIRSTUDIO-487.
--------------------------------------------
Apache Directory Studio version 1.5.0 has been released.
> 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
> Components: studio-ldapbrowser
> Affects Versions: 1.4.0
> Environment: Domino 7, Exchange 5.5
> Reporter: James Brown
> Assignee: Stefan Seelmann
> Priority: Minor
> Fix For: 1.5.0
>
>
> 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.