jBPM 4.2 GWT Console Login

[c.kloy]

Hello,

I have installed jBPM 4.2 on a JBoss 5.1. The database is setup correctly and I insert the users from the file example.identites.sql.
But when I try to login into the jbpm-console I get the message "Authentication failed". Is there something I have to configure?
The log dont show any exceptions (loglevel = all).

Best Regards
Christian

[sebastian.s]

Have you set up the demo setup coming with jBPM or have you installed jBPM into an existing Tomcat installation?

"Authentication failed" is not only shown when you've supplied the wrong credentials but also when Tomcat could not access the database with the users' credentials or when there was a problem with the class for authentication configurated in the realm.

[c.kloy]

I have installed jBPM in an fresh JBoss 5.1 on a DB2 9.5. JBPM starts without any errors and can connect to the database.
Now I get the following messages in the Log, when I try to login with correct credentials:

11:06:32,666 DEBUG [CoyoteAdapter] Requested cookie session id is BFA55D72FE5E895472BEB915A1E4CB76
11:06:32,666 DEBUG [AuthenticatorBase] Security checking request GET /gwt-console-server/rs/identity/secure/sid
11:06:32,666 DEBUG [RealmBase] Checking constraint 'SecurityConstraint[Resteasy]' against GET /rs/identity/secure/sid --> true
11:06:32,666 DEBUG [RealmBase] Checking constraint 'SecurityConstraint[Resteasy]' against GET /rs/identity/secure/sid --> true
11:06:32,666 DEBUG [AuthenticatorBase] Calling hasUserDataPermission()
11:06:32,666 DEBUG [RealmBase] User data constraint has no restrictions
11:06:32,666 DEBUG [AuthenticatorBase] Calling authenticate()
11:06:32,666 DEBUG [FormAuthenticator] Save request in session 'BFA55D72FE5E895472BEB915A1E4CB76'
11:06:32,666 TRACE [StandardWrapper] Returning non-STM instance
11:06:32,666 DEBUG [[default]] Disabling the response for futher output
11:06:32,666 DEBUG [AuthenticatorBase] Failed authenticate() test
11:06:32,666 DEBUG [CoyoteAdapter] Requested cookie session id is BFA55D72FE5E895472BEB915A1E4CB76
11:06:32,666 DEBUG [AuthenticatorBase] Security checking request POST /gwt-console-server/rs/identity/secure/j_security_check
11:06:32,666 DEBUG [FormAuthenticator] Authenticating username 'mike'
11:06:32,713 TRACE [StandardWrapper] Returning non-STM instance
11:06:32,713 DEBUG [[default]] Disabling the response for futher output
11:06:32,713 DEBUG [AuthenticatorBase] Failed authenticate() test ??/gwt-console-server/rs/identity/secure/j_security_check

[sebastian.s]

And the security realm was configured to use the JbpmDatabase to authenticate users?

P.S.: Sorry for asking for Tomcat. You've written in your first post that you're using JBossAS. It was just me thinking about a problem I had with Tomcat.

[c.kloy]

I configured the realm in the login-config.xml if the jboss instance.

 <application-policy name="jbpm-console">
 <authentication>
 <login-module code="org.jboss.security.auth.spi.DatabaseServerLoginModule" flag="required">
 <module-option name="dsJndiName">java:/JbpmDS</module-option>
 <module-option name="principalsQuery"> SELECT PASSWORD_ FROM JBPM4_ID_USER WHERE ID_=? </module-option>
 <module-option name="rolesQuery">
 SELECT g.NAME_ ,'Roles' FROM JBPM4_ID_USER u, JBPM4_ID_MEMBERSHIP m, JBPM4_ID_GROUP g
 WHERE g.TYPE_='security-role' AND m.GROUP_ = g.DBID_ AND m.USER_ = u.DBID_ AND u.ID_=? </module-option>
 </login-module>
 </authentication>
 </application-policy>

I also tried the names "jbpm" or "other". The results in the logs are the same.

[c.kloy]

I solved the problem. It was a DB2 issue. The SQL-statement needs the name of the schema bevor the tablename.

Thanks for the help.

[kukeltje]

and you thanks for reporting back. That way topics are really useful to others