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
Unable to set nsslapd-db-locks: Object class violation #4341
Comments
Please try with
|
It's not set in |
does not persist the value. The setting gets lost every time DS is restarted. |
mh, it's not getting persistent in
|
This is a bug in FreeIPA, see https://pagure.io/freeipa/issue/8515 Thanks for your assistance, @vashirov |
I have opened freeipa/freeipa#5145 to address the FreeIPA bug. There is nothing to do for 389-DS. |
Issue Description
I'm unable to configure
nsslapd-db-locks
with ldapmodify. The attribute is not set by default and adding the attribute tocn=config,cn=ldbm database,cn=plugins,cn=config
fails with an object class violation. I'm getting the same error with Apache Directory Studio, too.Also see #1965
Package Version and Platform:
Steps to Reproduce
Run ldapmodify as DM with LDIF:
Expected results
no error
Additional context
cn=config,cn=ldbm database,cn=plugins,cn=config
has classextensibleObject
but no schema provides the attributensslapd-db-locks
. I think this triggers the violation.The text was updated successfully, but these errors were encountered: