#3740 Utilizing domain_resolution_order in sssd.conf breaks SELinux user map
Closed: Fixed 5 years ago Opened 5 years ago by jhrozek.

Ticket was cloned from Red Hat Bugzilla (product Red Hat Enterprise Linux 7): Bug 1571466

Please note that this Bug is private and may not be accessible as it contains confidential Red Hat customer information.

This is a clone from a downstream bug so the details are not visible, but the tl;dr is that the combination of the domain resolution order and SELinux user mapping does not work well together.


Metadata Update from @jhrozek:
- Custom field rhbz adjusted to https://bugzilla.redhat.com/show_bug.cgi?id=1571466

5 years ago

Metadata Update from @fidencio:
- Issue assigned to fidencio

5 years ago

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

5 years ago

Metadata Update from @fidencio:
- Issue tagged with: PR

5 years ago

Metadata Update from @jhrozek:
- Issue set to the milestone: SSSD 1.16.2

5 years ago

Metadata Update from @fidencio:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

5 years ago

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

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.

Login to comment on this ticket.

Metadata