AD provides flexibility, to AD client, to use shortcuts values in filter components. For example objectCategory [1] or objectSID [2] allows shortcuts. The transformation of the filter components assertion can be done with a plugin using slapi_compute_add_search_rewriter.
The RFE is to create a "generic" plugin that registers rewriter callback, plugin/callbacks being referenced in the config. So a third party rewriter plugin/callback could easy be integrated with 389-ds.
[1] https://social.technet.microsoft.com/wiki/contents/articles/5392.active-directory-ldap-syntax-filters.aspx#Filter_on_objectCategory_and_objectClass [2] https://docs.microsoft.com/en-us/openspecs/windows_protocols/ms-adts/5d58c90d-3cc5-444f-aabd-cff5f99d70f7
N/A
Currently rewriter need a new plugin (init/start/stop/config/rewriters callbacks)
rewriter should be a shared library only containing the rewriter callbacks
An alternate approach could be to have something like memberof but when an objectClass contains one of the matching oc types, we extract and generate a corresponding objectCategory on the object - then we can just use it as a true attribute rather than as something that is a filter rewrite?
Metadata Update from @firstyear: - Custom field origin adjusted to None - Custom field reviewstatus adjusted to None
Metadata Update from @mreynolds: - Issue priority set to: major - Issue set to the milestone: 1.4.3
PR https://pagure.io/389-ds-base/pull-request/50939
New PR dedicated to filter rewriter for objectCategory https://pagure.io/389-ds-base/pull-request/50988
46fb7ce..12c6814 master
Metadata Update from @tbordaz: - Issue assigned to tbordaz
Metadata Update from @tbordaz: - Issue close_status updated to: fixed - Issue status updated to: Closed (was: Open)
Commit cec0506 relates to this ticket
f910aa5..dc8e260 389-ds-base-1.4.3 -> 389-ds-base-1.4.3
Metadata Update from @mreynolds: - Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1843159
Issue linked to Bugzilla: Bug 1843159
389-ds-base is moving from Pagure to Github. This means that new issues and pull requests will be accepted only in 389-ds-base's github repository.
This issue has been cloned to Github and is available here: - https://github.com/389ds/389-ds-base/issues/3984
If you want to receive further updates on the issue, please navigate to the github issue and click on subscribe button.
subscribe
Thank you for understanding. We apologize for all inconvenience.
Metadata Update from @spichugi: - Issue close_status updated to: wontfix (was: fixed)
Login to comment on this ticket.