If you issue ldap.modify_s([(ldap.MOD_DELETE, Key, NONE)]) this works.
If you issue ldap.modify_s([(ldap.MOD_DELETE, Key, Value)]), this acts as MOD_ADD, due to a bug in how we pass the value to libglobs.
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 - Issue set to the milestone: FUTURE
If the attribute is required we cannot just delete it, so we would have to reject the delete. But then there is no easy way to reset to the default value (if it is not known).
So what is the request: reject the delete ?
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/2523
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)
Log in to comment on this ticket.