hassox/warden — Issue #35: Warden.authenticate! is losing instance variable
Author: pdindak
Created: 2011-11-19 00:24:37+00:00
State: open

Using Warden/Devise with Rails 2.3.8

Previously used Devise database_authenticable without any problems. Current_user is always there from the Warden.authenticate! call.

Switched to using ldap_authentication. Warden authenticate! is returning empty strings, which when used by Devise as @current_user, loses the user from the first index page of the app.

I am stepping thru the ruby debugger and can see this happening.

I realize that the ldap strategy with Devise does the actual authentication. I do not see why Warden should think it is empty, when I can see it with breakpoints and analysis in the ldap strategy code that returns the resource.

I have posted earlier findings on the Devise group, but it seemed correct to ask here with what I am seeing with Warden.