Both local and extended local configurations use an ABL application's WEB-INF/users.properties file as the source for user account information.

Local configurations

The local model is usually used during application development, to have a quick way of testing a web application's security structure. The local model allows you to edit accounts and add clear-text passwords in order to test user access based on roles.

To implement the local model, add the following setting in the Security and authentication models section of the oeablSecurity.properties file:
http.all.authmanager=local

For more information, see the oeablSecurity.properties.README file.

After choosing the local security configuration model for a web application, you can add, remove, modify users or user authentication settings by updating the ABL application's WEB-INF/users.properties file.

Extended local configurations

Like the local model, the extended local model uses the WEB-INF/users.properties as the source for user account information. However, the extended local model is more secure because it allows you to use encrypted passwords. Encrypted (hashed/salted) passwords are generated with the GENSPRINGPWD utility.

For more information about the GENSPRINGPWD utility, see Generate encrypted passwords with GENSPRINGPWD.

To implement the extended local model, add the following setting in the Security and authentication models section of the oeablSecurity.properties file:
http.all.authmanager=extlocal

For more information, see the oeablSecurity.properties.README file.

The users.properties file

The following shows the syntax of entries in users.properties:

username=password, role1, [role2, ..., roleN, ] { enabled | disabled }

The following shows the content of the default users.properties file:

restuser=passwordpassword,ROLE_PSCUser,enabled
restdebug=passwordpassword,ROLE_PSCUser,ROLE_PSCDebug,enabled

The contents of the users.properties file are included as an example, and they are not secure since they are stored as plain text. Typically, for a production server, you generate encrypted passwords, and add the secure passwords to the users.properties file. For more information about generating encrypted passwords, see Generate encrypted passwords with GENSPRINGPWD.