Social login enables users to register on your web site by using an account created with a third-party identity provider (IDP). For example, instead of creating a new site-specific user name and password just for your site, users can register by using an existing Facebook or Twitter account.
You can use the Engage Dashboard to configure the identity providers users can employ to register or to log on to your site. Because setup requirements for identity providers differ, we have put together configuration guides for each Identity Cloud-compatible IDP. Links to these configuration guides are shown in the table below. In addition, the table also:
- Lists the identity provider’s string specifier. This value is required when using the Social APIs to manage social login.
- Indicates whether you need to create an app in order to configure the provider for social logon.
- Specifies whether you can choose which user data is returned by an identity provider.
In the table you will also see a handful of providers with the entry N/A in each column. These are identity providers that no longer offer social login but are still shown in the Engage Dashboard. Other providers are marked by asterisks. For information on these providers, contact your Akamai representative.
Following are the identity providers available in the Engage Dashboard, as well as links to their respective configuration guides:
Provider | String Specifier | App Required | Return Data Customizable |
---|---|---|---|
amazon | Yes | Yes | |
doccheck | *** | *** | |
doximity | |||
Yes | Yes | ||
fimnet | *** | *** | |
flickr | |||
foursquare | Yes | ||
Yes | Yes | ||
livejournal | |||
medikey | *** | *** | |
medy | *** | *** | |
microsoftaccount | Yes | Yes | |
mixi | Yes | Yes | |
odnoklassniki | Yes | Yes | |
renren | Yes | ||
salesforce | Yes | ||
sina weibo | Yes | ||
vk | Yes | Yes | |
Yes | |||
yahoo | Yes |