---
title: Twitter Login Integration Kit
description: The Twitter Login Integration Kit allows PingFederate to use Twitter as an identity provider (IdP). This allows users to access service provider (SP) applications by signing into Twitter.
component: twitter
page_id: twitter::pf_twitter_cic
canonical_url: https://docs.pingidentity.com/integrations/twitter/pf_twitter_cic.html
revdate: January 21, 2026
section_ids:
  features: Features
  components: Components
  intended-audience: Intended audience
  system-requirements: System requirements
---

# Twitter Login Integration Kit

The Twitter Login Integration Kit allows PingFederate to use Twitter as an identity provider (IdP) *(tooltip: \<div class="paragraph">
\<p>A service that manages identity information and provides authentication services to relying clients or SPs within a federated or distributed network.\</p>
\</div>)*. This allows users to access service provider (SP) *(tooltip: \<div class="paragraph">
\<p>In SAML, an entity that receives and accepts an authentication assertion issued by an IdP, typically for the purpose of allowing access to a protected resource.\</p>
\</div>)* applications by signing into Twitter.

## Features

* Supports the [PingFederate authentication API](https://docs.pingidentity.com/pingfederate/latest/developers_reference_guide/pf_authentication_api.html).

* Supports the [JavaScript Widget for the PingFederate Authentication API](https://github.com/pingidentity/pf-authn-js-widget).

## Components

* Twitter IdP Adapter

  * Allows PingFederate to communicate with the Twitter API to process sign-on requests and get user information.

* Templates

  * Allows the adapter to prompt the user to sign on. The template can be presented with a browser redirect or as a pop-up window.

  * Allows you to modify the appearance of the sign-on prompt.

* Language packs

  * Allows you to customize or localize the messages returned by the PingFederate authentication API and shown on the templates during authentication. You can find help in [Localizing messages for end users](https://docs.pingidentity.com/pingfederate/latest/administrators_reference_guide/pf_local_message_end_users.html) in the PingFederate documentation.

## Intended audience

This document is intended for PingFederate administrators. If you need help during the setup process, refer to the following resources:

* The following sections of the PingFederate documentation:

  * [Identity provider SSO configuration](https://docs.pingidentity.com/pingfederate/latest/administrators_reference_guide/pf_ident_provid_sso_config.html)

  * [Managing IdP adapters](https://docs.pingidentity.com/pingfederate/latest/administrators_reference_guide/pf_managing_idp_adapters.html)

  * [Authentication policies](https://docs.pingidentity.com/pingfederate/latest/administrators_reference_guide/pf_authentication_policies.html)

  * [SP connection management](https://docs.pingidentity.com/pingfederate/latest/administrators_reference_guide/pf_sp_connect_management.html)

* The following sections of the Twitter documentation:

  * [Developer portal](https://developer.twitter.com/en/docs/developer-portal/dev-portal-enhancements)

  * [Developer Apps](https://developer.twitter.com/en/docs/apps/overview)

## System requirements

* PingFederate 11.3 or later

* A Twitter developer account