Description of problem: It would be nice to have a shortcut option on welcome page of ovirt-engine just like for Administration portal or VM portal in the section Portals. Regarding bug 2021497, keycloak is installed by default and it's not visible on the first sight how to get to the administration console of the keycloak. Version-Release number of selected component (if applicable): ovirt-engine-4.5.1.2-1.el8.noarch
This is relatively quick and easy to implement. We only need to only display it when keycloak is enabled. There is already an example for Grafana/Monitoring portal [1]. The open question is where this link should be added. Would it be under 'Portals' ? [1] https://github.com/oVirt/ovirt-engine/commit/60f473bf7be4b00bbd20de9345419af79151c6c4
One more thought after discussing with Radek. Perhaps we want to have a keycloak admin console link even for keyloak being configured manually. That means when Keycloak/RH SSO is not bundled. That will extend the scope.
I have made some changes in the setup code. Please ack if that is something that will be good enough to solve this issue: --== SUMMARY ==-- [ INFO ] Starting dwh service [ INFO ] Starting Grafana service [ INFO ] Restarting ovirt-vmconsole proxy service (..) ===== updated text start =====vvvvv==== To login to oVirt using Keycloak SSO, enter username 'admin@ovirt' and the password provided during the setup. To login to Keycloak Administration Console enter username 'admin'with the password provided during the setup Keycloak Administration Console is enabled at: https://dev2.dom/ovirt-engine-auth/admin ===== updated text end =====^^^^^^==== (..) Web access is enabled at: http://dev2.dom:80/ovirt-engine https://dev2.dom:443/ovirt-engine Internal CA fingerprint: SHA256: 36:4E:B6:48:0A:12:9B:FC:3D:72:3D:B3:58:F7:C3:63:A7:C5:8C:43:C5:59:E4:81:38:1C:67:47:BD:56:7C:69
It is good enough and it works. Verified in ovirt-engine-keycloak-15.0.2-4.el8.noarch > I have made some changes in the setup code. Please ack if that is something > that will be good enough to solve this issue: > > --== SUMMARY ==-- > > [ INFO ] Starting dwh service > [ INFO ] Starting Grafana service > [ INFO ] Restarting ovirt-vmconsole proxy service > (..) > ===== updated text start =====vvvvv==== > To login to oVirt using Keycloak SSO, enter username 'admin@ovirt' > and the password provided during the setup. > To login to Keycloak Administration Console enter username > 'admin'with the password provided during the setup > Keycloak Administration Console is enabled at: > https://dev2.dom/ovirt-engine-auth/admin > ===== updated text end =====^^^^^^==== > (..) > Web access is enabled at: > http://dev2.dom:80/ovirt-engine > https://dev2.dom:443/ovirt-engine > Internal CA fingerprint: SHA256: > 36:4E:B6:48:0A:12:9B:FC:3D:72:3D:B3:58:F7:C3:63:A7:C5:8C:43:C5:59:E4:81:38: > 1C:67:47:BD:56:7C:69 (In reply to Artur Socha from comment #3) > I have made some changes in the setup code. Please ack if that is something > that will be good enough to solve this issue: > > --== SUMMARY ==-- > > [ INFO ] Starting dwh service > [ INFO ] Starting Grafana service > [ INFO ] Restarting ovirt-vmconsole proxy service > (..) > ===== updated text start =====vvvvv==== > To login to oVirt using Keycloak SSO, enter username 'admin@ovirt' > and the password provided during the setup. > To login to Keycloak Administration Console enter username > 'admin'with the password provided during the setup > Keycloak Administration Console is enabled at: > https://dev2.dom/ovirt-engine-auth/admin > ===== updated text end =====^^^^^^==== > (..) > Web access is enabled at: > http://dev2.dom:80/ovirt-engine > https://dev2.dom:443/ovirt-engine > Internal CA fingerprint: SHA256: > 36:4E:B6:48:0A:12:9B:FC:3D:72:3D:B3:58:F7:C3:63:A7:C5:8C:43:C5:59:E4:81:38: > 1C:67:47:BD:56:7C:69
This bugzilla is included in oVirt 4.5.2 release, published on August 10th 2022. Since the problem described in this bug report should be resolved in oVirt 4.5.2 release, it has been closed with a resolution of CURRENT RELEASE. If the solution does not work for you, please open a new bug report.