Bug 1499239

Summary:	Propagate errors to welcome page
Product:	[oVirt] ovirt-engine	Reporter:	Ravi Nori <rnori>
Component:	AAA	Assignee:	Ravi Nori <rnori>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Lucie Leistnerova <lleistne>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	4.2.0	CC:	bugs, lleistne, mperina
Target Milestone:	ovirt-4.2.0	Flags:	rule-engine: ovirt-4.2+
Target Release:	4.2.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-12-20 11:08:29 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	Infra	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Ravi Nori 2017-10-06 12:33:59 UTC

Description of problem: The welcome page requires the error to be send as error_description and code should be sent as error.

How reproducible:

Steps to Reproduce:
1. From welcome page login as user with privileges to only UserPortal
2. Trying accessing Administration Portal

Actual results: The user stays on welcome page with no error message

Expected results: The error message should be displayed that the user cannot access admin portal.

Comment 1 Martin Perina 2017-10-07 06:25:35 UTC

Found out that issue was caused by OpenId Connect changes, so retargeting to 4.2

Comment 2 Lucie Leistnerova 2017-11-07 12:48:07 UTC

user returned back to welcome page and 'The user xxx is not authorized to perform login' is displayed (for both admin and vm portal)

verified in ovirt-engine-4.2.0-0.0.master.20171105155215.git59d3324.el7.centos.noarch
ovirt-engine-extension-aaa-jdbc-1.1.7-0.0.master.git1660a27.el7.centos.noarch

Comment 3 Sandro Bonazzola 2017-12-20 11:08:29 UTC

This bugzilla is included in oVirt 4.2.0 release, published on Dec 20th 2017.

Since the problem described in this bug report should be
resolved in oVirt 4.2.0 release, published on Dec 20th 2017, it has been closed with a resolution of CURRENT RELEASE.

If the solution does not work for you, please open a new bug report.