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

Unable to search RootDSE Operational attributes

Watch issueLinkCloneUpdate Comment AuthorReplace String in CommentUpdate Comment VisibilityDelete Comments
    XMLWordPrintableJSON

Details

    • Bug
    • Status: Closed
    • Major
    • Resolution: Fixed
    • 1.5.4
    • 1.5.2
    • ldap
    • None

    Description

      Using "bigbang" I've found that ApacheDS does not respond properly to
      Root DSE searches for both "+" (all operational) and "*" (all
      non-operational) attributes". I believe that the following change
      fixes the problem:

      $ svn diff DefaultPartitionNexus.java
      Index: DefaultPartitionNexus.java
      ===================================================================
      — DefaultPartitionNexus.java (revision 634445)
      +++ DefaultPartitionNexus.java (working copy)
      @@ -1002,7 +1002,7 @@

      { serverEntry.put( attribute ); }
      - else if ( containsPlus && ( type.getUsage() ==
      UsageEnum.USER_APPLICATIONS ) )
      + else if ( containsPlus && ( type.getUsage() !=
      UsageEnum.USER_APPLICATIONS ) )
      { serverEntry.put( attribute ); }

      Without this fix, ApacheDS treats the following ldap searches return
      identical responses (neither will return operational attributes):

      $ ldapsearch -x -h localhost -p10389 -s base -b "" '+'
      $ ldapsearch -x -h localhost -p10389 -s base -b "" '*'

      With the fix, ApacheDS responds correctly – or as least as correct
      with respect to the attribute usage assigned to the rootDSE
      attributes.

      Attachments

        Activity

          This comment will be Viewable by All Users Viewable by All Users
          Cancel

          People

            akarasulu Alex Karasulu
            ickydude Icky Dude
            Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved:

              Slack

                Issue deployment