omniauth/oa-oauth
Michał Krzyżanowski 729b892c6b fixed thirty_seven_signals strategy 2011-10-20 15:04:48 +02:00
..
autotest Upgrade to RSpec 2.0, add universal options hash for strategies, custom paths, closes #54 2010-11-03 13:19:10 -05:00
lib fixed thirty_seven_signals strategy 2011-10-20 15:04:48 +02:00
spec Merge pull request #501 from chriswarren/0-3-stable 2011-10-14 14:04:37 -07:00
.gemtest Gem dependency refactor 2011-04-22 02:52:52 -05:00
.rspec Made in America. 2011-04-22 02:37:29 -05:00
.yardopts Gem dependency refactor 2011-04-22 02:52:52 -05:00
Gemfile Allow bundling of unreleased versions of sub-gems 2011-06-28 19:17:40 -07:00
LICENSE Update licenses throughout the gems. 2011-01-05 09:53:29 -06:00
README.rdoc Everything can now be initialized with a block instead of arguments. Closes #56 2010-11-29 12:59:20 -06:00
Rakefile Gem dependency refactor 2011-04-22 02:52:52 -05:00
oa-oauth.gemspec Update multi_xml dependency to version 0.4.0 2011-09-15 11:33:35 -07:00

README.rdoc

= OmniAuth::OAuth

OAuth 1.0 and 2.0 strategies for the OmniAuth gem.

== Installation

To get just OAuth functionality:

    gem install oa-oauth
    
For the full auth suite:

    gem install omniauth
    
== Stand-Alone Example

Use the strategy as a middleware in your application:

    require 'omniauth/oauth'
    
    use OmniAuth::Strategies::Twitter, 'consumer_key', 'consumer_secret'
    
Then simply direct users to '/auth/twitter' to have them authenticate via Twitter.

== OmniAuth Builder

If you want to allow multiple providers, use the OmniAuth Builder:

    require 'omniauth/oauth'
    
    use OmniAuth::Builder do
      provider :twitter, 'consumer_key', 'consumer_secret'
      provider :facebook, 'client_id', 'client_secret'
    end