-
Notifications
You must be signed in to change notification settings - Fork 386
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
Token authentication #70
Comments
Yes, it's been asked for a few times. |
Great to hear. I will keep plugging away with Sorcery then. Look forward to the 0.8.0.0 release! Thanks for your hard work, making mine easier! |
Token authentication would be great for use with mobile app backends and Web Services :) I'll try and look into this over the weekend. Maybe I can submit a pull request! Anyway, +1 from me. |
+1 Would love to see this feature, would really make mobile-development easier :) |
Hi, I was thinking about an API like this: require_login :token_allowed => true, :only => [:json] This way it extends require_login to allow or disallow tokens, and only for I would probably do it in a new submodule. If anyone wants to 'lift the glove', it shouldn't be much trouble On Fri, Mar 30, 2012 at 3:19 PM, Henning M. Stephansen <
|
Actually require_login has all the options of a before filter, so I shouldn't touch 'only'. Maybe another before filter, allows_token_authentication. Not sure. How is it done in other gems? |
Atm I'm building my app in the hope token authentication comes along before I start building my API. Seeing this feature in there would be a massive +100 from me |
+1 Authlogic was a good one for this back in the day although it's methodology may be outdated now, I'm not sure: see Single Access Token module and Session Params module |
I'm thinking this design:
Also the whole thing might be a new submodule and not in the default. |
That design sounds ideal, only side note I'd say is allowing the auth_token to generated on request by the application as well and not just when the password gets touched. |
+1 |
+1 |
1 similar comment
+1 |
Now that sorcery 0.8.0 has been released how do I use this feature? |
I'm curious as to the status of this. Think it's okay to manually implement my own token authentication using authenticate_or_request_with_http_token in my rails-api app in the meantime? |
I am working on an api using sorcery and this is certainly something I'd love to have. |
Hello everybody, hi Noam. I just sent a pull request that adds supports for access tokens in RESTful JSON APIs and extends the external submodule to support OAuth 2.0 For Login (client side flow). I needed this for a pet project that I have been working on my free time, an angularjs app with rails-api as the backend server. I would really appreciate if you guys could test it, code reviews would be great too. Support for mongoid and mongomapper is included, but I don't use mongodb so if you plan to use it please do review the code to make sure everything works correctly. Instructions are in the README. Let me know what you guys think. Regards, |
@ fzagarzazu Awesome! +1 Would be nice with a small demo app on github demonstrating this feature :) Cheers! |
I have just published a quick demo with rails-api and OAuth 2.0 for login. https://github.com/fzagarzazu/sorcery_access_token_demo Hope it helps, regards, |
+1 |
1 similar comment
+1 |
Any update about it?. +1 |
I have plans on this feature, but it will probably be in 1.x release. |
Glad to know that! Thanks for your work. |
This was implemented? |
What's the status of this awesome feature? |
Three years have passed :) I am sure it will be easier to implement app-specific solution |
Is token authentication planned for 1.x release? |
Seems that we should use some custom implementation of tokens :) |
hi excelent work. Thanks I was wondering, if was implemented this feature ? |
@arjayx the gem is transitioning to new maintainers, is this a useful feature for? If a few folks weigh in, it will make it onto the 1.0 roadmap. @Mehonoshin, @volisoft, and @FUT, are you all still using Sorcery? |
@Ch4s3 yep, still using |
@Mehonoshin would JWT/ruby-jwt integration work for you? |
@Ch4s3 I'm no longer using Sorcery |
@Ch4s3 we've implemented some workaround, but anyway jwt looks good for token authentication |
@volisoft, if you don't mind me asking, what are you using now and what features does it provide that sorcery does not? Thanks @Mehonoshin. |
@Ch4s3 I wondered about feature Token for restfull api and be able to implement sorcery in projects that could have mobile clients |
@arjayx interesting, let me look into how people do that |
@Ch4s3 Is there any plan to support this feature? Thanks. |
I think its on the 1.0 agenda. |
Hi Noam. Great work on the Sorcery gem. Is token authentication something that would find it's way into Sorcery on day?
The text was updated successfully, but these errors were encountered: