Bug 1499239 - Propagate errors to welcome page
Summary: Propagate errors to welcome page
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: ovirt-engine
Classification: oVirt
Component: AAA
Version: 4.2.0
Hardware: Unspecified
OS: Unspecified
unspecified
medium
Target Milestone: ovirt-4.2.0
: 4.2.0
Assignee: Ravi Nori
QA Contact: Lucie Leistnerova
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-10-06 12:33 UTC by Ravi Nori
Modified: 2017-12-20 11:08 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2017-12-20 11:08:29 UTC
oVirt Team: Infra
Embargoed:
rule-engine: ovirt-4.2+


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
oVirt gerrit 82587 0 master MERGED aaa: Propagate errors to welcome page 2017-10-06 15:26:28 UTC

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.


Note You need to log in before you can comment on or make changes to this bug.