Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.

+++ This bug was initially created as a clone of Bug #843730 +++

In SSSD there is a new feature which writes SSSD config files into /etc/selinux/<policy>/logins/ for SELinux PAM module which then uses this information to set correct context for remote user logging in.

I'd like to ask for update of SELinux policy so SSSD can write into this directory. I've set permissive mode on my machine, tried to log in several times and these are the rules that audit2allow returned:

allow sssd_t selinux_config_t:dir { write remove_name add_name };
allow sssd_t selinux_config_t:file { write rename create unlink };

Please note that we don't write directly to final config files but we rather use mkstemp-style temporary files which are then renamed to the final name.

--- Additional comment from jzeleny on 2012-07-27 10:12:27 CEST ---

There is one mistake in my initial description. SSSD of course writes SELinux config files into /etc/selinux/<policy>/logins/, not SSSD config files.

We added fixes to Fedora. Let's wait to see if this works correctly.

*** Bug 848751 has been marked as a duplicate of this bug. ***

Backported to RHEL6.4.

# matchpathcon /etc/selinux/targeted/logins//etc/selinux/targeted/logins	system_u:object_r:selinux_login_config_t:s0
# sesearch -s sssd_t -t selinux_login_config_t -c file --allow
Found 1 semantic av rules:
   allow sssd_t selinux_login_config_t : file { ioctl read write create getattr setattr lock append unlink link rename open } ; 

# sesearch -s sssd_t -t selinux_login_config_t -c dir --allow
Found 1 semantic av rules:
   allow sssd_t selinux_login_config_t : dir { ioctl read write getattr lock add_name remove_name search open } ; 

#

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

http://rhn.redhat.com/errata/RHBA-2013-0314.html