The default query to be used for authentication
The default query to retrieve all permissions for the role
The default query to retrieve all roles for the user
The default role prefix
Compute the hashed password given the unhashed password and the salt without nonce
The implementation relays to the JDBCHashStrategy provided.
Compute the hashed password given the unhashed password and the salt
The implementation relays to the JDBCHashStrategy provided.
Compute a salt string.
The implementation relays to the JDBCHashStrategy provided.
Set the authentication query to use. Use this if you want to override the default authentication query.
Provide a application configuration level on hash nonce's as a ordered list of nonces where each position corresponds to a version.
The nonces are supposed not to be stored in the underlying jdbc storage but to be provided as a application configuration. The idea is to add one extra variable to the hash function in order to make breaking the passwords using rainbow tables or precomputed hashes harder. Leaving the attacker only with the brute force approach.
The implementation relays to the JDBCHashStrategy provided.
Set the permissions query to use. Use this if you want to override the default permissions query.
Set the role prefix to distinguish from permissions when checking for isPermitted requests.
Set the roles query to use. Use this if you want to override the default roles query.
Create a JDBC auth provider implementation
Generated using TypeDoc
Factory interface for creating {@link AuthenticationProvider} instances that use the Vert.x JDBC client.
By default the hashing strategy is SHA-512. If you're already running in production this is backwards compatible, however for new deployments or security upgrades it is recommended to use the PBKDF2 strategy as it is the current OWASP recommendation for password storage.