This is the beginning of a plugin for implementing OAuth Providers in Rails applications.
See the OAuth specs at:
and the OAuth site at:
You need to install the oauth gem (0.2.1) which is the core OAuth ruby library. It will NOT work on any previous version of the gem.
sudo gem install oauth
The Generator currently creates code (in particular views) that only work in Rails 2.
It should not be difficult to manually modify the code to work on Rails 1.2.x
I think the only real issue is that the views have .html.erb extensions. So these could theoretically just be renamed to .rhtml.
Please let me know if this works and I will see if I can make the generator conditionally create .rhtml for pre 2.0 versions of RAILS.
OAuth Provider generator
While it isn't very flexible at the moment there is an oauth_provider generator which you can use like this:
This generates OAuth and OAuth client controllers as well as the required models.
It requires an authentication framework such as acts_as_authenticated, restful_authentication or restful_open_id_authentication. It also requires Rails 2.0.
You need to add the following to your routes (config/routes.rb)
map.resources :oauth_clients map.authorize '/oauth/authorize',:controller=>'oauth',:action=>'authorize' map.request_token '/oauth/request_token',:controller=>'oauth',:action=>'request_token' map.access_token '/oauth/access_token',:controller=>'oauth',:action=>'access_token' map.test_request '/oauth/test_request',:controller=>'oauth',:action=>'test_request'
Add the following lines to your user model:
has_many :client_applications has_many :tokens, :class_name=>"OauthToken",:order=>"authorized_at desc",:include=>[:client_application]
The database is defined in: db/migrate/XXX_create_oauth_tables.rb
Run them as any other normal migration in rails with:
The generator installs a collection of RSpec (rspec.info) specs instead of normal unit_tests. If you don't use RSpec (and really why aren't you?) feel free to remove the spec folder. If you would like to contribute regular unit tests I will accept them with a smile.
Protecting your actions
I recommend that you think about what your users would want to provide access to and limit oauth for those only. For example in a CRUD controller you may think about if you want to let consumer applications do the create, update or delete actions. For your application this might make sense, but for others maybe not.
If you want to give oauth access to everything a registered user can do, just replace the filter you have in your controllers with:
before_filter :login_or_oauth_required If you want to restrict consumers to the index and show methods of your controller do the following:
If you have an action you only want used via oauth:
All of these places the tokens user in current_user as you would expect. It also exposes the following methods:
current_token - for accessing the token used to authorize the current request
current_client_application - for accessing information about which consumer is currently accessing your request
You could add application specific information to the OauthToken and ClientApplication model for such things as object level access control, billing, expiry etc. Be creative and you can create some really cool applications here.
The Google Code project is code.google.com/p/oauth-plugin/
The Mailing List for all things OAuth in Ruby is:
The Mailing list for everything else OAuth is:
The OAuth Ruby Gem home page is oauth.rubyforge.org
Please help documentation, patches and testing.
Copyright © 2007-2008 Pelle Braendgaard, released under the MIT license