Hide Forgot
securitylevel_name: Public This will likely be configuration to persist to a database or file store.
For now we can use the in memory settings checked into the drools-repository module.
Hi Van, 1. We need to have a 'modeshape-jcr' policy in the login-config.xml. Maybe at a later time we can use the already exisiting 'modeshape' policy (BRMS-415). Or maybe the other projects can simply use the 'modeshape-jcr' policy since they are identical. 2. The policy should point to a *-users.properties and *-roles.properties file. Right now the ones for jmx-console are used. Van I think you where going to sort out what to use (on soa, the soa-users.properties) is used. 3. The *-users.properties should contain 2 users: admin and mailman, both with pw set to 'password' (they are hardcoded right now BRMS-416) 4. The *-roles.properties needs to give the admin role to the admin and the readwrite role to the mailman user. I will attach the files like they currently are in my setup. -Kurt
example files which work for me.
Attachment: Added: jmx-console-roles.properties Attachment: Added: jmx-console-users.properties Attachment: Added: login-config.xml
Link: Added: This issue is related to BRMS-416
With the https://jira.jboss.org/browse/MODE-1009, the policy can remain 'modeshape'. We still need the extra users/roles for admin and mailman. From a guvnor perspective the password for these users can be set in the components.xml, which should match the setting in the users.properties file.