Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
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.
Apache HTTP Server now supports UPN
Names stored in the `subject alternative name` portion of SSL/TLS client certificates, such as the Microsoft User Principle Name, can now be used from the SSLUserName directive and are now available in *mod_ssl* environment variables. Users can now authenticate with their Common Access Card (CAC) or certificate with a UPN in it, and have their UPN used as authenticated user information, consumed by both the access control in Apache and using the `REMOTE_USER` environment variable or a similar mechanism in applications. As a result, users can now set `SSLUserName SSL_CLIENT_SAN_OTHER_msUPN_0` for authentication using UPN.
DescriptionJan Pazdziora (Red Hat)
2015-07-13 12:55:20 UTC
Description of problem:
Apache HTTP Server will get support for retrieving Microsoft User Principal Name in mod_ssl codebase, per http://mail-archives.apache.org/mod_mbox/httpd-dev/201507.mbox/browser. That makes it possible for the user to authenticate with their CAC or certificate which UPN in it, and have their UPN used as authenticated user information, and consumed by both the access control in Apache, and via REMOTE_USER or similar mechanism in applications.
It'd be good to have at least the part that allows
SSLUserName SSL_CLIENT_SAN_OTHER_msUPN_0
backported to Apache in RHEL 7.
Version-Release number of selected component (if applicable):
mod_ssl-2.4.6-31.el7.x86_64
How reproducible:
Deterministic.
Steps to Reproduce:
1. Have client certificate with UPN attribute set to user.
2. Configure authentication via client SSL certificate and set
SSLVerifyClient require
SSLUserName SSL_CLIENT_SAN_OTHER_msUPN_0
3. Restart httpd, authenticate with that certificate.
4. Check the request in ssl_access_log.
Actual results:
10.11.12.13 - - [13/Jul/2015 ...
and ssl_error_log complaining
Failed to set r->user to 'SSL_CLIENT_SAN_OTHER_msUPN_0'
Expected results:
10.11.12.13 - user [13/Jul/2015 ...
Additional info:
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/RHBA-2015-2194.html