Backends configuration | Type
Backends parameters help to manage identity storage and associated features within the server. Those are to keep credentials and identities while providing them abilities helping to manage authorization and authentication provided by the identity provider interfaces.
Backends can be customized through either the Administration API or the user interface providing 6 categories of settings:
- General configuration
- Type
- Email configuration
- Identity federation
- Verifiable credentials
- User metadata
Type parameters
Type is the backend type, can be one of:
- Internal user credentials are stored within boruta postgreSQL dependency database
- LDAP user credentials are checked and updated against a LDAP compliant server
Internal configuration
Password hashing algorithm is the algorithm used to hash the user passwords that then will be stored in their hashed form. All those hashing algorithms are provided with their custom parameters.
- Argon2 uses Argon2 hashing algorithm
- Bcrypt uses Bcrypt hashing algorithm
- Pbkdf2 uses Pbkdf2 hashing algorithm
Any change in either the algorithm or the parameters will invalidate all already stored passwords.
LDAP configuration (experimental)
Host would be the LDAP server hostname.
User RDN attribute would be the user username Relative Distinguished Name.
Base distinguished name (dn) would be the base Distinguished Name.
Users organization unit (ou) would be the users Organization Unit.
Master distinguished name (needed only for user edition) used for username or passowrd edition, would be the master Distinguished Name.
Master password (needed only for user edition) used for username or passowrd edition, would be the master password.
Pool size would be the connection pool size kept alive with the LDAP server
User interface
