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.
DescriptionStephen Gallagher
2011-12-20 13:29:21 UTC
This is not an issue with the currently-released SSSD packages in RHEL 6.2. It is pre-emptively opened for a new requirement that we will have in RHEL 6.3.
+++ This bug was initially created as a clone of Bug #769175 +++
Description of problem:
Version-Release number of selected component (if applicable):
sssd-1.7.0-0.20111219T1638Zgitbdd2050.fc15.x86_64
How reproducible:
Always
Steps to Reproduce:
1. Update Fedora 15 with the latest SSSD bits from http://jdennis.fedorapeople.org/ipa-devel/fedora/$releasever/$basearch/os/
2. ipa-client-install
3. Observe /var/log/messages
Actual results:
Dec 20 20:13:50 dhcp201-106 setroubleshoot: SELinux is preventing /usr/sbin/sssd from using the sys_admin capability. For complete SELinux messages. run sealert -l 650ca357-5e3a-455b-b028-4d0afaa8e5d0
Expected results:
No SELinux denials and SSSD should be started successfully.
Additional info:
SELinux is preventing /usr/sbin/sssd from using the sys_admin capability.
***** Plugin catchall (100. confidence) suggests ***************************
If you believe that sssd should have the sys_admin capability by default.
Then you should report this as a bug.
You can generate a local policy module to allow this access.
Do
allow this access for now by executing:
# grep sssd /var/log/audit/audit.log | audit2allow -M mypol
# semodule -i mypol.pp
--- Additional comment from sgallagh on 2011-12-20 08:27:31 EST ---
SSSD grew a dependency on the sys_admin capability because it is now using keyctl_join_session_keyring() and keyctl_setperm() to connect to the kernel keyring and store passwords securely while the SSSD is running (such as for deferred kinit operation).
We need this new requirement added to SSSD in the selinux policy.
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-2012-0780.html