-
Notifications
You must be signed in to change notification settings - Fork 1.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Cannot use this gem alongside Devise #192
Comments
@robypez can you post more of the error call stack? Also, have you tried using |
I try also with scope. Here is the full stack
|
Looks like this line is broken. You're using the 0.1.32.beta8 version, in which this may be a bug. I'm using version 0.1.29 successfully side by side with devise 3.2.4 in my Rails 4.1.8 app. Maybe specify a non-beta version and try again? |
Using 1.30 I have another problem:
|
Looks like you don't have the omniauth gem installed... is it in the Gemfile? Did you do |
@milesmatthias I want to use it without omniauth. I followed the instructions to disable it |
I can add another info: using 1.30 with omniauth gem it works |
I think @lynndylanhurley might have some comments here. Personally, it seems like an overreach of this gem to require omniauth, but maybe there's some other thinking there. |
Yes, I think is a bug. |
@lynndylanhurley @milesmatthias another info. My routes.rb
|
Thanks guys, I think this is a bug. I'll look into the problem tonight. |
@lynndylanhurley thank you. If you need test or support I'm here! 👍 |
@lynndylanhurley for you info I cloned the gem in local and I comment the line where you clear the scope:
Now rake routes works but of course the result is:
As you can see here I have the double namespace. PS: is there a way to have just login routes (no registration, update, etc). |
The problem is Rails 4.1: Scope.new works only in Rails 4.2. Using Rails 4.1 and Devise Token Auth 1.30 is not possible to delete unused routes.
doesn't work. |
been awhile - still broken on latest master 8a6ba64 |
I'm having the same issue with Rails 4.1.1 and devise_token_auth 0.1.37 |
I am also experiencing this issue on Rails 4.1.8 and devise_token_auth 0.1.37. I updated from 0.1.30 to fix the bcrypt error then got this error.
|
Using rails -> 4.8.1 and the latest version of device_token_auth, I've also this error when running
With the following:
|
@aliceclv I got the same error when running rake db:migrate. Did you fix yours? |
@BecomingSam I've given up using the gem and followed a tutorial to implement the API authentication system myself: you can find it here |
@aliceclv Thanks for the link. I'll do the same. |
Has this been ever resolved? |
@aliceclv for the amount of effort in "roll your own" wouldn't it be possible to fix and pull request? |
same issue =( |
Hi there @robypez , In an effort to cleanup this project and prioritize a bit, we're marking issues that haven't had any activity in a while with a "close-in-7-days" label. If we don't hear from you in about a week, we'll be closing this issue. Obviously feel free to re-open it at any time if it's the right time or this was done in error! If you are still having the issue (especially if it's a bug report) please refer to our new Issue Template to provide some more details to help us solve it. Hope all is well. |
Hello. I cannot find a way to use this gem.
I'm working on a Ionic app and I need Angular authentication. I don't need Omniauth, mail and password login. Very simple.
I follow every step in the installation. I have a working Rails 4.1 app with Device installed and I'm using the beta 8 of Devise_token_auth.
I modify the migration file because I need only a couple of fields:
In my user.rb I have
In my api base controller I have
In my routes I have
The result is
A brief question: how can I secure only update, post and delete method in my api?
The text was updated successfully, but these errors were encountered: