How to override the Devise::SessionsController (JSON, token auhentication)? about simple_token_authentication HOT 7 CLOSED

Hello @JoshuaNovak919,

Simple Token Authentication was created to work with a vanilla Devise installation, and it doesn't require you to override the Devise::SessionController at all.

If you want an example of how to install it within a Rails app, you can take a look at this Cucumber step definition. The file contains some noise relative to it's usage by Cucumber (e.g. path: '../../' in this Gemfile line), but you'll find there a sequence of commands to generate quickly a token-authentication-enabled Rails app. If you have issues reading it, just tell me and I'll find something better.

Regards

from simple_token_authentication.

@JoshuaNovak919
You were asking about a JSON version of the sessions controller, I'm sorry I skipped that (important) part.

Here is a working JSON sessions controller example to use with SimpleTokenAuthentication. Keep me updated! : )

from simple_token_authentication.

Thanks, that was very helpful. I had to modify it to use request headers for destroy and a few other things, but it was exactly what I needed. Would this work with the current_user helper method though?

from simple_token_authentication.

Great. And yes, current_user is set when users are signed in by token authentication. Simple Token Authentication relies directly on Devise for signing users in, and the Devise sign_in method takes responsibility for setting the current_user.

from simple_token_authentication.

I'm closing this issue and I'll edit a little bit its title to make it easier to find.

from simple_token_authentication.

Hey gonzalo,

Thanks for this snippet. I was wondering how you would set this up in your routes.rb. I have my api routes namespaced:

namespace :api do
   namespace :v1 do
       # this is my json sign in controller from your snippet above
      post "sessions", :controller => :sessions, :action => :create  

      resources :some_entity
   end
end

The error Im getting is:

Devise] Could not find devise mapping for path "/api/v1/sessions".
This may happen for two reasons:

1. You forgot to wrap your route inside the scope block. For example:

devise_scope :user do
get "/some/route" => "some_devise_controller"
end

2. You are testing a Devise controller bypassing the router.
   If so, you can explicitly tell Devise which mapping to use:

   @request.env["devise.mapping"] = Devise.mappings[:user]

I tried wrapping my post session route as they suggest but it still wont work, not really sure what to do about this.

from simple_token_authentication.

@jamespeerless That's a bit off-topic, but maybe this Devise issue and in particular this comment may help you?

from simple_token_authentication.