plataformatec/devise — Issue #1580: Passive authentication
Author: hazah
Created: 2012-01-18 15:16:56+00:00
State: open

Currently Devise provides wrappers for `env['warden'].authenticate!` in both the controller and router. Warden provides an `authenticate` method that is passive. Is there any reason for its exclusion in Devise? It's true that one can use `current_user` to do a passive authentication attempt in the controller action, it seems that `before_filter :current_user` could also work. But then there is nothing that one could do in the router, save for creating a constraints lambda manually.

What are your thoughts on this? Are there any concerns regarding having access to the passive authentication api in warden?