WCF Update Twitter-Login to OAuth2

WSC still uses OAuth1, which may lead to application suspension (because Twitter/X is.... nevermind).

https://developer.twitter.com/en/docs/authentication/guides/v2-authentication-mapping https://developer.twitter.com/en/docs/authentication/oauth-2-0/authorization-code

Please consider migrating to OAuth2.

Sep 15 '23 12:09 SoftCreatR

Log In with Twitter is documented as OAuth 1.0: https://developer.twitter.com/en/docs/authentication/guides/log-in-with-twitter

Sep 15 '23 12:09 TimWolla

I just got my application suspended with this information:

And since it's only used for the purpose of logging in to WSC, it must have something to do with your integration.

Sep 15 '23 12:09 SoftCreatR

No e-mail is transmitted when using the OAuth2 API. This was possible with the OAuth1 API. The assignment to users is still possible, the X userIDs have not changed. To call up your own profile, it is not sufficient to specify users.read as the scope, but tweet.read users.read follows.read offline.access should work. The previous API keys can NOT be used for the new API, the credentials under OAuth 2.0 Client ID and Client Secret must be used.

Feb 18 '25 12:02 Cyperghost