How can I add users that can log in to the KIE Workbench?

[ingmarhaasdijk]

Hello JBoss Community,

How can I add users that can log in to the KIE Workbench en perform Tasks?

Now I'm using the standard john, mary and krisv, but I would like my own names.

Kind regards,

Ingmar Haasdijk

[salaboy21]

Hi, if you are deploying the KIE-Workbench/jBPM Console NG in jboss you need to add a new JBoss user following this docs: http://docs.jboss.org/jbpm/v6.0/userguide/wb.Workbench.html#wb.UserManagement

[ingmarhaasdijk]

Hi Mauricio, thanks for your quick response.

I tried this, but the system adds the new user, when I try to log in in the KIE Workbench it gives me an error: Login failed: Invalid UserName or Password.

What could be the problem?

[salaboy21]

That should work. But why secretaresse is admin? try with Role: user and make sure that you select Application User in the first option as mentioned in the docs. You can also share the content of the files: application-users.properties and application-roles.properties so we can take a look on them.

Cheers

[ingmarhaasdijk]

I tried adding a new user; testpersoon as a user. Still didn't work unfortunately! Below are the files you asked for.

application-roles.properties

#
# Properties declaration of users roles for the realm 'ApplicationRealm'.
#
# This includes the following protocols: remote ejb, remote jndi, web, remote jms
#
# Users can be added to this properties file at any time, updates after the server has started
# will be automatically detected.
#
# The format of this file is as follows: -
# username=role1,role2,role3
#
# A utility script is provided which can be executed from the bin folder to add the users: -
# - Linux
#  bin/add-user.sh
#
# - Windows
#  bin\add-user.bat
#
# The following illustrates how an admin user could be defined.
#
#admin=PowerUser,BillingAdmin,
#guest=guest
secretaresse=admin
testpersoon=user

application-users.properties

#
# Properties declaration of users for the realm 'ApplicationRealm' which is the default realm
# for application services on a new AS 7.1 installation.
#
# This includes the following protocols: remote ejb, remote jndi, web, remote jms
#
# Users can be added to this properties file at any time, updates after the server has started
# will be automatically detected.
#
# The format of this realm is as follows: -
# username=HEX( MD5( username ':' realm ':' password))
#
# A utility script is provided which can be executed from the bin folder to add the users: -
# - Linux
#  bin/add-user.sh
#
# - Windows
#  bin\add-user.bat
#
# The following illustrates how an admin user could be defined, this
# is for illustration only and does not correspond to a usable password.
#
#admin=2a0923285184943425d1f53ddd58ec7a
secretaresse=9923474a8e31707379f9948edc95c696
testpersoon=6f7b5a1176cdef5410c8ea5854602159

[bobalu]

Ingmar Haasdijk, have you manage to solve that problem? I have the same issue. Do everything in the same and correct way but can not login.

What I'm doing after that is to add one account as user. Try to login and receive Unauthorize error message. Then open application-roles.property and change the role from user to admin

bobalu=user to bobalu=admin

It works, but now I have another issue. There is nothing display after that, like in this picture:

I have tried chrome, firefox and internet explorer. It is the same. In chrome, I have a popup tell something like:

The page at localhost:8080 says:

ERROR: Possible problem with your *.gwt.xml module file.

The compile time user.agent value (gecko1_8) does not match the runtime user.agent value (safari). Expect more errors.

What could be the problem?

[ingmarhaasdijk]

No my problem has not been solved yet. I already submitted the model with the standard users to my teacher, but would still really love to know how to do it.

[maciej-starzyk]

Hi

Check your configuration xml (either standalone or standalone-full - depending what you are using) for domain security subsystem. You may find that the security-domain "other" has been modified to use not standard login-module. Replace it with standard login-module from base jboss installation, something like this:

<security-domain name="other" cache-type="default">
                    <authentication>
                        <login-module code="Remoting" flag="optional">
                            <module-option name="password-stacking" value="useFirstPass"/>
                        </login-module>
                        <login-module code="RealmUsersRoles" flag="required">
                            <module-option name="usersProperties" value="${jboss.server.config.dir}/application-users.properties"/>
                            <module-option name="rolesProperties" value="${jboss.server.config.dir}/application-roles.properties"/>
                            <module-option name="realm" value="ApplicationRealm"/>
                            <module-option name="password-stacking" value="useFirstPass"/>
                        </login-module>
                    </authentication>
</security-domain>

Of course after this all the previous logins will stop working so you have to recreate them (like krisv, etc)

Cheers

Maciej

[ingmarhaasdijk]

When I edit the file with your new code, my suite won't start up. In the Terminal it stays still after "start.jboss:".

[maciej-starzyk]

Hi

Strange. After when I edited security subsystem to look like this:

<subsystem xmlns="urn:jboss:domain:security:1.1">
            <security-domains>
                <security-domain name="other" cache-type="default">
                    <authentication>
                        <login-module code="Remoting" flag="optional">
                            <module-option name="password-stacking" value="useFirstPass"/>
                        </login-module>
                        <login-module code="RealmUsersRoles" flag="required">
                            <module-option name="usersProperties" value="${jboss.server.config.dir}/application-users.properties"/>
                            <module-option name="rolesProperties" value="${jboss.server.config.dir}/application-roles.properties"/>
                            <module-option name="realm" value="ApplicationRealm"/>
                            <module-option name="password-stacking" value="useFirstPass"/>
                        </login-module>
                    </authentication>
                </security-domain>
                <security-domain name="jboss-web-policy" cache-type="default">
                    <authorization>
                        <policy-module code="Delegating" flag="required"/>
                    </authorization>
                </security-domain>
                <security-domain name="jboss-ejb-policy" cache-type="default">
                    <authorization>
                        <policy-module code="Delegating" flag="required"/>
                    </authorization>
                </security-domain>
            </security-domains>
</subsystem>

I can log in using users created by add-user script.

Maybe there is something missing/wrong with your configuration file after editing?

BTW I changed configuration for two instances of my jbpm 6, one dev - Windows and one test - Linux and both are working fine.

Cheers

Maciej

[muktiprakashmisra]

I faced the same problem.

I found that application-roles.properties has an user role entry similar like

#admin=PowerUser,BillingAdmin,

please add admin,developer role to your application user. restart application server.