Advanced Usage

Padrino and OmniAuth Overview

This article will show you how to mix our Access Control described here with the beautiful omniauth rack middleware.

The Padrino admin authentication and access control system provides a simple foundation from which you can create your authentication system. Combined with omniauth you can then easily leverage the system to allow authentication through a variety of methods. Read below for more details on how to integrate them.

In this article we’ll cover two topics:

  • 1) Integrating Padrino Admin Authentication into all apps within your project
  • 2) Enabling custom authentication strategies within the authentication system

Before we begin, it is important to note that our integrated authentication based on project-roles can interact easily with other systems. The only files that need to be changed are session.rb and account.rb in order to add your own custom code.

So, let’s start by creating a project using activerecord:

$ padrino g project foo --orm activerecord --tiny
$ cd foo
$ bundle install

Now we need to add a model called Account to act as our persistence model:

$ padrino g model Account name:string email:string role:string uid:string provider:string

Now we need to create and migrate our database:

$ padrino rake ar:create ar:migrate

NOTE: If your migration fails with something like this

Directly inheriting from ActiveRecord::Migration is not supported. Please specify the Rails release the migration was written ...

then you need to update the db/migrate/001_create_account.rb with class CreateAccounts < ActiveRecord::Migration[4.2]

Open your favorite editor and browse and edit Gemfile and add omniauth gem and the providers for twitter and facebook. We also add the haml gem as it's not included by default in the "tiny" padrino template:

# Gemfile
gem 'omniauth'
gem 'omniauth-twitter'
gem 'omniauth-facebook'
gem 'haml'

Now, run bundle install to install dependencies:

$ bundle install

Now we need to add the omniauth middleware. Here you can choose two ways:

  • 1) Add the middleware project-wide (so every subapp can use it)
  • 2) Add the middleware only to the one app that requires it

In our example, we need to edit simply app/app.rb and add:

# app/app.rb
use OmniAuth::Builder do
  provider :twitter,  'consumer_key', 'consumer_secret'
  provider :facebook, 'app_id', 'app_secret'

If you are in a multiapp scenario you need to edit config/boot.rb:

# config/boot.rb
Padrino.use OmniAuth::Builder do
  provider :twitter,  'consumer_key', 'consumer_secret'
  provider :facebook, 'app_id', 'app_secret'

# before the line

To obtain an app_id and secret for Facebook, you need to:

  • Go to the Facebook Developers Page
  • Browse and click create a new app
  • Set your app name and complete the form…
  • One you finish that you are allowed to edit your settings, go to website section
  • Add to site url: http://localhost:3000
  • Add to domain: localhost
  • Write the Application ID and Application Secret to the OmniAuth::Builder

To obtain a consumer_key and consumer_secret for Twitter, you need to:

  • Go to Twitter Applications Page
  • Insert all details and be sure to check Application Type: Browser
  • Set a callback url with a valid domain ex:
  • Save and go to Application Settings and Manage Domains
  • Be sure that you can see your example domain:
  • Authorize domain: localhost
  • Now go to Application Details and save Consumer key and Consumer Secret to the OmniAuth::Builder

NOTE: For domain, it is not important that this path exist because omniauth changes the callback url.

Next, we can integrate our authentication system within in app/app.rb:

# app/app.rb
# at the top after the enable :sessions
register Padrino::Admin::AccessControl

set :login_page, "/" # determines the url login occurs

access_control.roles_for :any do |role|
  role.protect "/profile"
  role.protect "/admin" # here is a demo path

# now we add a role for users
access_control.roles_for :users do |role|
  role.allow "/profile"

And add a couple useful routes, edit app/controllers.rb with:

# app/controllers.rb
get :index do
  haml <<-HAML.gsub(/^ {6}/, '')
    Login with
    =link_to('Facebook', '/auth/facebook')
    =link_to('Twitter',  '/auth/twitter')

get :profile do
  content_type :text

get :destroy do
  redirect url(:index)

get :auth, :map => '/auth/:provider/callback' do
  auth    = request.env["omniauth.auth"]
  account = Account.find_by_provider_and_uid(auth["provider"], auth["uid"]) ||
  redirect "http://" + request.env["HTTP_HOST"] + url(:profile)

We invoked a method Account.create_with_omniauth above, so edit app/models/account.rb and add:

# app/models/account.rb
def self.create_with_omniauth(auth)
  create! do |account|
    account.provider = auth["provider"]
    account.uid      = auth["uid"]    = auth["info"]["name"] if auth["info"]    = auth["info"]["email"] if auth["info"] # we get this only from FB
    account.role     = "users"

That should just about do it! Let’s start the server:

$ padrino start

Browse http://localhost:3000/profile

That will kickoff to the login_page, in our case /.

Now you can login here http://localhost:3000

Follow your login process and then if needed http://localhost:3000/destroy

That is all you need to setup a barebones authentication system in Padrino. This post has gotten you started with a working “Account” and role based authentication solution with integrated omniauth support. From here, obviously there are a number of other features you might want to add on top to flesh out, and that is left for another post or as an exercise to the reader.

last updated: 2022-02-22

comments powered by Disqus