A Ruby wrapper for the OAuth 2.0 specification. This is a work in progress, being built first to solve the pragmatic process of connecting to existing OAuth 2.0 endpoints (a.k.a. Facebook) with the goal of building it up to meet the entire specification over time.
gem install oauth2
- View Source on GitHub (https://github.com/intridea/oauth2)
- Report Issues on GitHub (https://github.com/intridea/oauth2/issues)
- Read More at the Wiki (https://wiki.github.com/intridea/oauth2)
Below is a fully functional example of a Sinatra application that would authenticate to Facebook utilizing the OAuth 2.0 web server flow.
require 'rubygems'
require 'sinatra'
require 'oauth2'
require 'json'
def client
OAuth2::Client.new('app_id', 'app_secret', :site => 'https://graph.facebook.com')
end
get '/auth/facebook' do
redirect client.web_server.authorize_url(
:redirect_uri => redirect_uri,
:scope => 'email,offline_access'
)
end
get '/auth/facebook/callback' do
access_token = client.web_server.get_access_token(params[:code], :redirect_uri => redirect_uri)
user = JSON.parse(access_token.get('/me'))
user.inspect
end
def redirect_uri
uri = URI.parse(request.url)
uri.path = '/auth/facebook/callback'
uri.query = nil
uri.to_s
end
That's all there is to it! You can use the access token like you would with the OAuth gem, calling HTTP verbs on it etc. You can view more examples on the OAuth2 Wiki.
Because JSON has become the standard format of the OAuth 2.0 specification, the oauth2 gem contains a mode that will perform automatic parsing of JSON response bodies, returning a hash instead of a string. To enable this mode, simply add the :parse_json option to your client initialization:
client = OAuth2::Client.new(
'app_id',
'app_secret',
:site => 'https://example.com',
:parse_json => true,
)
# Obtain an access token using the client
token.get('/some/url.json') #=> {"some" => "hash"}
To use the OAuth2 client for testing error conditions do:
my_client.raise_errors = false
It will then return the error status and response instead of raising an exception.
- Fork the project.
- Create a topic branch.
- Implement your feature or bug fix.
- Add documentation for your feature or bug fix.
- Add specs for your feature or bug fix.
- Run bundle exec rake spec. If your changes are not 100% covered, go back to step 5.
- Commit and push your changes.
- Submit a pull request. Please do not include changes to the gemspec, version, or changelog file. (If you want to create your own version for some reason, please do so in a separate commit.)
Copyright (c) 2011 Intridea, Inc. and Michael Bleigh. See LICENSE for details.