Authentication providers

Blueriq uses Spring Security to allow custom flexible authentication providers. Spring Security provides a variety of options for performing authentication – all following a simple contract – an Authentication request is processed by an AuthenticationProvider and a fully authenticated object with full credentials is returned.
The 'blueriqAuthenticationManager' defined in 'com.aquima.web.boot.SecurityConfiguration' allows configuration based on Spring environment properties. The anonymous authenticationProvider should is be added (hardcoded) at the end of the authentication providers chain.

Blueriq provides support for an 'in-memory' authentication provider and a "customBean" authentication provider for a custom implmentation. Multiple authentication providers can be chained. Every authentication provider has a must have an unique name. This name is also used in the auth-providers-chain property to determine the order of the authentication providers in the chain.  

...

All security properties are prefixed with "blueriq.security".

An in-memory authentication provider

In the application.properties file two properties are expected. Example of an 'in-memory' authentication provider configuration:

...

# format: USERNAME=PASSWORD,ROLE1,ROLE2
admin=welcome,dcm,administrator
jane=welcome02,dcm,operator
john=welcome03,dcm

A customBean authentication provider

blueriq.security.auth-providers.ldap01.type=customBean

...