Deprecation of Twitter as an ID Service in Authentications and Connections

Caspio will retire support for Twitter as an ID service for both Authentications and Connections on August 1, 2025. After this date, the Twitter ID service will no longer be available in any Authentications or Connections. This change affects all applications that use Twitter for social login.

Caspio strongly recommends reviewing all applications that currently use Twitter in Authentications or Connections and planning a migration to a supported ID service before the retirement date. Failing to do so will prevent users who sign in with Twitter from accessing your applications after the retirement date.

Migration Steps for Authentications

App authors must migrate users who currently sign in using Twitter to a supported alternative, such as Caspio’s standard login method or an external ID service like Google ID or OpenID.

Steps:

1. In the Authentication data source, identify users who are currently using Twitter to sign in.
2. For the affected users, choose one of the following:
   • Switch users to Caspio’s standard authentication.
   • Switch users to a supported external ID service.
3. Notify affected users about the change and provide them with the necessary credentials or updated login instructions.

Migration Steps for Connections

There is no need to migrate user credentials for Connections, as these configurations do not rely on a user authentication data source. However, app authors should notify users who authenticate through Twitter that they must switch to another supported ID service, such as Google ID or OpenID, before August 1, 2025.