Tree @debian/3.0.0-1 (Download .tar.gz)
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 39 40 41 42 43 44 45 46 47 48 49 50 51 52 53 54 55 56 57 58 59 60 61 62 63 64 65 66 67 68 69 70 71 72 73 74 75 76 77 78 79 80 81 82 83 84 85 86 87 88 89 90 91 92 93 94 95 96 97 98 99 100 101 102 103 104 105 106 107 108 109 110 111 112 113 114 115 116 117 118 119 120 121 122 123 124 125 126 127 128 129 130 131 132 133 134 135 136 137 138 139 140 141 142 143 144 145 146 147 148 149 150 151 152 153 154 155 156 157 158 159 160 161 162 163 164 165 166 167 168 169 170 171 172 173 174 175 176 177 178 179 180 181 | **IMPORTANT: If you're running < 1.5.1, please upgrade to the latest version to address 3 security vulnerabilities. More details [here](https://github.com/mkdynamic/omniauth-facebook/wiki/CSRF-vulnerability:-CVE-2013-4562), [here](https://github.com/mkdynamic/omniauth-facebook/wiki/Access-token-vulnerability:-CVE-2013-4593) and [here](http://web.nvd.nist.gov/view/vuln/detail?vulnId=CVE-2012-6134).** --- # OmniAuth Facebook [![Build Status](https://secure.travis-ci.org/mkdynamic/omniauth-facebook.svg?branch=master)](https://travis-ci.org/mkdynamic/omniauth-facebook) [![Gem Version](https://img.shields.io/gem/v/omniauth-facebook.svg)](https://rubygems.org/gems/omniauth-facebook) **These notes are based on master, please see tags for README pertaining to specific releases.** Facebook OAuth2 Strategy for OmniAuth. Supports the OAuth 2.0 server-side and client-side flows. Read the Facebook docs for more details: http://developers.facebook.com/docs/authentication ## Installing Add to your `Gemfile`: ```ruby gem 'omniauth-facebook' ``` Then `bundle install`. ## Usage `OmniAuth::Strategies::Facebook` is simply a Rack middleware. Read the OmniAuth docs for detailed instructions: https://github.com/intridea/omniauth. Here's a quick example, adding the middleware to a Rails app in `config/initializers/omniauth.rb`: ```ruby Rails.application.config.middleware.use OmniAuth::Builder do provider :facebook, ENV['FACEBOOK_KEY'], ENV['FACEBOOK_SECRET'] end ``` [See the example Sinatra app for full examples](https://github.com/mkdynamic/omniauth-facebook/blob/master/example/config.ru) of both the server and client-side flows (including using the Facebook Javascript SDK). ## Configuring You can configure several options, which you pass in to the `provider` method via a `Hash`: Option name | Default | Explanation --- | --- | --- `scope` | `email` | A comma-separated list of permissions you want to request from the user. See the Facebook docs for a full list of available permissions: https://developers.facebook.com/docs/reference/login/ `display` | `page` | The display context to show the authentication page. Options are: `page`, `popup` and `touch`. Read the Facebook docs for more details: https://developers.facebook.com/docs/reference/dialogs/oauth/ `image_size` | `square` | Set the size for the returned image url in the auth hash. Valid options include `square` (50x50), `small` (50 pixels wide, variable height), `normal` (100 pixels wide, variable height), or `large` (about 200 pixels wide, variable height). Additionally, you can request a picture of a specific size by setting this option to a hash with `:width` and `:height` as keys. This will return an available profile picture closest to the requested size and requested aspect ratio. If only `:width` or `:height` is specified, we will return a picture whose width or height is closest to the requested size, respectively. `info_fields` | 'name,email' | Specify exactly which fields should be returned when getting the user's info. Value should be a comma-separated string as per https://developers.facebook.com/docs/graph-api/reference/user/ (only `/me` endpoint). `locale` | | Specify locale which should be used when getting the user's info. Value should be locale string as per https://developers.facebook.com/docs/reference/api/locale/. `auth_type` | | Optionally specifies the requested authentication features as a comma-separated list, as per https://developers.facebook.com/docs/facebook-login/reauthentication/. Valid values are `https` (checks for the presence of the secure cookie and asks for re-authentication if it is not present), and `reauthenticate` (asks the user to re-authenticate unconditionally). Use 'rerequest' when you want to request premissions. Default is `nil`. `secure_image_url` | `false` | Set to `true` to use https for the avatar image url returned in the auth hash. `callback_url` / `callback_path` | | Specify a custom callback URL used during the server-side flow. Note this must be allowed by your app configuration on Facebook (see 'Valid OAuth redirect URIs' under the 'Advanced' settings section in the configuration for your Facebook app for more details). For example, to request `email`, `user_birthday` and `read_stream` permissions and display the authentication page in a popup window: ```ruby Rails.application.config.middleware.use OmniAuth::Builder do provider :facebook, ENV['FACEBOOK_KEY'], ENV['FACEBOOK_SECRET'], :scope => 'email,user_birthday,read_stream', :display => 'popup' end ``` ### API Version OmniAuth Facebook uses unversioned API endpoints by default. You can configure custom endpoints via `client_options` hash passed to `provider`. ```ruby use OmniAuth::Builder do provider :facebook, ENV['APP_ID'], ENV['APP_SECRET'], :client_options => { :site => 'https://graph.facebook.com/v2.0', :authorize_url => "https://www.facebook.com/v2.0/dialog/oauth" } end ``` ### Per-Request Options If you want to set the `display` format, `auth_type`, or `scope` on a per-request basis, you can just pass it to the OmniAuth request phase URL, for example: `/auth/facebook?display=popup` or `/auth/facebook?scope=email`. ## Auth Hash Here's an example *Auth Hash* available in `request.env['omniauth.auth']`: ```ruby { :provider => 'facebook', :uid => '1234567', :info => { :nickname => 'jbloggs', :email => 'joe@bloggs.com', :name => 'Joe Bloggs', :first_name => 'Joe', :last_name => 'Bloggs', :image => 'http://graph.facebook.com/1234567/picture?type=square', :urls => { :Facebook => 'http://www.facebook.com/jbloggs' }, :location => 'Palo Alto, California', :verified => true }, :credentials => { :token => 'ABCDEF...', # OAuth 2.0 access_token, which you may wish to store :expires_at => 1321747205, # when the access token expires (it always will) :expires => true # this will always be true }, :extra => { :raw_info => { :id => '1234567', :name => 'Joe Bloggs', :first_name => 'Joe', :last_name => 'Bloggs', :link => 'http://www.facebook.com/jbloggs', :username => 'jbloggs', :location => { :id => '123456789', :name => 'Palo Alto, California' }, :gender => 'male', :email => 'joe@bloggs.com', :timezone => -8, :locale => 'en_US', :verified => true, :updated_time => '2011-11-11T06:21:03+0000' } } } ``` The precise information available may depend on the permissions which you request. ## Client-side Flow with Facebook Javascript SDK You can use the Facebook Javascript SDK with `FB.login`, and just hit the callback endpoint (`/auth/facebook/callback` by default) once the user has authenticated in the success callback. **Note that you must enable cookies in the `FB.init` config for this process to work.** See the example Sinatra app under `example/` and read the [Facebook docs on Login for JavaScript](https://developers.facebook.com/docs/facebook-login/login-flow-for-web/) for more details. ### How it Works The client-side flow is supported by parsing the authorization code from the signed request which Facebook places in a cookie. When you call `/auth/facebook/callback` in the success callback of `FB.login` that will pass the cookie back to the server. omniauth-facebook will see this cookie and: 1. parse it, 2. extract the authorization code contained in it 3. and hit Facebook and obtain an access token which will get placed in the `request.env['omniauth.auth']['credentials']` hash. ## Token Expiry The expiration time of the access token you obtain will depend on which flow you are using. ### Client-Side Flow If you use the client-side flow, Facebook will give you back a short lived access token (~ 2 hours). You can exchange this short lived access token for a longer lived version. Read the [Facebook docs](https://developers.facebook.com/docs/facebook-login/access-tokens/) for more information on exchanging a short lived token for a long lived token. ### Server-Side Flow If you use the server-side flow, Facebook will give you back a longer lived access token (~ 60 days). ## Supported Rubies Actively tested with the following Ruby versions: - MRI 2.1.0 - MRI 2.0.0 - MRI 1.9.3 - MRI 1.9.2 - MRI 1.8.7 - JRuby 1.7.9 - Rubinius (latest stable) ## License Copyright (c) 2012 by Mark Dodwell 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. [![Bitdeli Badge](https://d2weczhvl823v0.cloudfront.net/mkdynamic/omniauth-facebook/trend.png)](https://bitdeli.com/free "Bitdeli Badge") |
Commit History @debian/3.0.0-1
0
»»
- Preparing changelog Nitesh A Jain 9 years ago
- Removed stub_request_scheme.patch Nitesh A Jain 9 years ago
- Preparing changelog Nitesh A Jain 9 years ago
- Refreshed patch Nitesh A Jain 9 years ago
- Merge tag 'upstream/2.0.0' Nitesh A Jain 9 years ago
- Imported Upstream version 2.0.0 Nitesh A Jain 9 years ago
- prepare changelog Cédric Boutillier 9 years ago
- Add stub_request_scheme.patch to stub Request#scheme method and avoid test failures (Closes: #747740) Cédric Boutillier 9 years ago
- Simplify debian/ruby-tests.rb to require the unique test file test/test.rb Cédric Boutillier 9 years ago
- correct description and dependencies Praveen Arimbrathodiyil 9 years ago
- updated long description Nitesh A Jain 9 years ago
- changed target to unstable Nitesh A Jain 10 years ago
- changed to upstream version to 1.6.0 in d/changelog Nitesh A Jain 10 years ago
- updated standards version and build depends Nitesh A Jain 10 years ago
- updated removing_bundler patch Nitesh A Jain 10 years ago
- Imported Upstream version 1.6.0 Nitesh A Jain 10 years ago
- Merge tag 'upstream/1.6.0' Nitesh A Jain 10 years ago
- corrected the upstream name Nitesh A Jain 10 years ago
- removing ruby-test-files Nitesh A Jain 10 years ago
- removed bundler Nitesh A Jain 10 years ago
- updated control Nitesh A Jain 10 years ago
- installing readme Nitesh A Jain 10 years ago
- enabled Vcs browser and git fields Nitesh A Jain 10 years ago
- updated changelog and copyright Nitesh A Jain 10 years ago
- added ruby-test.rb Nitesh A Jain 10 years ago
- debian/copyright: use DEP5 copyright-format/1.0 official URL for Format field Cédric Boutillier 10 years ago
- use canonical URI in Vcs-* fields Cédric Boutillier 10 years ago
- debian/control: remove obsolete DM-Upload-Allowed flag Cédric Boutillier 10 years ago
- Imported Upstream version 1.4.1 Nitesh A Jain 10 years ago
- Imported Debian patch 1.4.1-1 Nitesh A Jain 10 years ago
0
»»