Fusion provides your customers the ability to sign in to your web portal or applications using credentials from existing social identity providers.
When the customer uses these to authenticate they are redirected back to your application and you benefit from some (you can choose how much) of their social profile information from being stored within the Strivacity Identity Store. You can also define (within each Social Login provider) the frequency on when this information is updated.
Fusion currently supports the following social identity login providers:
See the specific guides to quickly setup your application for use with any of these supported providers:
When a social login provider is enabled for an application, a customer is then able to register to use that application using their social login. This process requests the customers consent and according to that consent, Fusion will initially synchronize the social profile attributes with the Strivacity Identity Store.
Once a customer has registered using a social login, they can continue to use that account for any further authentication. This removes the need for customer to have to register an account and require a separate username and password (or Multi-factor Authentication) to log-in.
Starting from customer registration, Fusion can synchronize and store social profile information during each customer login. Since a customer can use multiple social login providers, Fusion supports the incremental updating of the customer account where the attributes from the last successful login would always win - ensuring the account is always up to date.
Since Fusion supports OAuth 2.0 scopes, you can choose selectively choose which social attributes to synchronize to the Strivacity Identity store.
The social login process starts at the Fusion login screen and then goes out to the social login provider and back:
Setting up a Social Login provider with Fusion requires just three simple steps. Each of these steps is described within Setup and Manage Social Logins
1) Setup your social provider, e.g. the configuration in Facebook, Google, Github etc
2) Setup your social provider as an identity provider in Fusion
3) Add your configured social login providers to an Application Policy. See Adding a Social Login to an Application for guidance on how to do this