Red Hat Bugzilla – Bug 1513583
[downstream clone - 4.2.0] [RFE] Add a link to CA certificate on the main landing page
Last modified: 2018-05-15 13:47:49 EDT
+++ This bug is an upstream to downstream clone. The original bug is: +++ +++ bug 1433676 +++ ====================================================================== Description of problem: I'm quite sure we used to have a link to the Engine's CA certificate in the landing page. Can't see it now. Version-Release number of selected component (if applicable): [root@lago-basic-suite-master-engine ~]# rpm -qa |grep webadmin ovirt-engine-webadmin-portal-4.2.0-0.0.master.20170317143110.git21edba0.el7.centos.noarch ovirt-engine-webadmin-portal-debuginfo-4.2.0-0.0.master.20170317143110.git21edba0.el7.centos.noarch (Originally by Yaniv Kaul)
I don't recall it, and I don't see anything in the history of packaging/branding/ovirt.brand/welcome_page.template @Alexander, do you recall this? (Originally by Greg Sheremeta)
I don't think we had such a link. We do have a URL providing that, but I don't recall having any link there. (Originally by Oved Ourfali)
We never had one on the welcome page, there is one on the client resources page though. (Originally by Alexander Wels)
"For using web-browser-based console clients, the certificate authority must be imported in your browser since the communication is secured. You can download the certificate authority by navigating 'https:///ovirt-engine/services/pki-resource?resource=ca-certificate&format=X509-PEM-CA'." http://www.ovirt.org/documentation/admin-guide/virt/console-client-resources/ Thanks Alexander. @Yaniv, ok to close? (Originally by Greg Sheremeta)
Converting it to a RFE. (Originally by Yaniv Kaul)
*** Bug 1467817 has been marked as a duplicate of this bug. *** (Originally by Greg Sheremeta)
Verified in RHVM version 4.2.0-0.6.el7.
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://access.redhat.com/errata/RHEA-2018:1488