Uploaded image for project: 'Directory ApacheDS'
  1. Directory ApacheDS
  2. DIRSERVER-632

If one tries to connect with an illegal LDAP protocol version, no error occurs

    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Minor
    • Resolution: Fixed
    • 1.0-RC3
    • 1.0-RC4, 1.5.0
    • None
    • None
    • Sun ONE Directory SDK for Java 4.1
      ApacheDS 1.0 RC 3
      Java(TM) 2 Runtime Environment, Standard Edition (build 1.5.0_04-b05)
      Microsoft Windows XP version 5.1 Service Pack 1

    Description

      If one tries to connect to an LDAP server with a wrong version number (e.g. 4 instead of 2 or 3), it is expected that a protocol error occurs. See RFC 2251, 4.2.3, "Bind Response" for details.

      This is not the case with ApacheDS, the client seems to hang instead, if you use version=4.
      Unfortunately, I was not able to create this situation with JNDI, because its LDAP Provider does not allow this operation. You can specify the version via environment (key "java.naming.ldap.version", but for an illegal value it throws an exception on the client side and does not seem to call the server at all.

      Therefore I have created a JUnit test case with Sun ONE Directory SDK for Java. Netscape SDK (now Mozilla SDK, http://www.mozilla.org/directory/), will probably do as well. Please let me know, if you have any problem to reproduce the problem.

      Attachments

        1. IllegalLDAPVersionBindTest.java
          1 kB
          Stefan Zoerner
        2. DIRSERVER-632.log
          6 kB
          Stefan Zoerner

        Activity

          People

            akarasulu Alex Karasulu
            szoerner Stefan Zoerner
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: