Bug 1132703

Summary:	Teiid Dashboard DV ER1 redirection issue
Product:	[JBoss] JBoss Data Virtualization 6	Reporter:	Thomas Hauser <thauser>
Component:	Dashboard Builder	Assignee:	Van Halbert <vhalbert>
Status:	CLOSED WONTFIX	QA Contact:
Severity:	unspecified	Docs Contact:
Priority:	unspecified
Version:	6.1.0	CC:	atangrin, jstastny, nshendye, vhalbert
Target Milestone:	---	Keywords:	Documentation
Target Release:	6.1.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Known Issue
Doc Text:	JBoss Data Virtualization Dashboard fails to redirect if user enters correct login credentials, but doesn't have the correct role to access the dashboard. The browser redirects to a blank page. This only occurs when the user passes the authentication but is not authorized to use the application.	Story Points:	---
Clone Of:
Clones:	1133714 (view as bug list)		Environment:
Last Closed:	2015-01-20 14:01:49 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:
Bug Depends On:	1133714
Bug Blocks:

Description Thomas Hauser 2014-08-21 20:39:39 UTC

Description of problem:
The user enters a state where Firefox states: the server is redirecting the request for this address in a way that will never complete.

if one uses the incorrect login credentials on the teiid-dashboard.


Version-Release number of selected component (if applicable):
DV 6.1.0 ER1

How reproducible:
Always

Steps to Reproduce:
1. Install / start the server through standalone.sh
2. Navigate to localhost:8080/dashboard
3. Attempt to login using incorrect credentials.

Actual results:
The browser reports "the server is redirecting the request for this address in a way that will never complete."

Expected results:
Some kind of "login failed" message is displayed instead.

Comment 2 Thomas Hauser 2014-08-21 20:42:04 UTC

After more testing, this only occurs on a user meeting the following criteria:

a) They exist within application-users.properties / -roles.properties
b) They lack the required roles to login to dashboard builder. 

For other users, such as gibberish / non-existent users, login is not allowed and the server does not enter the "the server is redirecting the request for this address in a way that will never complete." state.

Comment 3 Van Halbert 2014-08-25 23:57:58 UTC

Hold off on doing anything.  It appears to be fixed in our next ER2 release (Based on my building locally and testing).

Comment 4 Jan Stastny 2014-12-04 07:12:29 UTC

In ER4 the error present again. When I log in to dashboard with a user without user or admin role, than the message "Firefox has detected that the server is redirecting the request for this address in a way that will never complete." appears. 

Again it is the user which passes the authentication, but is not authorized to use the application.

Comment 5 Thomas Hauser 2014-12-04 15:02:29 UTC

I'm not sure if this is an installer issue or not based on the above.

Comment 6 Van Halbert 2014-12-04 15:32:16 UTC

I don't think its an installer issue.   It handles correctly if the user doesn't exist, but doesn't like it if the user exist, but doesn't have the correct roles.

Comment 7 Van Halbert 2014-12-04 15:45:55 UTC

Will need to create a BZ in the dashboard builder (BAM) to see if they can fix the issue.

Comment 8 Van Halbert 2014-12-04 15:51:40 UTC

This has been logged with BAM, see the attached BZ (1133714).

Comment 9 Van Halbert 2014-12-05 20:26:43 UTC

This issue is dependent on the BAM being fixed and its not a high priority at this time.

Comment 10 Van Halbert 2015-01-20 14:01:49 UTC

Per the BAM (Dashboard builder project):

There is nothing we can do for getting rid of the blank page. When a user without any of the webapp roles tries to login, EAP responds that way. The auth request is not even handed over to the webapp in such case.

This is an IT issue. If users are created properly, with the right roles, they will never see a blank screen, as it does not make sense to register a user not having a valid role.