Description of problem: On enterprise website, after having added an alias to an app, add an SSL certificate file with invalid content to the alias, click "save" button, it doesn't show any information about whether it's successful or invalid. Version-Release number of selected component (if applicable): ose2.1.z/2014-09-19.2 How reproducible: always Steps to Reproduce: 1.Login to enterprise website.Create an app, add an alias to the app, click "save". 2.Under SSL Certificate item, enter the path of file with invalid content(such as f1 with "abcd"), click "save". 3.Add SSL Certificate file in command line. 3.1 $rhc alias update-cert srb19 rb.test.com --certificate f1 --private-key f2 3.2 $ rhc alias update-cert srb19 rb.test.com --certificate ~/server.crt --private-key f.txt Actual results: 1.Save successfully. 2.Show nothing. 3.Have error info displayed: 3.1 $rhc alias update-cert srb19 rb.test.com --certificate f1 --private-key f2 Invalid certificate: not enough data 3.2 $ rhc alias update-cert srb19 rb.test.com --certificate /home/yanping/server.crt --private-key f1.txt Invalid private key or pass phrase: Could not parse PKey: no start line Expected results: 2.Should show info as the command line do : "Invalid certificate: not enough data" or "Invalid private key or pass phrase" under the related form. Additional info: If add the alias and invalid SSL Certificate file at the same time on the website, it will show erro info.
http://etherpad.corp.redhat.com/puddle-2-2-2014-10-07
Verified with puddle-2-2-2014-10-07. Steps to verify: 1.Login to enterprise website.Create an app, add an alias to the app, click "save". 2.Under SSL Certificate item, enter the path of .crt file with invalid content(such as f1.crt with "abcd"), click "save". 3.Under SSL Certificate item, enter the path of .key file with invalid content(such as f1.key with "test"), click "save" Actual results: 2.Have error info prompted: Invalid certificate: not enough data. 3.Have error info prompted: Invalid private key or pass phrase: Could not parse PKey: no start line.
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/RHSA-2014-1796.html