You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I have tried to use user openbacchus@internal in ovirt-engine to login from openbacchus web console. But auth failed with error in ovirt engine log:
2018-08-15 10:06:39,681+03 ERROR [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-25) [] EVENT_ID: USER_VDC_LOGIN_FAILED(114), User openbacchus@internal connecting from '10.169.2.2' failed to log in : 'Unable to log in. Verify your login information or contact the system administrator.'.
2018-08-15 10:06:39,682+03 ERROR [org.ovirt.engine.core.sso.utils.SsoUtils] (default task-23) [] OAuthException access_denied: Cannot authenticate user 'openbacchus@internal': Unable to log in. Verify your login information or contact the system administrator.
But if use curl to examine ovirt API auth going with no problems:
2018-08-15 10:06:59,942+03 INFO [org.ovirt.engine.core.sso.utils.AuthenticationUtils] (default task-30) [] User openbacchus@internal successfully logged in with scopes: ovirt-app-api ovirt-ext=token-info:authz-search ovirt-ext=token-info:public-authz-search ovirt-ext=token-info:validate ovirt-ext=token:password-access
2018-08-15 10:06:59,975+03 INFO [org.ovirt.engine.core.dal.dbbroker.auditloghandling.AuditLogDirector] (default task-27) [16aa1567] EVENT_ID: USER_VDC_LOGIN(30), User openbacchus@internal-authz connecting from '10.169.2.2' using session 'zrnefmQfOaFXhv4PoHXmDOScUtPTr0ivr+/zxAXmKCEG/FLUGoxe1u1SCVWA2ZuVhUl6RMpq9drT/S+7op6DTA==' logged in.
The text was updated successfully, but these errors were encountered:
I have tried to use user openbacchus@internal in ovirt-engine to login from openbacchus web console. But auth failed with error in ovirt engine log:
But if use curl to examine ovirt API auth going with no problems:
curl -u openbacchus@internal:XXX https://ovirt.XXX/ovirt-engine/api --insecure
The text was updated successfully, but these errors were encountered: