Details
-
Bug
-
Status: Resolved
-
Major
-
Resolution: Fixed
-
1.2.5
-
None
Description
During ambari-server setup-https process, a wrong password produces the same result as correct password, the importing and saving config process are correct.
In the Browser side, when click on the https locker, the certification details have changed to the new cert (but the password was wrong), which should not happen.
Every running of "ambari-server setup-https" command overwrites current "https.keystore.p12" and "https.pass.txt" files despite the correct password was provided or not.