Legacy Social Provider Handler node
This legacy node is similar to the newer Social Provider Handler node. It takes a provider selection from the Select Identity Provider node and attempts to authenticate the user. The node collects relevant profile information from the provider, transforms the profile information into the appropriate attributes and returns the user to the journey.
This node remains supported in existing journeys. For new journeys, use the Social Provider Handler node instead.
Implement this node with the Select Identity Provider node to use the Social Identity Provider Service.
Compatibility
| Product | Compatible? |
|---|---|
PingOne Advanced Identity Cloud |
Yes |
PingAM (self-managed) |
Yes |
Ping Identity Platform (self-managed) |
Yes |
Outcomes
Account exists-
Social authentication succeeded, and a matching ForgeRock account exists.
No account exists-
Social authentication succeeded, but no matching ForgeRock account exists.
Properties
| Property | Usage |
|---|---|
Transformation Script (required) |
This script is used after the configured provider’s normalization script has mapped the social identity provider’s attributes to a profile format compatible with AM. The transformation script then transforms a normalized social profile to an identity (standalone AM) or a managed object (Ping Identity Platform deployment). Select To view the scripts and bindings, refer to normalized-profile-to-identity.js. Select To view the scripts and bindings, refer to normalized-profile-to-managed-user.js. Normalization scripts ( |
Username Attribute |
(Ping Identity Platform deployments only.) The attribute in IDM that contains the username for this object. |
Client Type |
Specify the client type you are using to authenticate to the provider. Use the default, Select |