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.

Description of problem:

SELinux prevents httpd from connecting to localhost port 389.

Version-Release number of selected component (if applicable):


How reproducible:

Always

Steps to Reproduce:
1. Configure mod_authnz_ldap to connect to a running LDAP server on localhost port 389.
2.
3.

Actual results:

type=AVC msg=audit(1603323574.899:1916): avc:  denied  { name_connect } for  pid=3540 comm="httpd" dest=389 scontext=system_u:system_r:httpd_t:s0 t
context=system_u:object_r:ldap_port_t:s0 tclass=tcp_socket permissive=0

Expected results:

Connects properly.

Additional info:

This should be controlled by the httpd_can_connect_ldap SELinux boolean, have you tried 

# semanage boolean -m --on httpd_can_connect_ldap

?

Let me know if you still have problems but I'm going to assume works when configured in SELinux.

The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days