--- title: Legacy Social Provider Handler node description: Configure the Legacy Social Provider Handler node to authenticate users with a social identity provider and collect profile attributes. Use the Social Provider Handler node for new journeys. component: auth-node-ref version: 8.1 page_id: auth-node-ref::legacy-social-provider-handler canonical_url: https://docs.pingidentity.com/auth-node-ref/latest/legacy-social-provider-handler.html llms_txt: https://docs.pingidentity.com/auth-node-ref/llms.txt docs_for_agents: https://developer.pingidentity.com/build-with-ai/docs-for-agents.md revdate: 2026-08-18T00:00:00Z keywords: ["Nodes & Trees", "Journeys", "Authentication", "Social Authentication", "Scripts"] page_aliases: ["auth-node-legacy-social-provider-handler.adoc"] 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 AM. The *transformation* script then transforms a normalized social profile to an identity or a managed object.Select `Normalized Profile to Identity` (AM), `Normalized Profile to Managed User` (Ping Identity Platform), or a custom script you've created to transform the profile to an identity object. Review the sample script ([normalized-profile-to-identity.js](https://docs.pingidentity.com/pingam/8.1/am-scripting/sample-scripts.html#normalized-profile-to-identity-js) or [normalized-profile-to-managed-user.js](https://docs.pingidentity.com/pingam/8.1/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 | Ping Identity Platform deployments onlyThe 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 | The attribute in the underlying identity store that's used to search for an existing user. This attribute is only used in AM standalone deployments that use an identity store other than PingDS.Default: `iplanet-am-user-alias-list` | ## 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/pingam/8.1/am-authentication/callbacks-supported.html). ## Outcomes * `Account exists` Social authentication succeeded and a matching AM account exists. * `No account exists` Social authentication succeeded but no matching AM account exists.