Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

cn=config delete with a value to remove causes add. #2523

Open
389-ds-bot opened this issue Sep 13, 2020 · 2 comments
Open

cn=config delete with a value to remove causes add. #2523

389-ds-bot opened this issue Sep 13, 2020 · 2 comments
Milestone

Comments

@389-ds-bot
Copy link

Cloned from Pagure issue: https://pagure.io/389-ds-base/issue/49464


Issue Description

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.

@389-ds-bot
Copy link
Author

Comment from firstyear (@Firstyear) at 2018-01-30 00:15:06

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

@389-ds-bot 389-ds-bot added this to the FUTURE milestone Sep 13, 2020
@389-ds-bot
Copy link
Author

Comment from lkrispen (@elkris) at 2020-05-06 16:24:16

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 ?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant