Social Connections Settings

Social connections settings enable and configure the integrations with supported social identity providers. As a Digital Identity Management Admin user, you can enable and configure social integrations with one or more of our supported social account providers. Currently, Digital Identity Management supports integrations with Apple, Facebook, Google, LinkedIn, and Microsoft (Azure). Configure the social connections from Admin console > Authentication > Social Connections page. When you enable and configure a social integration with one or more of these providers, then you can build social onboarding and social authentication user flows into your application(s). More specifically, your client application(s) can execute our OAuth 2.0-based social Processes, and specify the enabled provider during Process execution. Before you configure a social media integration, an app on the social provider’s developer portal must be created. You must have secret keys (for example, App/Client ID and App/Client Secret) issued by the social media provider. Refer to the following topics for more details:

Onboard and Authenticate User with Social Account – an anonymous user onboards or authenticates with a social account.
Associate Social Account to User – an authenticated user connects their social account to their User entity.

Apple

The table below lists and explains all the settings related to Apple social connection:

Setting	Description	Example
Enable Apple	Whether to enable Apple as a social media provider. This will allow social association, social onboarding, and social association Processes to use Apple as a specified provider.	True
Client ID	ID used for integration between Digital Identity Management and Apple.	com.amdocs.example
Redirect URL	The Redirect URL to your client application. This should point to a landing page that you or your developers build into the application. When the social provider redirects back to this page, it will pass along `code` and `state` values that your client will then pass back to Digital Identity Management using our GET /process/step?code={code value}&state={state value} API. This enables Digital Identity Management to complete the Process.	https://abc-ulm-pdt.m1amdocs.io/platform/rest/v85/social\_end
Client secret	Shared secret key used for integration between Digital Identity Management and Apple.	eyJraWQiOiI4VzdexampleGMlIzVjQ3IiwiY

Facebook

The table below lists and explains all the settings related to Facebook social connection:

Setting	Description	Example
Enable Facebook	Whether to enable Facebook as a social media provider. This will allow social association, social onboarding, and social association Processes to use Facebook as a specified provider.	False
Client ID	ID used for integration between Digital Identity Management and Facebook.	com.amdocs.example
Redirect URL	The Redirect URL to your client application. This should point to a landing page that you or your developers build into the application. When the social provider redirects back to this page, it will pass along `code` and `state` values that your client will then pass back to Digital Identity Management using our GET /process/step?code={code value}&state={state value} API. This enables Digital Identity Management to complete the Process.	https://abc-ulm-pdt.m1amdocs.io/social\_end
Client secret	Shared secret key used for integration between Digital Identity Management and Facebook.	fdsfeyJraVzdexampleVgjghjjQ3Iiwihbgghf

Google

The table below lists and explains all the settings related to Google social connection:

Setting	Description	Example
Enable Google	Whether to enable Google as a social media provider. This will allow social association, social onboarding, and social association Processes to use Google as a specified provider.	True
Client ID	ID used for integration between Digital Identity Management and Google.	com.amdocs.example
Redirect URL	The Redirect URL to your client application. This should point to a landing page that you or your developers build into the application. When the social provider redirects back to this page, it will pass along `code` and `state` values that your client will then pass back to Digital Identity Management using our GET /process/step?code={code value}&state={state value} API. This enables Digital Identity Management to complete the Process.	https://abc-ulm-pdt.m1amdocs.io/social\_end
Client secret	Shared secret key used for integration between Digital Identity Management and Google.	VwLaJraWiOiI4VzdexampleGMlIzVjQ3IN36L

The table below lists and explains all the settings related to LinkedIn social connection:

Setting	Description	Example
Enable LinkedIn	Whether to enable LinkedIn as a social media provider. This will allow social association, social onboarding, and social association Processes to use LinkedIn as a specified provider.	True
Client ID	ID used for integration between Digital Identity Management and LinkedIn.	com.amdocs.example
Redirect URL	The Redirect URL to your client application. This should point to a landing page that you or your developers build into the application. When the social provider redirects back to this page, it will pass along `code` and `state` values that your client will then pass back to Digital Identity Management using our GET /process/step?code={code value}&state={state value} API. This enables Digital Identity Management to complete the Process.	https://abc-ulm-pdt.m1amdocs.io/platform/rest/v85/social\_end
Client secret	Shared secret key used for integration between Digital Identity Management and LinkedIn.	t8KrwWr8N4EdbzdexampleGMlIzVjQ3IqqUp

Microsoft

The table below lists and explains all the settings related to Microsoft social connection:

Setting	Description	Example
Enable Microsoft	Whether to enable Microsoft as a social media provider. This will allow social association, social onboarding, and social association Processes to use Microsoft as a specified provider.	False
Client ID	ID used for integration between Digital Identity Management and Facebook.	com.amdocs.example
Redirect URL	The Redirect URL to your client application. This should point to a landing page that you or your developers build into the application. When the social provider redirects back to this page, it will pass along `code` and `state` values that your client will then pass back to Digital Identity Management using our GET /process/step?code={code value}&state={state value} API. This enables Digital Identity Management to complete the Process.	https://abc-ulm-pdt.m1amdocs.io/social\_end
Client secret	Shared secret key used for integration between Digital Identity Management and Microsoft.	fdsfeyJraVzdexampleVgjghjjQ3Iiwihbgghf

Social Connection Setup

Parent topic:Authentication

Home

Guides

APIs

Apple

Facebook

Google

LinkedIn

Microsoft

​Related Topics

​Apple

​Facebook

​Google

​LinkedIn

​Microsoft

Related Topics

Apple

Facebook

Google

LinkedIn

Microsoft