Configuring Users
By default only the Admin user exists and a login is required only for administration operations like creating and configuring applications.
It’s possible to create additional users and configure the applications to ask for user credentials when the session starts.
Users can be configured through the WebClient Admin Console.
By default, the Admin Console is reachable via HTTP on the port 8090 of the server where you started the webclient-admin service, i.e.
The Admin credentials are required in order to access the Configuration page.
By default, users are defined via the WebClient interface as follows:
1. set the Security Module Name field to EMBEDDED to make the list of current defined users appear
2. click on the "+" button on the bottom right for a new row to appear in the list
a. fill Username and Password fields with the new user credentials
b. optionally assign a role to the user (see
Roles below for more information)
c. click on the "Apply" button
Roles
WebClient users can be assigned the following roles:
Role | Permissions |
---|
admin | create new users create new applications change the configuration of an application monitor the activity of connected users run an application |
support | view the configuration of an application monitor the activity of connected users run an application |
<none> | run an application |
Only admin and support users have access to the Dashboard.
Setting Security Module Name field to NONE allows all users to access WebClient without authentication. This is not good practice.
The users configured here are available in the whole WebClient environment. It’s also possible to define different users for the single applications. See
Applications Monitoring and Configuration for details.
It’s possible to define users also through a property file or a database. In order to enable these features:
1. click on the "+" below Security Module Class Path
2. select the value "${webclient.rootDir}/security/database+property/*" from the list
3. click on the "Apply" button
After it, the list of options under Security Module changes from
o NONE
o EMBEDDED
to
o NONE
o EMBEDDED
o org.webswing.security.modules.database.DatabaseSecurityModule
o org.webswing.security.modules.property.PropertySecurityModule
For more information about configuring users via property file or database, refer to the next chapters:
Note - regardless of the method that you choose for configuring users, ensure to have at least one user with role “admin”, otherwise it will not be possible to alter the WebClient configuration.