Currently attribute uniqueness can be configured to scope/exclude specific subtrees. An other option (exclusive to the previous one) specify a given objectclass value to select ONE subtree and objectclass value to check only given type of entries.
For example, it is possible to configure:
uniqueness-attribute-name: mail uniqueness-top-entry-oc: nscontainer uniqueness-subtree-entries-oc: inetOrgPerson
It will check mail uniqueness the first 'nsContainer' subtree (from the updated entry back to the top) mail values of all inetOrgPerson entries.
It works, it looks nice but I wonder if it is not addressing an old corner case, now looking more like a hack.
This ticket is to evaluate if this option should be deprecated.
All
I have no issue deprecating this, it seems really edge-casey. You either want the uniqueness "everywhere" or "not at all" I think ...
Metadata Update from @firstyear: - Custom field component adjusted to None - Custom field origin adjusted to None - Custom field reviewstatus adjusted to None - Custom field type adjusted to None - Custom field version adjusted to None
Metadata Update from @mreynolds: - Issue set to the milestone: 1.4 backlog
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/2398
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 - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.