SSSD / sssd

#1743 selinux: move all logic to responder, provider should only update db
Closed: Fixed Opened by jhrozek.

Closed: Fixed
Reopen Issue

The logic of the SELinux processing is split between the provider and the responder. This has caused headaches especially with getting offline processing right.

The provider also writes a "score" into the database and the responder acts upon the score. That's not correct architecture-wise, the provider should be just providing data, not providing much processing logic.

We should move the processing logic to the responder and only update the database in the provider.

Internal change only. No RHEL clone.

rhbz: => 0

Fields changed

milestone: NEEDS_TRIAGE => SSSD 1.10 beta

Fields changed

owner: somebody => mzidek

Fields changed

patch: 0 => 1
  • master: b42bb7d9dbf9a4c44a03e7bf1bab471a8a85e858

review: => 0

Fields changed

resolution: => fixed
status: new => closed

Metadata Update from @jhrozek:
- Issue assigned to mzidek
- Issue set to the milestone: SSSD 1.10 beta

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

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
Normal
defect
SSSD
1.9.3
None
0
1
0
0
0
None
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.