com.mohiva.play.silhouette.impl.providers
BasicAuthProvider
Related Docs:
object BasicAuthProvider
| package providers
com.mohiva.play.silhouette.impl.providers
The auth info repository.
The password hashers used by the application.
The execution context to handle the asynchronous operations.
Indicates that the entered password doesn't match with the stored one.
Indicates that the entered password doesn't match with the stored one.
Indicates that no password info was stored for the login info.
Indicates that no password info was stored for the login info.
The authentication state.
The authentication state.
Indicates that the stored password cannot be checked with the registered hashers.
Indicates that the stored password cannot be checked with the registered hashers.
Indicates that the authentication was successful.
Indicates that the authentication was successful.
The auth info repository.
The auth info repository.
Authenticates an identity based on credentials sent in a request.
Authenticates an identity based on credentials sent in a request.
The type of the body.
The request.
Some login info on successful authentication or None if the authentication was unsuccessful.
Authenticates a user
Authenticates a user
The login info to search the password info for.
The user password to authenticate with.
The authentication state.
The execution context to handle the asynchronous operations.
The execution context to handle the asynchronous operations.
Encodes the credentials.
Encodes the credentials.
Contains the colon-separated name-value pairs in clear-text string format
The users credentials as plaintext
Gets the provider ID.
A named logger instance.
A named logger instance.
The password hashers used by the application.
The password hashers used by the application.
A request provider implementation which supports HTTP basic authentication.
The provider supports the change of password hashing algorithms on the fly. Sometimes it may be possible to change the hashing algorithm used by the application. But the hashes stored in the backing store can't be converted back into plain text passwords, to hash them again with the new algorithm. So if a user successfully authenticates after the application has changed the hashing algorithm, the provider hashes the entered password again with the new algorithm and stores the auth info in the backing store.