---
title: Overview of the SSO flow
description: With the Twitter Login Integration Kit, PingFederate includes the Twitter authentication API in the sign-on flow.
component: twitter
page_id: twitter::pf_twitter_cic_overview_of_the_sso_flow
canonical_url: https://docs.pingidentity.com/integrations/twitter/pf_twitter_cic_overview_of_the_sso_flow.html
revdate: January 21, 2026
section_ids:
  description: Description
---

# Overview of the SSO flow

With the Twitter Login Integration Kit, PingFederate includes the Twitter authentication API in the sign-on flow.

The following diagram illustrates a SP-initiated SSO *(tooltip: \<div class="paragraph">
\<p>In SAML, an identity federation transaction in which the initial action for SSO occurs at the SP site.\</p>
\</div>)* scenario where PingFederate authenticates users to an SP application using the Twitter IdP Adapter.

![A diagram showing the SSO flow using the Twitter Login Integration Kit.](_images/twitter-login-ik-sso-flow-overview.jpg)

## Description

1. The user opens a web application and chooses the Twitter sign-on option.

2. The sign-on link points to the Twitter IdP Adapter.

3. The Twitter IdP Adapter requests a request token from Twitter and provides the callback URL. Twitter returns the request token.

4. The PingFederate server redirects the user to Twitter with the request token and a list of requested permissions. On Twitter, the user authenticates their identity, then authorizes the requested permissions.

   Twitter redirects the browser to the Twitter IdP Adapter callback URL with a verification code.

   |   |                                                                                                                  |
   | - | ---------------------------------------------------------------------------------------------------------------- |
   |   | If the user fails to authenticate or doesn't authorize the request, the response includes an error code instead. |

5. PingFederate sends Twitter the request token and verification code. Twitter validates these components and returns an access token to the PingFederate callback URL.

6. PingFederate sends Twitter a request for user attributes and presents the access token.

7. PingFederate redirects the user to the web application with the user attributes.