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.
This bug is created as a clone of upstream ticket:
https://fedorahosted.org/gss-proxy/ticket/101
When attempting to enable GSS-Proxy & [wiki:Apache], I find that the '''!KrbLocalUserMapping''' configuration option does not work. This is an imporant part of the configuration options, as not all web applications properly support '''!username''' style usernames, so I need to be able to say '''Require user username''' instead of '''Require user !username''' in some cases. I'm using gssproxy-0.2.3-6.fc19.1.x86_64, httpd-2.4.6-2.fc19.x86_64 and mod_auth_kerb-5.4-24.fc19.x86_64.
{{{
<Location /redacted>
SSLRequireSSL
AuthType Kerberos
AuthName "Login"
KrbAuthoritative On
KrbLocalUserMapping On
KrbServiceName HTTP/example.com
Require user username
</Location>
}}}
{{{
AH01631: user username\x02s: authorization failure for /redacted
AH01663: access to /redacted failed, reason: user 'username\x02' does not meet 'require'ments for user to be allowed access
AH01631: user username\x02: authorization failure for "/redacted":
AH01663: access to /redacted failed, reason: user 'username\x02IN1' does not meet 'require'ments for user to be allowed access
AH01631: user username\x02IN1: authorization failure for "/redacted":
AH01663: access to /redacted failed, reason: user 'username\x7f' does not meet 'require'ments for user to be allowed access
AH01631: user username\x7f: authorization failure for "/redacted":
AH01663: access to /redacted failed, reason: user 'username\x02' does not meet 'require'ments for user to be allowed access
}}}
I suggest we do SanityOnly testing on this one for RHEL 7.0. It will be tested indirectly by the solutions on top of RHEL7. The problem is that we can't even create these solutions since it is not working and preventing us to create repeatable setups and guidelines for the layered products to follow.
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-2298.html