Uploaded image for project: 'OpenDJ'
  1. OpenDJ
  2. OPENDJ-46

Extensible filters which use dnAttributes are not processed correctly when there is an existing index for the named attribute

    Details

    • Type: Bug
    • Status: Done
    • Priority: Minor
    • Resolution: Fixed
    • Affects Version/s: 2.6.0, 2.4.0
    • Fix Version/s: 2.6.0
    • Component/s: backends
    • Labels:
      None

      Description

      A filter of the form (ou:dn:=people) should match the following entries:

      • any entry having an attribute "ou" whose value is "people"
      • any entry having a DN containing an AVA of the form "ou=people".

      Currently, the JE backend mishandles extensible filters of this form and will use attribute indexes if available. If there is no attribute index available then the candidate list defaults to allIDs, which is ok. If there is an attribute index available then it will use it and only find entries fulfilling the first category above.

      The only feasible way we have today of processing this type of filter is to always default to allIDs.

      The fix is pretty straightforward.

        Attachments

          Activity

            People

            • Assignee:
              matthew Matthew Swift
              Reporter:
              matthew Matthew Swift
              Dev Assignee:
              Matthew Swift
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: