Red Hat Bugzilla – Bug 1012019
OOTB - The BPEL console does not allow users to login until after a BPEL process is deployed
Last modified: 2014-02-06 10:28:42 EST
Description of problem:
Related to bugzilla: https://bugzilla.redhat.com/show_bug.cgi?id=1011665
After BPEL users are created, they cannot log into the BPEL console until after a BPEL process is deployed. Before a process is deployed, login attempts are blocked - the user is shown this error:
BPEL Engine is not started
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Create users as described in: https://bugzilla.redhat.com/show_bug.cgi?id=1011665
2. Attempt to log into the BPEL console
The user is blocked from logging into the console
Why can't the user login before a BPEL process is deployed?
See attached screenshot
Created attachment 802899 [details]
BPEL login screenshot
The reason for this is that the BPEL console (currently) needs the BPEL engine to be initialized. However the BPEL engine is only initialized after a BPEL process is deployed - to avoid unnecessary startup delay in switchyard if user is not using BPEL.
Had a look, and this error is displayed if the console gets a login failure that is not authentication related:
This won't be a quick fix, so suggest it should be post-beta.
We need to make sure it's documented for Beta so the user knows to deploy before attempting to log in to console. Agree it has to be fixed for GA.
Applied part of the fix - to enable the console server to cause the engine to be initialized even if no BPEL processes have been deployed. Remainder of solution should be provided when the login mechanism is changed in the console to use the Overlord SSO mechanism.
Gary Brown <firstname.lastname@example.org> updated the status of jira RIFTSAW-545 to Resolved
*** Bug 947313 has been marked as a duplicate of this bug. ***
Verified on ER7