+++ This bug is a downstream clone. The original bug is: +++ +++ bug 1825907 +++ ====================================================================== Description of problem: An error is returned when trying to retrieve the OpenID userinfo Version-Release number of selected component (if applicable): 4.3.9.4 How reproducible: Always Steps to Reproduce: 1. Get an access token from the API ~~~ token=$(curl -s -k -H 'Accept: application/json' "https://${engine}/ovirt-engine/sso/oauth/token?grant_type=password&scope=ovirt-app-api&username=admin@internal&password=redhat" | jq -r '.access_token') ~~~ 2. Try to retrieve the OpenID userinfo: ~~~ curl -s -k -H "Accept: application/json" -H "Authorization: Bearer ${token}" "https://${engine}/ovirt-engine/sso/openid/userinfo?access_token=${token}" ~~~ Actual results: {"error_description":"WELD-001437: Bean type class org.ovirt.engine.core.sso.utils.openid.OpenIdService is not proxyable because it is final - <unknown javax.enterprise.inject.spi.Bean instance>.","error":"server_error"} Expected results: Obtain the actual user information Additional information: The same request works in previous versions. (Originally by Miguel Martin Villamuelas)
This is a clone candidate and ultimately a 4.4 bug entry. Do not add ZStream kw nor ack 4.3.z flag prior to cloning. No data loss - decreasing severity (Originally by michal.skrivanek)
Moving back to MODIFIED, not included in latest 4.3.10 build
Apparently still not included in the latest build. Using ovirt-engine-4.3.10-0.2.el7.noarch this still fails with: {"error_description":"WELD-001437: Bean type class org.ovirt.engine.core.sso.utils.openid.OpenIdService is not proxyable because it is final - <unknown javax.enterprise.inject.spi.Bean instance>.","error":"server_error"}
Verified on ovirt-engine-4.1.11.2-0.1.el7.noarch Now the request returns JSON Web Token and no errors.
Wrong machine...ovirt-engine-4.3.10.1-0.1.master.el7.noarch
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/RHBA-2020:2396