[Date Prev][Date Next]
(ITS#4195) matchedDN issues with back-meta
Full_Name: Pierangelo Masarati
Submission from: (NULL) (220.127.116.11)
Submitted by: ando
There's yet another minimal issue with back-meta, which returns a spurious
matchedDN when configured with (at least) a target that spans the entire naming
context, and another target that spans a subordinate of the naming context:
and a search is performed for that subordinate only,
"ou=Subordinate,dc=example,dc=com". The first target is (correctly) returning
noSuchObject with a matchedDN of "dc=example,dc=com", and back-meta correctly
ignores the error code and returns the entire subtree of the second target.
However, a "dangling" (logically; memory is handled correctly ;) matchedDN
remains around and is returned with the searchResult response.
A fix to HEAD is about to come.