SSSD / sssd

#4178 Odd lastUpdate attribute if SSSD is started without sssd.conf
Closed: Fixed by pbrezina. Opened by sbose.

Closed: Fixed
Reopen Issue

If sssd.conf is missing at startup and SSSD is compiled to support the implicit files provider (--enable-files-domain configure option) the lastUpdate attribute of the cn=config object in /var/lib/sss/db/config.ldb has some odd binary value.

PR: https://github.com/SSSD/sssd/pull/1017

Metadata Update from @sbose:
- Issue assigned to sbose

Metadata Update from @sbose:
- Custom field patch adjusted to on

Commit dab522c0 fixes this issue
  • master
    • dab522c09887e50722b17afa1a700b08ca1b7732 - confdb: use proper timestamp if sssd.conf is missing

SSSD is moving from Pagure to Github. This means that new issues and pull requests
will be accepted only in SSSD's github repository.

This issue has been cloned to Github and is available here:
- https://github.com/SSSD/sssd/issues/5133

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
None
None
None
High
on
Static archive. pagure.io was sunset in 2026; this is a read-only snapshot.
Red Hat Logo

Fedora is sponsored by Red Hat. Learn more about the relationship between Red Hat and Fedora »

© Red Hat, Inc. and others.