Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite 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 "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. 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 "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-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.
DescriptionMichael J. Ayers
2014-10-23 14:28:32 UTC
Document URL: https://access.redhat.com/documentation/en-US/Red_Hat_Satellite/6.0/html/Installation_Guide/index.html
Section Number and Name: 3.3. Configuring LDAP Authentication for Red Hat Satellite
Describe the issue: SELinux can prevent outgoing connections in RHEL 7 of certain types. With out the proper SEBool setting LDAP authentication will never work and debugging it is difficult due to the nature of the failure in Foreman. This can happen by default if you do a minimal RHEL install and then expand it later to support running Satellite.
Suggestions for improvement: Add a note to section 3.3 that informs the reader that setting the SELinux SEBool will allow outgoing LDAP requests.
Additional information: The denials in the /var/log/audit/audit.log look like this:
type=AVC msg=audit(1414013923.072:498): avc: denied { name_connect } for pid=3341 comm="ruby" dest=389 scontext=system_u:system_r:passenger_t:s0 tcontext=system_u:object_r:ldap_port_t:s0 tclass=tcp_socket
Dumping those through and audit2allow -m gives the following:
[root@satellite ~]# grep denied /var/log/audit/audit.log | grep ruby | audit2allow -m selinux-foreman-ldap
module selinux-foreman-ldap 1.0;
require {
type ldap_port_t;
type passenger_t;
class tcp_socket name_connect;
}
#============= passenger_t ==============
#!!!! This avc can be allowed using one of the these booleans:
# nis_enabled, authlogin_nsswitch_use_ldap, passenger_can_connect_all
allow passenger_t ldap_port_t:tcp_socket name_connect;
My suggestion would be to set authlogin_nsswitch_use_ldap = 1 by executing the following:
[root@satellite ~]# setsebool authlogin_nsswitch_use_ldap=1
Comment 1RHEL Program Management
2014-10-23 14:43:01 UTC
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.
Comment 4RHEL Program Management
2015-04-21 16:09:36 UTC
Since this issue was entered in Red Hat Bugzilla, the release flag has been
set to ? to ensure that it is properly evaluated for this release.