Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 0.8.1
    • Fix Version/s: 1.1.0
    • Component/s: studio-ldapbrowser
    • Labels:
      None
    • Environment:
      LDAP Studio 0.8.1 on Windows XP MCE 2005

      Description

      I'm trying to establish a Connection to an iPlanet LDAP server. The Base DN for this server is of the form 'dc=smtp,dc=company,dc=com,dc=' - note the trailing 'dc='. This Base DN is valid and mandatory - access to this server won't work without it.
      If I attempt the 'Fetch Base DNs' function, I get a java.lang.NullPointerException error while fetching the Base DN.
      If I leave 'Get base DNs from Root DSE' set, the Connection fails to open with an error of "Empty Value is not allowed! Can't set Base DN entry'.
      If I attempt to type in the actual Base DN, I get a popup that states 'Please enter a valid Base DN'.
      If I attempt any other value for Base DN, the connection fails with a LDAP error 32 - No Such Object.

      I am able to browse the server with the Novell ldapsearch and the LDAP Browser/Editor v2.8.2, but not with an OpenLDAP ldapsearch 2.3.30, if that helps anything.

      I don't know if relaxing the Base DN validation rule on the Connection form is enough to fix my issue as I see no way to test that scenario. Hand-editing the connections.xml (putting in a fake final dc=blah and then deleting the blah value from the file) does not seem to have done the trick.

        Activity

        Hide
        Emmanuel Lecharny added a comment -

        Hi,

        what if you use dc=smtp,dc=company,dc=com,dc="" instead of the DN you are using ? (note the "" at the end) ?

        Show
        Emmanuel Lecharny added a comment - Hi, what if you use dc=smtp,dc=company,dc=com,dc="" instead of the DN you are using ? (note the "" at the end) ?
        Hide
        Andy Deckowitz added a comment -

        The (dc="") format permits me to fill out the Connection form, but the Open Connection attempt still fails with an error of "String index out of range: -1".

        Show
        Andy Deckowitz added a comment - The (dc="") format permits me to fill out the Connection form, but the Open Connection attempt still fails with an error of "String index out of range: -1".
        Hide
        Stefan Seelmann added a comment -

        We are now using the shared-ldap DN parser.

        The version we are currently use (shared-ldap-0.9.8-SNAPSHOT) throws an AIOOBE when creating an Rdn instance with an empty RDN value.

        Also the current trunk version throws an AIOOBE.

        But in the bigbang branch this problem is fixed.

        Show
        Stefan Seelmann added a comment - We are now using the shared-ldap DN parser. The version we are currently use (shared-ldap-0.9.8-SNAPSHOT) throws an AIOOBE when creating an Rdn instance with an empty RDN value. Also the current trunk version throws an AIOOBE. But in the bigbang branch this problem is fixed.
        Hide
        Stefan Seelmann added a comment -

        @Emmanuel:
        I just wanted to ask you, if an RDN with an empty value is valid, e.g. "cn="? I already prepared a patch that fixed the RdnParser in trunk and bigbang.

        Show
        Stefan Seelmann added a comment - @Emmanuel: I just wanted to ask you, if an RDN with an empty value is valid, e.g. "cn="? I already prepared a patch that fixed the RdnParser in trunk and bigbang.
        Hide
        Emmanuel Lecharny added a comment -

        RFC 4514 states :

        relativeDistinguishedName = attributeTypeAndValue *( PLUS attributeTypeAndValue )
        attributeTypeAndValue = attributeType EQUALS attributeValue
        attributeValue = string / hexstring
        string = [ ( leadchar / pair ) [ *( stringchar / pair ) ( trailchar / pair ) ] ]

        (note the [ ] for string).

        'cn=' is valid wrt RFC 4514

        Show
        Emmanuel Lecharny added a comment - RFC 4514 states : relativeDistinguishedName = attributeTypeAndValue *( PLUS attributeTypeAndValue ) attributeTypeAndValue = attributeType EQUALS attributeValue attributeValue = string / hexstring string = [ ( leadchar / pair ) [ *( stringchar / pair ) ( trailchar / pair ) ] ] (note the [ ] for string). 'cn=' is valid wrt RFC 4514
        Hide
        Stefan Seelmann added a comment -

        Thanks Emmanuel

        Show
        Stefan Seelmann added a comment - Thanks Emmanuel
        Show
        Stefan Seelmann added a comment - Fixed with commits http://svn.apache.org/viewcvs?view=rev&rev=620282 http://svn.apache.org/viewcvs?view=rev&rev=620281 http://svn.apache.org/viewcvs?view=rev&rev=620280 http://svn.apache.org/viewcvs?view=rev&rev=620036 http://svn.apache.org/viewcvs?view=rev&rev=620035
        Hide
        Pierre-Arnaud Marcelot added a comment -

        Version 1.1.0 has been released.
        Closing this issue.

        Show
        Pierre-Arnaud Marcelot added a comment - Version 1.1.0 has been released. Closing this issue.

          People

          • Assignee:
            Stefan Seelmann
            Reporter:
            Andy Deckowitz
          • Votes:
            0 Vote for this issue
            Watchers:
            1 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development