Red Hat Bugzilla – Bug 1441192
Add the name of URL parameter which will be check for username during cert login
Last modified: 2017-08-01 05:48:56 EDT
Cloned from upstream: https://pagure.io/freeipa/issue/6860 mod_lookup_identity checks one URL parameter during login using certificate and tries to get the user name provided during login from this parameter. Name of the URL parameter has to be configured in apache. Without configuration mod_lookup_identity does not check the URL and therefore login using certificates does not work correctly when one certificate is mapped to more users. Proposed changes: IPA webui adds 'username' as URL parameter. This parameter name should be set in IPA httpd conf by default.
Upstream ticket: https://pagure.io/freeipa/issue/6860
Fixed upstream ipa-4-5: https://pagure.io/freeipa/c/a9721e529e7a02eeb40d29cb7820e69cd86d9337 master: https://pagure.io/freeipa/c/157831a287c64106eed4da4ace5228d7e369ae2f
Fixed upstream master: https://pagure.io/freeipa/c/9d32e61ba548e7e940f165c0ec8df0b4bfd210bd ipa-4-5: https://pagure.io/freeipa/c/76e5ac59579f36f28bb247bf3173e95e57ee4af4
Is this related to the issue we saw when I was originally trying to verify bug #1430675?
Verified. Version :: ipa-server-4.5.0-13.el7.x86_64 Results :: Functionality provided by this already covered here: https://bugzilla.redhat.com/show_bug.cgi?id=1403194#c4 To confirm upgrade works, I upgraded from 4.5.0-5. [root@rhel7-4 ~]# grep Lookup /etc/httpd/conf.d/ipa.conf LookupUserByCertificate On [root@rhel7-4 ~]# yum update ipa-server ... Updated: ipa-server.x86_64 0:4.5.0-13.el7 Dependency Updated: ipa-client.x86_64 0:4.5.0-13.el7 ipa-client-common.noarch 0:4.5.0-13.el7 ipa-common.noarch 0:4.5.0-13.el7 ipa-server-common.noarch 0:4.5.0-13.el7 python2-ipaclient.noarch 0:4.5.0-13.el7 python2-ipalib.noarch 0:4.5.0-13.el7 python2-ipaserver.noarch 0:4.5.0-13.el7 Complete! [root@rhel7-4 ~]# grep Lookup /etc/httpd/conf.d/ipa.conf LookupUserByCertificate On LookupUserByCertificateParamName "username"
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://access.redhat.com/errata/RHBA-2017:2304