Possible Authenticated Constraint for Sorcery

full_constraint.rb

# SCOPE GETS CROSSED - DO NOT USE AS IS!

class AuthenticatedConstraint
  extend Sorcery::Controller::InstanceMethods
  def self.matches?(request)
    Sorcery::Controller::InstanceMethods.send(:define_method, :session, proc{request.session})
    Sorcery::Controller::InstanceMethods.send(:define_method, :request, proc{request})
    logged_in?
  end
end

routes.rb

  constraints(AuthenticatedConstraint) do 
    root :to => 'home#index'
  end

simple_constraint.rb

class AuthenticatedConstraint
  def self.matches?(request)
    !!request.session[:user_id]
  end
end

Ok, maybe I'm dumb, but this doesn't work here :(
Scope gets crossed.

(Updating this thread in case others stumble across it later)

I think either going with a stripped-down version of Devise (which is built atop Warden) is a good option, or just roll your own atop Warden.

I'm about to cross this bridge (needing to share authentication w/a mounted app & needing to constrain routes based on authentication) for an app currently using Sorcery and will like rip it out in favor of the stripped-down Devise.

Here is my solution to using constraints with Sorcery. I really did not want to switch to Devise after investing in Sorcery. NoamB/sorcery#341 (comment)