All Projects → jamiew → omniauth-youtube

jamiew / omniauth-youtube

Licence: other
OmniAuth 1.0 strategy for connecting to YouTube

Programming Languages

ruby
36898 projects - #4 most used programming language

OmniAuth YouTube

NOTE: THIS GEM IS DEPRECATED IN FAVOR OF google_oauth2

google_oauth2 configuration for YouTube

This gem no longer works. Try omniauth-google-oauth2 instead:

config.omniauth :google_oauth2,KEY,SECRET, { access_type: "offline", approval_prompt: "force", name: "youtube" }

For more discussion, see omniauth-youtube issue #7

About (OLD)

This is an OmniAuth 1.0 strategy for authenticating to YouTube.

Get a Google Oauth2.0 API key at their API console

Your key (AKA client_id) looks like "555555555555.apps.googleusercontent.com"; a longer key like "555555555-xxxxyyyzzz" won't work. See this issue for discussion.

An example Rails 3.2 application using omniauth and omniauth-youtube is also available: https://github.com/jamiew/omniauth-rails-app

Usage

In a Rack application:

use OmniAuth::Builder do
  provider :youtube, ENV['YOUTUBE_KEY'], ENV['YOUTUBE_SECRET'], {:access_type => 'online', :approval_prompt => ''}
end

For Rails, put this in config/initializers/omniauth.rb:

Rails.application.config.middleware.use OmniAuth::Builder do
  provider :youtube, ENV['YOUTUBE_KEY'], ENV['YOUTUBE_SECRET'], {:access_type => 'online', :approval_prompt => ''}
end

Restart your server and visit /auth/youtube to try it out

Options

Re. :access_type and :approval_prompt, via omniauth-google-oauth2:

If you don't need a refresh token -- you're only using Google for account creation/auth and don't need Google services -- set the access_type to 'online', vs. 'offline' Also, set the approval prompt to an empty string, since otherwise it will be set to 'force', which makes users manually approve to the Oauth every time they log in. See http://googleappsdeveloper.blogspot.com/2011/10/upcoming-changes-to-oauth-20-endpoint.html

Authors

License

Copyright (c) 2011 Jamie Wilkinson

This source code released under an MIT license.

Note that the project description data, including the texts, logos, images, and/or trademarks, for each open source project belongs to its rightful owner. If you wish to add or remove any projects, please contact us at [email protected].