The jbpm-console.war was deployed successfully in Weblogic with no errors. I was able to get to the jbpm-console login screen, but then the authentication fails even though all the data has been populated correctly.
The following was done to achieve the above:
i) In the Weblogic console, created a new provider for SQLReadOnly Authentication Provider using the default tables for Group, Users, GroupMembers etc. The idea was not to change the SQL, and created the corresponding tables in Oracle to which the datasource configured in weblogic (JbpmDS1). Had also tried with using the JBPM provide user, group, member tables with SQLReadOnly which did not work.
ii) Modified the following files from the jbpm-console which comes with jbpm 3.2.3 and repackaged it in the new war file.
a) hibernate.cfg.xml to point to the datasource in Oracle which weblogic uses.
b) Web.xml to specify the security realm configured in weblogic and the datasource for Oracle.
c) Added weblogic.xml to the war file to specify the datasource JNDI name and security role.
Any help to get weblogic working with the jbpm-console would be great as the first part of deploying the console app and bringing the login screen works successfuly.
The other option would be to bypass the security altogether, not sure if this can be done via descriptors alone or the jbpm-console code uses the security check in each JSF screen.
I think you might get more info when you turn on the debug level of authentication in WLS.... Often helped me in finding errors (But that was on WLS 8.1