Hide Forgot
When Kerberos single sign on fails, IPA should fall back to a landing page with a username + password login form that also has directions on it to install the single sign on plugin if the platform supports it This would enable better cross-browser compatibility and access from workstations where the kereberos browser plug-in cannot be installed.
Upstream ticket: https://fedorahosted.org/freeipa/ticket/2109
Ticket 2109 was closed as duplicate. The BZ is now linked to the following upstream ticket: https://fedorahosted.org/freeipa/ticket/2095
Fixed upstream: master: ee780df13c99a5465cd6df965772260c297a5eb2 ipa-2-2: 135e208a665a6f9b7cbba32371b35f8ea705c9cb Be more forgiving about content-type format: master: 610420bd2ab976ea9e35e6d010e3f1c9f572c646 ipa-2-2: d5fbb878eee78eeccae0baca12f38a29ed07085d
Technical note added. If any revisions are required, please edit the "Technical Notes" field accordingly. All revisions will be proofread by the Engineering Content Services team. New Contents: Cause: When Kerberos single sign on to IPA Web UI fails, IPA Web UI does not have means to fall back to login+password authentication. Consequence: Workstations outside of IPA Kerberos realm or with in-compatible browsers cannot access the IPA Web UI unless a fallback from Kerberos authentication to login+password authentication is configured on the IPA web server. Change: IPA Web UI is now able to fall back to form based authentication when Kerberos authentication cannot be used. Result: Users outside of IPA Kerberos realm or with in-compatible browsers can now login with their login and passwords.
verified using ipa-server-2.2.0-12.el6.x86_64 On a windows machine, used IE to access a ipa server. was able to login using form based auth, browsed through UI. Also logged in as a non-admin user (whose password doesn't need to be reset) and got to page with user details.
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-0819.html