Bug 1287844

Summary:	mod_authz_dbd: group query fails if the user is in multiple group (httpd bug 46421)
Product:	Red Hat Enterprise Linux 7	Reporter:	jouvin
Component:	httpd	Assignee:	Luboš Uhliarik <luhliari>
Status:	CLOSED ERRATA	QA Contact:	Martin Frodl <mfrodl>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	7.1	CC:	bnater, isenfeld, jkaluza, jorton, mfrodl
Target Milestone:	rc
Target Release:	---
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:	httpd-2.4.6-41.el7	Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-11-04 08:09:49 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description jouvin 2015-12-02 19:45:27 UTC

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:

Comment 1 Joe Orton 2015-12-18 11:41:55 UTC

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.

Comment 2 jouvin 2015-12-18 13:07:10 UTC

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

Comment 5 jouvin 2016-03-18 10:56:57 UTC

Thanks!

Michel

Comment 9 errata-xmlrpc 2016-11-04 08:09:49 UTC

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