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.
Bug 719409 - make ssl functions available in wsgi access scripts.
Summary: make ssl functions available in wsgi access scripts.
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: mod_wsgi
Version: 6.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: 6.2
Assignee: Joe Orton
QA Contact: BaseOS QE Security Team
URL:
Whiteboard:
Depends On:
Blocks: 719411 741889
TreeView+ depends on / blocked
 
Reported: 2011-07-06 18:10 UTC by James Slagle
Modified: 2012-10-11 09:12 UTC (History)
2 users (show)

Fixed In Version: mod_wsgi-3.2-3.el6
Doc Type: Bug Fix
Doc Text:
Clone Of:
: 719411 (view as bug list)
Environment:
Last Closed: 2012-10-11 09:12:55 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
mod_wsgi patch (6.09 KB, application/octet-stream)
2011-07-06 18:10 UTC, James Slagle 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2012:1358 0 normal SHIPPED_LIVE mod_wsgi bug fix and enhancement update 2012-10-11 13:11:33 UTC

Description James Slagle 2011-07-06 18:10:23 UTC 
For the Pulp project (https://fedorahosted.org/pulp/), we need to be able to
access the http client's ssl certificate from within mod_wsgi.  We use the
client certificate to verify access to the various yum repos hosted by Pulp.

We've been using mod_python with a custom authentication handler that we set
with the PythonAuthenHandler apache config.  However, we want to move fully to
mod_wsgi since mod_python and mod_wsgi don't play nice together.

We can run an authentication script using the WSGIAuthUserScript configuration
for mod_wsgi.  However we need an additional patch from mod_wsgi upstream that
provides access to the client certificate in the implementing script that you
set with WSGIAuthUserScript.

The patch is changeset  1095:e1c09b0c8a2a in the mod_wsgi hg repository.  It's
only been applied for mod_wsgi 4.0, which hasn't been released yet.  I've
tested it, and the patch applies cleanly against version 3.2.  I've also attached the patch to this bugzilla.

More info about the patch on the mod_wsgi mailing list is here:
http://groups.google.com/group/modwsgi/browse_thread/thread/60314471e9d9e907
Comment 1 James Slagle 2011-07-06 18:10:50 UTC 
Created attachment 511548 [details]
mod_wsgi patch
Comment 3 RHEL Program Management 2011-07-06 18:57:24 UTC 
This request was evaluated by Red Hat Product Management for
inclusion in the current release of Red Hat Enterprise Linux.
Because the affected component is not scheduled to be updated
in the current release, Red Hat is unfortunately unable to
address this request at this time. Red Hat invites you to
ask your support representative to propose this request, if
appropriate and relevant, in the next release of Red Hat
Enterprise Linux. If you would like it considered as an
exception in the current release, please ask your support
representative.
Comment 6 Suzanne Logcher 2012-01-31 21:14:15 UTC 
This request was evaluated by Red Hat Product Management for inclusion in the
current release of Red Hat Enterprise Linux. Because the affected component is
not scheduled to be updated in the current release, Red Hat is unfortunately
unable to address this request at this time.  It has been proposed for the next
release. If you would like it considered as an exception in the current
release, please ask your support representative.
Comment 7 RHEL Program Management 2012-07-10 08:31:47 UTC 
This request was not resolved in time for the current release.
Red Hat invites you to ask your support representative to
propose this request, if still desired, for consideration in
the next release of Red Hat Enterprise Linux.
Comment 8 RHEL Program Management 2012-07-11 00:01:35 UTC 
This request was erroneously removed from consideration in Red Hat Enterprise Linux 6.4, which is currently under development.  This request will be evaluated for inclusion in Red Hat Enterprise Linux 6.4.
Comment 21 errata-xmlrpc 2012-10-11 09:12:55 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.

http://rhn.redhat.com/errata/RHBA-2012-1358.html
Note You need to log in before you can comment on or make changes to this bug.