Adding the Provider ID in the initial Request
Like most Processes, this Process is initialized by the Process Start API. The Process Start API optionally consumes no payload but you can actually add the required parameters upfront in the initial API request URL. For example, in a normal invocation, the Process Start API consumes no payload:providerID:
providerId in the initial Process Start request.
The client specify the providerID in either the request:
providerID to the request URL or request body enables you to build your application to display clear badges or links for the user (e.g., “Link Facebook to User Profile”). The client can then invoke the provider-specific variation of the Process when a user clicks on a provider-specific badge or link.
Process Flow
This flow describes the Associate Social Process at a high level, “happy path” flow: Preconditions- The Digital Identity Management User is fully activated with at least one verified email or mobile.
- The user is currently authenticated and in the client’s version of the user profile or user settings menu.
- The user has at least one social media account with a supported provider.
- The social provider integration has been enabled and configured in the MarketONE Admin console.
- The user selects to add a specific social media account to their sign-in options.
- The client redirects to the social provider, and the user authenticates into that provider.
- The social provider navigates the browser back to Digital Identity Management.
- On the backend, the provider sends along an authorization grant code to Digital Identity Management.
- Digital Identity Management makes a separate call to the provider backend and exchanges the code for an access token.
- Digital Identity Management makes another call to the provider backend to redeem the token for user data.
- The user data includes the user’s name, email/mobile, and an internal social media ID from the provider.
- Digital Identity Management searches for any existing User entity currently associated to this particular social media ID.
- If no User entity is found, the Process prompts the user to confirm that they want to connect their User ID to the selected social media account.
- The user confirms and Digital Identity Management associates the social media with the User ID.
- The user’s social account is associated to their Digital Identity Management User ID.
- The social account can be used for authentication with the Onboard and Authenticate User with Social Account Process.
- The user failed to sign-in with the social provider’s website.
- The social media account is already associated to another Digital Identity Management User ID.
- The selected social media provider is not enabled or supported.
- Access token error (social provider does not return user information to Digital Identity Management).
App Settings
This Process currently has no relevant app settings to configure the Process behavior.User Journey Diagram
This flow diagram illustrates the standard user journey using the Associate Social Account to User ID Process. [product: dim]
Use Cases
See the following use case topics for guided API walk-throughs of this Process:See Also
- Once the user associates a social account to their User ID, then can then authenticate into Digital Identity Management with the Onboard & Authenticate User with Social Account Process.
- The same Process,Onboard & Authenticate User with Social Account onboards a user into Digital Identity Management for the first time.
- The Dissociate Social Account from User Process removes a currently associated account.
- Associate social account to existing User
- Social account association errors

