You are viewing the documentation for Blueriq 16. Documentation for other versions is available in our documentation directory.
Using the in-memory authentication provider is strongly discouraged in production scenarios, as it introduces security risks.
Defining an in-memory
authentication provider
In the application.properties
file two properties are expected for an in-memory
authentication provider:
blueriq.security.auth-providers.local01.type=in-memory blueriq.security.auth-providers.local01.users.location=users.properties
auth-providers
is the property name of the authentication providers property- After the property name, the name of the authentication provider is specified. In this example the name is
local01
.
An in-memory authentication provider needs the file location of a property file to load the users/roles from, this is specified in the users.location
property.
At startup this file is not created. If the file does not exists and the current user tries to save the users he gets a warning.
An example of a users.properties
file:
# format: USERNAME=PASSWORD,ROLE1,ROLE2 admin={noop}welcome,dcm,administrator jane={noop}welcome02,dcm,operator john={noop}welcome03,dcm
Overview
Content Tools
1 Comment
Robin Collard
Please read "Changes in default password properties" on the following page: Release 11.0 Upgrade Instructions if you are using Blueriq 11.0 or newer.