A request provider implementation which supports HTTP basic authentication.
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.
The social profile contains all the data returned from the social providers after authentication.
The social profile contains all the data returned from the social providers after authentication.
Not every provider returns all the data defined in this class. This is also the representation of the most common profile information provided by the social providers. The data can be used to create a new identity for the first authentication(which is also the registration) or to update an existing identity on every subsequent authentication.
The linked login info.
Maybe the first name of the authenticated user.
Maybe the last name of the authenticated user.
Maybe the full name of the authenticated user.
Maybe the email of the authenticated provider.
Maybe the avatar URL of the authenticated provider.
The profile builder for the common social profile.
A provider for authenticating with credentials.
A provider for authenticating with credentials.
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.
The OAuth1 details.
The OAuth1 details.
The consumer token.
The consumer secret.
Base class for all OAuth1 providers.
The OAuth1 service trait.
The OAuth1 settings.
The OAuth1 settings.
The request token URL provided by the OAuth provider.
The access token URL provided by the OAuth provider.
The authorization URL provided by the OAuth provider.
The callback URL to the application after a successful authentication on the OAuth provider. The URL can be a relative path which will be resolved against the current request's host.
The consumer ID provided by the OAuth provider.
The consumer secret provided by the OAuth provider.
The OAuth1 token secret.
The OAuth1 token secret.
This represents the oauth_token_secret returned from the provider with the request token and which is then needed to retrieve the access token. The secret must be stored between two requests and this implementation provides an abstract way to store the secret in different locations.
Provides the token secret for OAuth1 authentication providers.
The Oauth2 info.
The Oauth2 info.
The access token.
The token type.
The number of seconds before the token expires.
The refresh token.
Additional params transported in conjunction with the token.
Base class for all OAuth2 providers.
The OAuth2 settings.
The OAuth2 settings.
The authorization URL provided by the OAuth provider.
The access token URL provided by the OAuth provider.
The redirect URL to the application after a successful authentication on the OAuth provider. The URL can be a relative path which will be resolved against the current request's host.
The client ID provided by the OAuth provider.
The client secret provided by the OAuth provider.
The OAuth2 scope parameter provided by the OAuth provider.
Additional params to add to the authorization request.
Additional params to add to the access token request.
A map of custom properties for the different providers.
The OAuth2 state.
The OAuth2 state.
This is to prevent the client for CSRF attacks as described in the OAuth2 RFC.
https://tools.ietf.org/html/rfc6749#section-10.12
Provides state for authentication providers.
The OpenID details.
The OpenID details.
The openID.
The attributes returned from the provider.
Base class for all OpenID providers.
The OpenID service trait.
The OpenID settings.
The OpenID settings.
The OpenID provider URL used if no openID was given. @see https://willnorris.com/2009/07/openid-directed-identity-identifier-select
The callback URL to the application after a successful authentication on the OpenID provider. The URL can be a relative path which will be resolved against the current request's host.
Required attributes to return from the provider after a successful authentication.
Optional attributes to return from the provider after a successful authentication.
An URL pattern that represents the part of URL-space for which an OpenID Authentication request is valid.
The social profile contains all the data returned from the social providers after authentication.
Builds the social profile.
Parses a social profile.
Parses a social profile.
A parser transforms the content returned from the provider into a social profile instance. Parsers can be reused by other parsers to avoid duplicating code.
The content type to parse a profile from.
The type of the profile to parse to.
The base interface for all social providers.
The companion object.
The companion object.
The OAuth1Provider companion object.
The Oauth2 info companion object.
The OAuth2Provider companion object.
The OpenIDProvider companion object.
The companion object.
Contains com.mohiva.play.silhouette.api.Provider implementations that provide authentication for different schemes and services.