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:

We are suffering httpd bug 46421 (https://bz.apache.org/bugzilla/show_bug.cgi?id=46421) with MySQL backend for authz. We assessed that the last version of mod_authz_dbd (rebuilt from sources, fixed in httpd 2.4.13) works. Any chance to have this patch backported to RHEL7 httpd.


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

httpd 2.4.6-31

How reproducible:

Always

Steps to Reproduce:
1. Create 2 groups (e.g. group1 and group2) into the httpd authz MySQL backend and add the same user in both groups
2. Add a 'require dbd-group group1' (or group2) for one <Directory> or <Location>
3. In a browser, try to access the URL: you'll get a 403 error (forbidden)

Actual results:

403 error

Expected results:

Successful access to the url

Additional info:

Thanks for the report.  If this issue is critical or in any way time sensitive,
please raise a ticket through your regular Red Hat support channels to make
certain it receives the proper attention and prioritization to assure a timely
resolution.

Hi Joe,

Thanks for the answer. In fact I'm a CentOS user so I don't think I can report it through the regular RH support channel. I hope it will be taken into account anyway...

Cheers,

Michel

Thanks!

Michel

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.

https://rhn.redhat.com/errata/RHEA-2016-2534.html