Users expect the browser to propose to cache credentials, however, this functionality does not work when logging into the RHEV User Portal.
1. This is actually a security issue - but I assume if customers do not want this, they can turn off it on the browser side - so I assume we do not need on our side the ability to turn on or off this. 2. It seems to be working (on 4.0) already for the admin portal - so is it just fixing the user portal?
(In reply to Yaniv Kaul from comment #5) > 1. This is actually a security issue - but I assume if customers do not want > this, they can turn off it on the browser side - so I assume we do not need > on our side the ability to turn on or off this. I agree, but during SSO refactoring we changed login screen, so it conforms to current practise. So browser will ask a user to store the password or even fill-in stored password depending on user's browser configuration. > 2. It seems to be working (on 4.0) already for the admin portal - so is it > just fixing the user portal? It was not possible to store password for both in 3.x, but in 4.0 storing password is available for both.
This is fixed as part of SSO work in 4.0, the browser setting for saving user name and password will be used for the login screen.
Merged long time ago and definitely part of 4.0.0.4 build
Verified in rhevm-4.0.2-0.2.rc1.el7ev.noarch. Browsers now offer the user to save credentials for the SSO login page. For details see bug 1164302 comment 9.
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/RHEA-2016-1743.html