[Date Prev][Date Next] [Chronological] [Thread] [Top]

Re: (ITS#4224) Incorrect return code from dyngroup/dynlist when checking membership of a non-existing DN?

ando@sys-net.it wrote:
> Full_Name: Pierangelo Masarati
> Version: HEAD,re23
> OS: irrelevant
> URL: ftp://ftp.openldap.org/incoming/
> Submission from: (NULL) (
> Submitted by: ando
> I've found out that if I run a compare for "member:cn=Non-Existing" with either
> dyngroup or dynlist, I get noSuchObject (32) instead of FALSE.  The dynamic
> object correctly expands "memberURL" attributes into lists of "member"
> attributes, so the "member" attribute virtually exists, but the value doesn't,
> so backend_group() return noSuchObject, and this error is echoed in the result. 
> I think this is incorrect, because since "member" virtually exists, while  the
> asserted value is absent, the correct return code should be compareFalse.
> I'd fix the code this way in the overlays unless there are objections.

Makes sense.

  -- Howard Chu
  Chief Architect, Symas Corp.  http://www.symas.com
  Director, Highland Sun        http://highlandsun.com/hyc
  OpenLDAP Core Team            http://www.openldap.org/project/