#305 Authentication with Warden pro

Dec 05, 2011 | 12 minutes | Authentication, Rack

Warden makes it easy to move authentication up into Rack middleware. This means authentication can be accessed outside of a Rails controller such as in routes or in a mountable engine.

Click to Play Video ▶

Download:
source codeProject Files in Zip (96.9 KB)
mp4Full Size H.264 Video (22.8 MB)
m4vSmaller H.264 Video (13.1 MB)
webmFull Size VP8 Video (16.8 MB)
ogvFull Size Theora Video (29.3 MB)

Browse Source Code

Resources

          Gemfile
        
gem 'warden'

          config/initializers/warden.rb
        
Rails.application.config.middleware.use Warden::Manager do |manager|
  manager.default_strategies :password
  manager.failure_app = lambda { |env| SessionsController.action(:new).call(env) }
end

Warden::Manager.serialize_into_session do |user|
  user.id
end

Warden::Manager.serialize_from_session do |id|
  User.find(id)
end

Warden::Strategies.add(:password) do
  def valid?
    params['email'] && params['password']
  end
  
  def authenticate!
    user = User.find_by_email(params['email'])
    if user && user.authenticate(params['password'])
      success! user
    else
      fail "Invalid email or password"
    end
  end
end

          application_controller.rb
        
def current_user
  warden.user
end
helper_method :current_user

def warden
  env['warden']
end

          sessions_controller.rb
        
def new
  flash.now.alert = warden.message if warden.message.present?
end

def create
  warden.authenticate!
  redirect_to root_url, notice: "Logged in!"
end

def destroy
  warden.logout
  redirect_to root_url, notice: "Logged out!"
end

          users_controller.rb
        
# after saving user
warden.set_user(@user)

          routes.rb
        
scope constraints: lambda { |r| r.env['warden'].user.nil? } do
  get "signup", to: "users#new", as: "signup"
  get "login", to: "sessions#new", as: "login"
end