Twitter 的 OmniAuth 策略
This gem contains the X (formerly Twitter) strategy for OmniAuth.
X supports a few different methods of integration. This strategy implements the browser variant of the "Sign in with Twitter" flow.
This strategy implements X's OAuth 1.0a flow and returns an OAuth access token and access token secret for the authenticated user.
X's developer documentation contains detailed information about its OAuth implementation if you are interested in the protocol details.
You should have already installed OmniAuth into your app; if not, read the OmniAuth README(https://github.com/omniauth/omniauth) to get started.
Now sign in to the X Developer Portal(https://developer.x.com/apps) and create an application. Take note of your API Key and API Secret (not the Access Token and Access Token Secret) because that is what your web application will use to authenticate against the X API. Make sure to configure a callback URL in the X Developer Portal or else you may get authentication errors. The configured callback URL should match the callback URL used by your application.
For production applications, it is recommended to store API credentials using Rails credentials, environment variables, or another secure secret management solution.
First start by adding this gem to your Gemfile:
gem 'omniauth-twitter'If you need to use the latest HEAD version, you can do so with:
gem 'omniauth-twitter', github: 'arunagw/omniauth-twitter'Next, tell OmniAuth about this provider. For a Rails app, your config/initializers/omniauth.rb file should look like this:
Rails.application.config.middleware.use OmniAuth::Builder do
provider :twitter, "API_KEY", "API_SECRET"
endAlternatively, you may use environment variables:
Rails.application.config.middleware.use OmniAuth::Builder do
provider :twitter,
ENV.fetch("TWITTER_API_KEY"),
ENV.fetch("TWITTER_API_SECRET")
endReplace "API_KEY" and "API_SECRET" with the appropriate values you obtained earlier.
X supports a few options when authenticating. Usually you would specify these options as query parameters to the X API authentication URL (https://api.x.com/oauth/authenticate by default). With OmniAuth, of course, you use http://yourapp.com/auth/twitter instead. Because of this, this OmniAuth provider will pick up the query parameters you pass to the /auth/twitter URL and re-use them when making the call to the X API.
The options are:
force_login - This option sends the user to a sign-in screen to enter their X credentials, even if they are already signed in. This is handy when your application supports multiple X accounts and you want to ensure the correct user is signed in. Example: http://yoursite.com/auth/twitter?force_login=true
screen_name - This option implies force_login, except the screen name field is pre-filled with a particular value. Example: http://yoursite.com/auth/twitter?screen_name=jim
lang - The language used in the X prompt. This is useful for adding i18n support since the language of the prompt can be dynamically set for each user. Example: http://yoursite.com/auth/twitter?lang=pt
secure_image_url - Set to true to use https for the user's image URL. Default is false.
image_size: This option defines the size of the user's image. Valid options include mini (24x24), normal (48x48), bigger (73x73) and original (the size of the image originally uploaded). Default is normal.
x_auth_access_type - This option (described in the X API documentation) lets you request the level of access that your app will have to the X account in question. Example: http://yoursite.com/auth/twitter?x_auth_access_type=read
use_authorize - There are actually two URLs you can use against the X API. As mentioned, the default is https://api.x.com/oauth/authenticate, but you also have https://api.x.com/oauth/authorize. Passing this option as true will use the second URL rather than the first. With authenticate, if your user has already granted permission to your application, X may redirect straight back to your application, whereas authorize forces the user to go through the authorization screen again. For certain use cases this may be necessary. Example: http://yoursite.com/auth/twitter?use_authorize=true.
Here's an example of a possible configuration where the user's original profile picture is returned over https, the user is always prompted to sign-in and the default language of the the X authentication prompt:
Rails.application.config.middleware.use OmniAuth::Builder do
provider :twitter, "API_KEY", "API_SECRET",
{
:secure_image_url => 'true',
:image_size => 'original',
:authorize_params => {
:force_login => 'true',
:lang => 'pt'
}
}
endThe structure below is a representative example of the authentication hash available in request.env['omniauth.auth']. Fields returned by X may vary depending on API permissions, user settings, and platform changes.
…Ryan Bates has put together an excellent RailsCast on OmniAuth:
OmniAuth Twitter is tested under Ruby 2.6 through 4.0 and JRuby.
Please read the contribution guidelines for some information on how to get started. No contribution is too small.
Copyright (c) 2011 by Arun Agrawal
Permission is hereby granted, free of charge, to any person obtaining a copy of this software and associated documentation files (the "Software"), to deal in the Software without restriction, including without limitation the rights to use, copy, modify, merge, publish, distribute, sublicense, and/or sell copies of the Software, and to permit persons to whom the Software is furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM, OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE SOFTWARE.
暂无开放 Issues,或尚未同步最近议题。