---
title: Integrating social sign-on into your application
description: To complete your Twitter sign-on integration, add a sign-on hyperlink to your application.
component: twitter
page_id: twitter:setup:pf_twitter_cic_integrating_social_sign_on_into_your_application
canonical_url: https://docs.pingidentity.com/integrations/twitter/setup/pf_twitter_cic_integrating_social_sign_on_into_your_application.html
revdate: January 21, 2026
section_ids:
  steps: Steps
---

# Integrating social sign-on into your application

To complete your Twitter sign-on integration, add a sign-on hyperlink to your application.

## Steps

1. If your application is outside the PingFederate domain, configure an SP connection:

   1. Create a service provider (SP) connection to your application as shown in [SP connection management](https://docs.pingidentity.com/pingfederate/latest/administrators_reference_guide/pf_sp_connect_management.html) in the PingFederate documentation.

      |   |                                                                                                                                                                                                                                                                     |
      | - | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
      |   | Use the Twitter IdP Adapter instance as an authentication source. Learn more in [Mapping an adapter instance](https://docs.pingidentity.com/pingfederate/latest/administrators_reference_guide/pf_mapping_adapter_instance.html) in the PingFederate documentation. |

   2. In your web application, create a hyperlink to allow users to sign on to the SP application. Use the following URL and replace the variables based on the descriptions in the following table:

      `https://<pf_host>:<pf_port>/idp/startSSO.ping?PartnerSpId=<ConnectionId>`

      | Variable          | Description                                                                                        |
      | ----------------- | -------------------------------------------------------------------------------------------------- |
      | *\<pf\_host>*     | The host name or IP address of the PingFederate server.                                            |
      | *\<pf\_port>*     | The port number for PingFederate.                                                                  |
      | *\<ConnectionId>* | The federation identifier of the SP for the connection that uses the Twitter IdP Adapter instance. |

2. If your application is inside the PingFederate domain, configure an adapter-to-adapter mapping:

   1. Create an SP connection to your application as shown in [SP connection management](https://docs.pingidentity.com/pingfederate/latest/administrators_reference_guide/pf_sp_connect_management.html) in the PingFederate documentation.

      |   |                                                                                                                                                                                                                                                                     |
      | - | ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
      |   | Use the Twitter IdP Adapter instance as an authentication source. Learn more in [Mapping an adapter instance](https://docs.pingidentity.com/pingfederate/latest/administrators_reference_guide/pf_mapping_adapter_instance.html) in the PingFederate documentation. |

   2. On the **System > Protocol Settings > Roles & Protocols** page, select **Enable Identity Provider (IdP) role and support for the following** and **Enable Service Provider (SP) role and support for the following**.

   3. In both the **Enable Identity Provider** and **Enable Service Provider** sections, select any protocol, such as **SAML 2.0**. Click **Save**.

      |   |                                                                                                                                  |
      | - | -------------------------------------------------------------------------------------------------------------------------------- |
      |   | PingFederate requires a protocol selection to activate the roles. The protocol that you select is not used for this integration. |

   4. On the **Service Provider > Adapters** page, create or select an adapter instance that's integrated with the application as shown in [SP application integration settings](https://docs.pingidentity.com/pingfederate/latest/administrators_reference_guide/pf_sp_applicat_integra_settings.html) in the PingFederate documentation.

   5. On the **Identity Provider > Adapter-to-Adapter Mappings** page, configure the IdP-to-SP adapter mapping as shown in [Adapter-to-adapter mappings](https://docs.pingidentity.com/pingfederate/latest/administrators_reference_guide/pf_adaptertoadapter_mappings.html) in the PingFederate documentation.

   6. In your web application, create a hyperlink to allow users to sign on to the SP application. Use the following URL and replace the variables based on the descriptions in the table below:

      `https://<pf_host>:<pf_port>/pf/adapter2adapter.ping?IdpAdapterId=<IdpAdapterId>&SpSessionAuthnAdapterId=<SpAdapterId>`

      | Variable          | Description                                                                               |
      | ----------------- | ----------------------------------------------------------------------------------------- |
      | *\<pf\_host>*     | The host name or IP address of the PingFederate server.                                   |
      | *\<pf\_port>*     | The port number for PingFederate.                                                         |
      | *\<IdpAdapterId>* | The instance ID of the Twitter IdP Adapter instance.                                      |
      | *\<SpAdapterId>*  | The instance ID of the SP adapter instance that has been integrated with the application. |