#47355 dse.ldif doesn't replicate update to nsslapd-sasl-mapping-fallback
Closed: wontfix None Opened 8 years ago by rcritten.

For IPA ticket https://fedorahosted.org/freeipa/ticket/3330 we are going to configure SASL LDAP mapping fallback.

The value is updated in LDAP but not in dse.ldif.

# service dirsrv@GREYOAK-COM stop
Redirecting to /bin/systemctl stop  dirsrv@GREYOAK-COM.service
# grep nsslapd-sasl-mapping-fallback /etc/dirsrv/slapd-GREYOAK-COM/dse.ldif
nsslapd-sasl-mapping-fallback: off
# service dirsrv@GREYOAK-COM start
Redirecting to /bin/systemctl start  dirsrv@GREYOAK-COM.service
# ldapsearch -LLL -x -s base -D 'cn=directory manager' -W -b cn=config nsslapd-sasl-mapping-fallback
Enter LDAP Password:
dn: cn=config
nsslapd-sasl-mapping-fallback: on

what version of 389? I was not able to reproduce this behavior. Using ldapmodify correctly updates the dse.ldif and the cn=config entry. I can restart the server, and everything is still correctly set.


I can reproduce some strange behavior with the current version.

git merge ticket47355
Updating 2473fcb..ba0d579
ldap/servers/slapd/libglobs.c | 17 +++++++++--------
ldap/servers/slapd/slap.h | 2 +-
2 files changed, 10 insertions(+), 9 deletions(-)

git push origin master
Counting objects: 13, done.
Delta compression using up to 4 threads.
Compressing objects: 100% (7/7), done.
Writing objects: 100% (7/7), 958 bytes, done.
Total 7 (delta 5), reused 0 (delta 0)
To ssh://git.fedorahosted.org/git/389/ds.git
2473fcb..ba0d579 master -> master

commit ba0d579

Metadata Update from @rcritten:
- Issue assigned to mreynolds
- Issue set to the milestone:

4 years ago

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/692

If you want to receive further updates on the issue, please navigate to the github issue
and click on subscribe button.

Thank you for understanding. We apologize for all inconvenience.

Metadata Update from @spichugi:
- Issue close_status updated to: wontfix (was: Fixed)

a year ago

Login to comment on this ticket.