Bug 1454811 - [downstream clone - 4.1.5] No error pops when logging with a locked ovirt user account
Summary: [downstream clone - 4.1.5] No error pops when logging with a locked ovirt use...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine
Version: 4.0.0
Hardware: x86_64
OS: Unspecified
medium
medium
Target Milestone: ovirt-4.1.5
: ---
Assignee: Ravi Nori
QA Contact: Gonza
URL:
Whiteboard:
Depends On: 1445681
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-05-23 13:50 UTC by rhev-integ
Modified: 2019-04-28 13:38 UTC (History)
22 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1445681
Environment:
Last Closed: 2017-08-22 17:42:35 UTC
oVirt Team: Infra
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2017:2509 0 normal SHIPPED_LIVE Red Hat Virtualization Manager (ovirt-engine) 4.1.5 2017-08-22 21:38:47 UTC
oVirt gerrit 76668 0 master MERGED aaa: Return SSO authentication errors in response 2017-07-18 19:07:00 UTC
oVirt gerrit 79770 0 ovirt-engine-4.1 MERGED aaa: Return SSO authentication errors in response 2017-07-25 10:22:11 UTC

Comment 6 Gonza 2017-08-21 09:43:54 UTC 
Verified with:
ovirt-engine-4.1.5.3-0.0.master.20170815115046.git41c45b8.el7.centos.noarch

...
< HTTP/1.1 401 Unauthorized
< Date: Mon, 21 Aug 2017 09:17:23 GMT
< Server: Apache/2.4.6 (CentOS) OpenSSL/1.0.1e-fips
* Authentication problem. Ignoring this.
< WWW-Authenticate: Basic realm="RESTAPI"
< Content-Type: text/html;charset=UTF-8
< Content-Length: 216
< 
* Connection #0 to host 10-xxx.com left intact
<html><head><title>Error</title></head><body>access_denied: Cannot authenticate user 'admin@internal': Unable to log in because the user account is disabled or locked. Contact the system administrator..</body></html>%
Comment 8 errata-xmlrpc 2017-08-22 17:42:35 UTC 
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-2017:2509
Note You need to log in before you can comment on or make changes to this bug.