---
title: Deploying the integration files
description: To get started with the integration, deploy the Twitter Login Integration Kit files to your PingFederate directory.
component: twitter
page_id: twitter:setup:pf_twitter_cic_deploying_the_integration_files
canonical_url: https://docs.pingidentity.com/integrations/twitter/setup/pf_twitter_cic_deploying_the_integration_files.html
revdate: January 21, 2026
section_ids:
  steps: Steps
---

# Deploying the integration files

To get started with the integration, deploy the Twitter Login Integration Kit files to your PingFederate directory.

## Steps

1. Download the Twitter Login Integration Kit `.zip` archive from the [**Add-ons** tab of the PingFederate downloads page](https://www.pingidentity.com/en/resources/downloads/pingfederate.html) or the [Ping Identity Marketplace](https://marketplace.pingone.com/item/twitter-login-integration-kit).

2. Stop PingFederate, if it's running.

3. If you're upgrading an existing deployment, back up your customizations and delete earlier versions of the integration files:

   1. Back up any Twitter Login Integration Kit files that you customized in the `<pf_install>/pingfederate/server/default/conf/` directory.

   2. Delete the `pf-twitter-adapter-<version>.jar` file from your `<pf_install>/pingfederate/server/default/deploy` directory.

4. Extract the `.zip` archive and merge the contents of the `dist` directory with your `<pf_install>/pingfederate` directory.

5. If there's more than one version of the `pf-authn-api-sdk-<version>.jar` file in your `<pf_install>/pingfederate/server/default/lib` directory, delete all but the latest version of the file.

6. If you backed up any customized files, modify the new files with your customizations.

7. Start PingFederate.

8. If you operate PingFederate in a cluster, repeat steps 2 - 7 for each engine node.