Fine backport details:
$ git log -1
Author: Martin Povolny <email@example.com>
Date: Sun Apr 9 20:12:01 2017 +0200
Merge pull request #972 from cben/get_hostname_from_routes-sslerror
Catch SSLError too when adding a provider
(cherry picked from commit bc446e54ba10dc0ca0a940abcd73f7e33d70c699)
New commit detected on ManageIQ/manageiq-ui-classic/fine:
Author: Martin Hradil <firstname.lastname@example.org>
AuthorDate: Mon Apr 24 14:25:55 2017 +0000
Commit: Satoe Imaishi <email@example.com>
CommitDate: Mon Apr 24 13:31:56 2017 -0400
Merge pull request #1126 from yaacov/fix-false-validation-error
Fix wrong validation error
(cherry picked from commit d63ee8fe6eb6907fbf57202029248bfba64704f5)
app/controllers/mixins/ems_common_angular.rb | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
Still able to add a provider with incorrect Custom Certificate.
Tested on v188.8.131.52-rc1
Please talk to me for more details
(In reply to Pavel Zagalsky from comment #4)
> Still able to add a provider with incorrect Custom Certificate.
> Tested on v184.108.40.206-rc1
> Please talk to me for more details
Beni please check what's going on here. Thanks.
Pavel can it be what you still see is bug 1444033?
- Entering the provider this BZ was originally seen with (whose cert doesn't cover it's hostname), I correctly see error flash:
»Credential validation was not successful: hostname "ep-ose32-master.scl.lab.tlv.redhat.com" does not match the server certificate«
- Entering same provider with Hostname = 10.35.160.9 (which the cert does cover), »Credential validation was successful«, which is correct.
- If you're referring to editing the custom CA cert and it still passing, that's bug 1444033.
Moving back to on QA per comment 7
Working fine, confused with other issue https://bugzilla.redhat.com/show_bug.cgi?id=1444033
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.