[ http://issues.apache.org/jira/browse/DIREVE-276?page=all ]
Alex Karasulu updated DIREVE-276:
---------------------------------
Fix Version: 0.9.4
(was: 0.9.3)
> Search for super OC does not return subclasses if add op does not add
> complete objectClass lineage
> --------------------------------------------------------------------------------------------------
>
> Key: DIREVE-276
> URL: http://issues.apache.org/jira/browse/DIREVE-276
> Project: Directory Server
> Type: Bug
> Reporter: Alex Karasulu
> Assignee: Alex Karasulu
> Fix For: 0.9.4
>
> If I add an entry with objectClass inetOrgPerson to the directory but do not
> include in the objectClass attribute values for the super objectClasses like
> organizationalPerson and person then (objectClass=person) will not return the
> entry when it is in scope. To fix this is simple. Instead of adding tests
> for lineage on search operations which would be a nightmare we should pay the
> price on the add operation. Basically an interceptor can check that the
> lineage of objectClasses is present within the objectClass attribute. If not
> then it can be injected into the entry before the add operation takes place.
> I don't know if this is correct behavior but it cannot hurt.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
