Drools-guvnor manage access – part 1

Externalize business or technical rules is very important for scalable applications but the BRMS service access should be managed. guvnor provides control UI access and operations using role based authorizations.

There are several permissions types as listed in drools-guvnor reference manual.
Admin with all permissions.
Analyst or Analyst read-only: analyst permissions for a specific category.
Package admin, Package developer or Package read-only: package permissions for a specific package.

– Allow user authentication control by updating the file compenent.xml located into the server deployed folder

<component name="org.jboss.seam.security.roleBasedPermissionResolver>
      <property name="enableRoleBasedAuthorization">false</property>
// change false to true

Embedded Guvnor in Jboss server control access configuration:

Stop guvnor server if started in user guest mode and enable role based authorization.

Add drools-guvnor access policy in the file login-config.xml located in server/default/conf

<application-policy name="drools-guvnor">
<login-module code="org.jboss.security.auth.spi.UsersRolesLoginModule" 
<module-option name="usersProperties">
<module-option name="rolesProperties">

Create properties files for users and roles with respective contents:

# A roles.properties file for UsersRolesLoginModule (drools-guvnor-roles.properties)

# A users.properties file for UsersRolesLoginModule (drools-guvnor-users.properties)

Restart the Jboss guvnor server and log into web interface using created accounts.


Leave a Reply

Fill in your details below or click an icon to log in:

WordPress.com Logo

You are commenting using your WordPress.com account. Log Out /  Change )

Google+ photo

You are commenting using your Google+ account. Log Out /  Change )

Twitter picture

You are commenting using your Twitter account. Log Out /  Change )

Facebook photo

You are commenting using your Facebook account. Log Out /  Change )


Connecting to %s