OID: 1.2.840.113556.1.4.1413
"Allows an LDAP modify to work under less restrictive conditions. Without it, a delete will fail if an attribute does not exist, and an add will fail if an attribute already exists. "
Metadata Update from @mreynolds: - Custom field origin adjusted to None - Custom field reviewstatus adjusted to None - Issue set to the milestone: 1.4.2
Might need aci's in cn=config so not everyone can use control?
I don't see why we need an aci for this - this is changing modify from an imperative flow to a stateful one - but at the end of the day the both achieve the same thing. Modifying the attributes of an entry.
Is there some concern you have that would necessitate an aci here?
I don't see why we need an aci for this - this is changing modify from an imperative flow to a stateful one - but at the end of the day the both achieve the same thing. Modifying the attributes of an entry. Is there some concern you have that would necessitate an aci here?
@lkrispen brought up that we protect other controls from being used in cn=config via aci's, and that perhaps we should do it here. So I added a comment to consider it.
Metadata Update from @mreynolds: - Issue priority set to: minor - Issue set to the milestone: 1.4 backlog (was: 1.4.2)
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/3700
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.