Hide Forgot
Affects Testing: Blocks Testing securitylevel_name: Public After successful installation of Modeshape into BRMS 5.2.0.DEV1 (+ EAP 5.1), I run into the following exception on server startup: org.jboss.seam.InstantiationException: Could not instantiate Seam component: repositoryConfiguration .... Caused by: org.drools.repository.RulesRepositoryException: UserName: [ logInAdmin] Unable to login to JCR backend. .... Caused by: javax.jcr.LoginException: The JAAS policy named 'modeshape' (nor the policy named 'other') could not be found; check the value of the 'JAAS_LOGIN_CONFIG_NAME' repository option in the configuration for the 'brms' repository at org.modeshape.jcr.JcrRepository.login(JcrRepository.java:1344) at org.modeshape.jcr.JcrRepository.login(JcrRepository.java:1289) at org.drools.repository.JCRRepositoryConfigurator.login(JCRRepositoryConfigurator.java:95) at org.drools.repository.RulesRepositoryConfigurator.login(RulesRepositoryConfigurator.java:85) at org.drools.guvnor.server.repository.RepositoryStartupService.newSession(RepositoryStartupService.java:213) ... 99 more Caused by: javax.security.auth.login.FailedLoginException: Password Incorrect/Password Required at org.jboss.security.auth.spi.UsernamePasswordLoginModule.login(UsernamePasswordLoginModule.java:252) at org.jboss.security.auth.spi.UsersRolesLoginModule.login(UsersRolesLoginModule.java:152) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at javax.security.auth.login.LoginContext.invoke(LoginContext.java:769) at javax.security.auth.login.LoginContext.access$000(LoginContext.java:186) at javax.security.auth.login.LoginContext$4.run(LoginContext.java:683) at java.security.AccessController.doPrivileged(Native Method) at javax.security.auth.login.LoginContext.invokePriv(LoginContext.java:680) at javax.security.auth.login.LoginContext.login(LoginContext.java:579) at org.modeshape.graph.JaasSecurityContext.<init>(JaasSecurityContext.java:115) at org.modeshape.graph.JaasSecurityContext.<init>(JaasSecurityContext.java:82) at org.modeshape.jcr.JcrRepository.login(JcrRepository.java:1341) ... 103 more As you can see from the attached server logs, Modeshape configuration and, importantly, the login-config.xml, the "modeshape" policy is there. In fact, the exact same process has been used to set up BRMS 5.2+Modeshape as was always being used to set up BRMS 5.1+Modeshape.
Attachment: Added: login-config.xml Attachment: Added: modeshape-config.xml Attachment: Added: server.log
Affects Testing: Added: [Blocks Testing]
Tested with the latest code updates to ModeShape and to the build scripts, and didn't see this issue. Suggest retesting with latest.
Still happening with BRMS 5.2.0-dev3.
Link: Added: This issue is duplicated by BRMS-615
It appears the logInAdmin password was defined incorrectly in the components.xml file. Use this: <key>org.drools.repository.logInAdmin.password</key> <value>logInAdmin</value>
Yes, this is probably just a configuration issue. If the 'logInAdmin' user is added to brms-users.properties and the line you mentioned to components.xml, deploying is done without errors and Guvnor can be used with ModeShape.
This issue is configuration issue to how components.xml and users are defined.
Agreed. However user 'logInAdmin' is not listed in brms-users.properties (and brms-roles.properties) and also not in compoments.xml by default. User has to be added manually. I think that it should be there by default.
Would it make sense to use 'admin' as the default connect account for modeshape instead of logInAdmin as it was in BRMS 5.1.0? Plus the 'admin' is still the default account for BRMS web interface login in.
Not sure where the logInAdmin came from, its not from modeshape.
So, it seems that the user name was added/changed in Guvnor 5.2. Not sure what is the reason for that, but I'll try to find out.
From e-mail communication come out, that Toni Rikkola changed the name by mistake and he will revert this change in brms 5.2 branch, so this should be probably fixed in new build.
Changing to a BRMS person, cause this is a BRMS configuration/kitting issue, that is not controlled by ModeShape.
Verified fixed in 5.2.0 ER2. Closing this issue.