A Heroku OAuth middleware with no other work to do
Latest commit 54eafd7 Aug 7, 2017 @wuputah wuputah 0.8.0


Build Status Dependency Status

Heroku Bouncer

Heroku Bouncer is a Rack middleware (implemented in Sinatra) that requires Heroku OAuth on all requests.

Ruby and Rack compatibility

  • Ruby: Versions >= 0.8.0 require Ruby >= 2.2. If you need a version that works with prior versions of Ruby, please use version ~> 0.7.1. Note, however, that 0.7.1 does not support Rack 2 (Rails 5).

  • Rack: Rack 1 and 2 are supported.


heroku-bouncer-demo is a Sinatra app that uses heroku-bouncer.


  1. Install the Heroku OAuth CLI plugin.

    heroku plugins:install heroku-cli-oauth
  2. Create your OAuth client using /auth/heroku/callback as your callback endpoint. Use http://localhost:5000/auth/heroku/callback for local development with Foreman.

    heroku clients:create localhost http://localhost:5000/auth/heroku/callback
    heroku clients:create myapp https://myapp.herokuapp.com/auth/heroku/callback

    See https://github.com/heroku/heroku-cli-oauth#clients for more details.

  3. Configure the middleware as follows:


    Heroku::Bouncer requires a session middleware to be mounted above it. Pure Rack apps will need to add such a middleware if they don't already have one. In config.ru:

    require 'rack/session/cookie'
    require 'heroku/bouncer'
    require 'my_app'
    # use `openssl rand -base64 32` to generate a secret
    use Rack::Session::Cookie, secret: "...", key: "my_app_session"
    use Heroku::Bouncer,
      oauth: { id: "...", secret: "..." }, secret: "..."
    run MyApp


    Heroku::Bouncer can be run like a Rack app, but since a Sinatra app can mount Rack middleware, it may be easier to mount it inside the app and use Sinatra's session.

    class MyApp < Sinatra::Base
      enable :sessions, secret: "...", key: "my_app_session"
      use ::Heroku::Bouncer,
        oauth: { id: "...", secret: "..." }, secret: "..."


    Add a middleware configuration line to config/application.rb:

    config.middleware.use ::Heroku::Bouncer,
      oauth: { id: "...", secret: "..." }, secret: "..."
  4. Fill in the required settings :oauth and :secret as explained below.


Two settings are required:

  • oauth: Your OAuth credentials as a hash - :id and :secret.
  • secret: A random string used as an encryption secret used to secure the user information in the session.

Using environment variables for these is recommended, for example:

use Heroku::Bouncer,
  oauth: { id: ENV['HEROKU_OAUTH_ID'], secret: ENV['HEROKU_OAUTH_SECRET'] },

Here are the supported options you can pass to the middleware:

  • oauth[:scope]: The OAuth scope to use when requesting the OAuth token. Default: identity.
  • allow_if: A lambda that takes an email address. If the lambda evaluates to true, allow the user through. If false, redirects to redirect_url. By default, all users are allowed through after authenticating.
  • allow_if_user: A lambda that takes the account resource representing the user. If the lambda evaluates to true, allow the user through. If false, redirects to redirect_url. By default, all users are allowed through after authenticating.
  • redirect_url: Where unauthorized users are redirected to. Defaults to www.heroku.com.
  • expose_token: Expose the OAuth token in the session, allowing you to make API calls as the user. Default: false
  • expose_email: Expose the user's email address in the session. Default: true
  • expose_user: Expose the user attributes in the session. Default: true
  • session_sync_nonce: If present, determines the name of a cookie shared across properties under a same domain in order to keep their sessions synchronized. Default: nil
  • allow_anonymous: Accepts a lambda that gets called with each request. If the lambda evals to true, the request will not enforce authentication (e.g: allow_anonymous: lambda { |req| !/\A\/admin/.match(req.fullpath) } will allow anonymous requests except those with under the /admin path). Default: nil, which does not allow anonymous access to any URL.
  • skip: Accepts a lambda that gets called with each request's env. If the lambda gets evaluated to true, heroku-bouncer's middleware will be completely skipped. Default: 'false', which applies heroku-bouncer to all requests.

You use these by passing a hash to the use call, for example:

use Heroku::Bouncer,
  oauth: { id: "...", secret: "...", scope: "global" },
  secret: "...",
  expose_token: true

How to get the data

Based on your choice of the expose options above, the middleware adds the following keys to your request environment:

  • bouncer.token
  • bouncer.refresh_token
  • bouncer.email
  • bouncer.user

You can access this in Sinatra and Rails by request.env[key], e.g. request.env['bouncer.token'].

Using the Heroku API

If you set expose_token to true, you'll get an API token that you can use to make Heroku API calls on behalf of the logged-in user using heroku.rb .

heroku = Heroku::API.new(:api_key => request.env["bouncer.token"])
apps = heroku.get_apps.body

Keep in mind that this adds substantial security risk to your application.

The API token is short-lived, and expires 8 hours after issue. Heroku provides a separate refresh_token (available as bouncer.refresh_token) that can be used to fetch fresh API tokens if necessary. See the token refresh documentation for details.

Logging out

Send users to /auth/sso-logout if logging out of Heroku is appropriate, or /auth/logout if you only wish to logout of your app. The latter will redirect to /, which may result is the user being logging in again.

Security Model: A Tale of Three Secrets

There are three secrets in use:

  • A OAuth secret. Paired with the OAuth ID, this is how the Heroku authorizes your OAuth requests with your particular OAuth client.
  • A bouncer secret. Bouncer encrypts and signs all user data placed in the session. This ensures such data cannot be viewed by anyone but the application.
  • A session secret. This is used to sign the session, which validates the session was generated by your application. Strictly speaking, however, this is outside of Bouncer and is not a part of its security model.

In totality, Heroku Bouncer ensures session data can only be generated and read by your application. However, they do not protect against replay attacks if the data is obtained in its entirety. SSL and session timeouts should be used to help mitigate this risk. CSRF tokens for any actions that modify data are also recommended.