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.
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.
Hold off on doing anything. It appears to be fixed in our next ER2 release (Based on my building locally and testing).
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.
I'm not sure if this is an installer issue or not based on the above.
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.
Will need to create a BZ in the dashboard builder (BAM) to see if they can fix the issue.
This has been logged with BAM, see the attached BZ (1133714).
This issue is dependent on the BAM being fixed and its not a high priority at this time.
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.