--- title: Legacy Social Provider Handler node description: 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. component: auth-node-ref version: latest page_id: auth-node-ref::legacy-social-provider-handler canonical_url: https://docs.pingidentity.com/auth-node-ref/latest/legacy-social-provider-handler.html keywords: ["Nodes & Trees", "Journeys", "Authentication", "Social Authentication", "Scripts"] page_aliases: ["auth-node-legacy-social-provider-handler.adoc"] superseded_by: https://docs.pingidentity.com/auth-node-ref/latest/legacy-social-provider-handler.html section_ids: availability: Availability configuration: Configuration callbacks: Callbacks outcomes: Outcomes --- # Legacy Social Provider Handler node This legacy node is similar to the newer [Social Provider Handler node](social-provider-handler.html). It takes a provider selection from the [Select Identity Provider node](select-identity-provider.html) 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](social-provider-handler.html) instead. Implement this node with the [Select Identity Provider node](select-identity-provider.html) to use the Social Identity Provider Service. ## Availability | Product | Available? | | ------------------------------------- | ---------- | | PingOne Advanced Identity Cloud | Yes | | PingAM (self-managed) | Yes | | Ping Identity Platform (self-managed) | Yes | ## Configuration | 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 Advanced Identity Cloud. The *transformation* script then transforms a normalized social profile to an identity or a managed object.Select `Normalized Profile to Managed User` (default), or a custom script you've created to transform the profile to a managed object. Review the sample script ([normalized-profile-to-managed-user.js](https://docs.pingidentity.com/pingoneaic/am-scripting/sample-scripts.html#normalized-profile-to-managed-user-js)) for a list of bindings.You can use either the next-generation script type (`Social Provider Handler Node`) or the legacy script type (`Social Identity Provider Profile Transformation`) to create a custom script. Don't use normalization scripts (\-profile-normalization.\*) for this purpose. | | Username Attribute | The attribute in the underlying identity service (PingIDM) that contains the username for this object. | | Client Type | The client type you're using to authenticate to the provider. Select one of the following:- `BROWSER` (default) Select this type for Ping Identity-provided user interfaces or the Ping SDK for JavaScript. With this setting, the node returns the `RedirectCallback`. - `NATIVE` Select this type for the Ping SDK for Android or iOS. With this setting, the node returns the `IdPCallback`. | | Store Tokens | Select this option to store access and refresh tokens in the transient state for use by subsequent nodes in the journey.Sometimes, the social provider requires these tokens, for example, to revoke user authorization. If you choose to store tokens, you can configure a [Scripted Decision node](scripted-decision.html) later in the journey to handle your social provider use case.Default: `Not enabled` | | Subject Attribute | This property doesn't apply to Advanced Identity Cloud. | ## Callbacks The node sends either a `RedirectCallback` or an `IdPCallback`, depending on the selected client type. Learn more in [Supported callbacks](https://docs.pingidentity.com/pingoneaic/am-authentication/callbacks-supported.html). ## Outcomes * `Account exists` Social authentication succeeded and a matching Advanced Identity Cloud account exists. * `No account exists` Social authentication succeeded but no matching Advanced Identity Cloud account exists.