com.mohiva.play.silhouette.contrib.services
The auth info DAO implementations.
Retrieves the auth info which is linked with the specified login info.
Retrieves the auth info which is linked with the specified login info.
The linked login info.
The class tag of the auth info.
The retrieved auth info or None if no auth info could be retrieved for the given login info.
Saves auth info.
Saves auth info.
This method gets called when a user logs in (social auth) or registers. This is the chance to persist the auth info for a provider in the backing store. If the application supports the concept of "merged identities", i.e., the same user being able to authenticate through different providers, then make sure that the auth info for every linked login info gets stored separately.
The login info for which the auth info should be saved.
The auth info to save.
The saved auth info.
An implementation of the auth info service which delegates the storage of an auth info instance to its appropriate DAO.
Due the nature of the different auth information it is hard to persist the data in a single data structure, expect the data gets stored in a serialized format. With this implementation it is possible to store the different auth info in different backing stores. If we speak of a relational database, then the auth info can be stored in different tables. And the tables represents the internal data structure of each auth info object.