I made this gem.
This gem is one of the OmniAuth strategies for Twitter, using OAuth 2.0 for the authentication protocol.
Yes, the omniauth-twitter gem is a well-maintained, widely-used gem.
But, omniauth-twitter uses OAuth 1.0a.
When 2021-12-15, Twitter announced OAuth 2.0 General Availability.
We can hardly believe it either, but It’s finally here! ⌛— Twitter Dev (@TwitterDev) December 14, 2021
Today, OAuth 2.0 and new fine-grained permission scopes are available to all developers. Thank you to our developer community who worked alongside us in the beta, and helped us get this right. https://t.co/jVJeDuF7rm
And we can use “new fine-grained permission scopes” at the release.
We could choose those three kinds of scopes in the older permission scope. That’s too rough.
But now, We can choose enough permissions from the list on OAuth 2.0 (through Twitter API V2)
I created a gem, “omniauth-twitter2”.
This is one of the omniauth strategies, so it’s easy to integrate your rails app if you use omniauth (or devise?)
(“2” means OAuth 2.0, not means successor of “omniauth-twitter” gem. because the gem still working everywhare!)
And I have created a sample application that uses omniauth and omniauth-twitter2.
This app only signs in with twitter, but it’s enough to show how to implement “sign in with Twitter”.
If you want to use OAuth 2.0 API in your twitter app, you should move your app to under “Project”. You can’t use OAuth 2.0 in your app if the app is still a “Standalone app”.
…And I’m not a specialist in the authentication. Please give me a pull request or issue if you found a bug.