Drop-in authentication for Sinatra with Google's OpenID endpoint.

Add this line to your application's Gemfile:

gem 'sinatra-google-auth'

Google has changed their implementation that requires a patch to the ruby-openid gem.

See here for discussion: openid/ruby-openid#51

For now, you have to add:

gem "ruby-openid",
  :git => "git://github.com/kendagriff/ruby-openid.git",
  :ref => "79beaa419d4754e787757f2545331509419e222e"

To your Gemfile if you're getting an OmniAuth Error

And then execute:

$ bundle

Or install it yourself as:

$ gem install sinatra-google-auth

The gem exposes a single authenticate helper that protects the endpoint with Google OpenID authentication.

As of version 0.0.7. you can also use Sinatra::GoogleAuth::Middleware to protect your whole app and/or control where the authentication happens in a middleware chain.

require 'sinatra/base'
require 'sinatra/google-auth'

class App < Sinatra::Base
  register Sinatra::GoogleAuth
  use Sinatra::GoogleAuth::Middleware

  get '*' do
    'hello'
  end
end

require 'sinatra'
require 'sinatra/google-auth'

get '*' do
  authenticate
  'hello'
end

require 'sinatra/base'
require 'sinatra/google-auth'

class App < Sinatra::Base
  register Sinatra::GoogleAuth

  get '*' do
    authenticate
    'hello'
  end
end

Define an on_user method in your app to do something with the user info after authentication.

class App < Sinatra::Base
  register Sinatra::GoogleAuth

  def on_user(info)
    puts info.inspect
  end

  get '*' do
    authenticate
    'hello'
  end
end

Configure your Google OpenID endpoint via setting the ENV var GOOGLE_CLIENT_<ID|SECRET> with key/secret from Google APIs console:

$ export GOOGLE_CLIENT_ID=<id>
$ export GOOGLE_CLIENT_SECRET=<secret>

or before requiring

ENV['GOOGLE_CLIENT_ID'] = '<id>'
ENV['GOOGLE_CLIENT_SECRET'] = '<secret>'

require 'sinatra'
require 'sinatra/google-auth'

Configure your session secret by setting SESSION_SECRET or SECURE_KEY ENV vars.

$ export SESSION_SECRET='super secure secret'

The 'SecureKey' add-on sets the SECURE_KEY variable for you and automatically rotates it.

$ heroku addons:add securekey

1. Fork it
2. Create your feature branch (git checkout -b my-new-feature)
3. Commit your changes (git commit -am 'Added some feature')
4. Push to the branch (git push origin my-new-feature)
5. Create new Pull Request