warden

In a blog app I want every user to access a form to post a comment. When the user submit the comment form he is redirected to the Devise sign_in form if is not logged in. before_filter :authenticate_user!, :except => [:index, :show, :new] How could I once the user sign_in, redirect him to the comment form and fill all fields ? Thanks in advance If you want to take the user to comment form after every sign in, add in ApplicationController: #after_sign_in_path_for is called by devise def after_sign_in_path_for(resource_or_scope) comment_path... end If you want to take user back to the page they

For my lastest project I'm using https://github.com/hassox/rails_warden . It suits my needs very well except that I can't find a good way to implement remember_me. I know that it's notoriously difficult to get remember_me right from a security point of view so I'm hoping there's a project out there that will do the job. Anyone seen anything or get a good idea? Devise , which is an authentication solution on top of Warden, has a rememberable implementation. Macario Ok here's how I solved it # User model must have remember_token attribute # in config.ru use Rack::Cookies run MyApp # in lib

I'm relatively new to rails. I have Devise set up, and want to run some callback code after users sign in. Looking at the Warden wiki page , I can use the "after_set_user" callback to perform this logic, for example: Warden::Manager.after_set_user do |user, auth, opts| unless user.active? auth.logout throw(:warden, :message => "User not active") end end However, I'm not sure where I should be storing this stuff. My first thought is that I could put it in config/initializers/devise.rb. Is that correct? It doesn't feel right putting what is essentially controller code in the config directory.

How can i prevent the session store from creating a session on JSON/XML calls ? My problem is that i save sessions in a database and it gets flooded on multiple api calls. I'm using Rails 3.2.2 and Devise for authentication. My problem here was with Warden inside Devise. I had to "tell" Warden not to store the user in the session after the user is authenticated. resource = warden.authenticate!(:scope => resource_name, :store => !(request.format.xml? || request.format.json?)) Hope that helps whoever sees this thread. Altonymous resource = warden.authenticate!(:scope => resource_name, :store =>

I am using devise & overriding SessionsController#create to track the login based on a specific condition. The value of session[:session_id] before sign_in(user) is same even after the execution of sign_in(user). I would like to store the new session_id in DB in order to track the user. But unable to access it. How to get it? While looking for it, found that Devise uses set_user method of Warden. But even then, I could not figure out where the session is set in Warden. Shriram Balakrishnan Found the answer in the following question: Rails ActiveRecord store and new session Answer by Benjamin

I'm having an issue with testing my controllers and using Warden. All examples point at stubbing request.env['warden'] . This causes issues in my controllers when I call env['warden'] , which then returns nil . For a crude example, using this: request.env['warden'] = double(Warden, :authenticate => nil, :authenticate! => nil, :authenticated? => false) And a simple before filter like this: before_filter do redirect_to new_user_session_url unless env['warden'].authenticated? end I get a nil . I just managed to get it working using controller.env['warden'] = ... and it works. This makes sense,