4 ms·
I will stick with OmniAuth as I want to use one of the existing auth libraries (devise/authlogic). I don't think integrating OmniAuth is difficult enough to war
by boundlessdreamz 16y ago
I will stick with OmniAuth as I want to use one of the existing auth libraries (devise/authlogic). I don't think integrating OmniAuth is difficult enough to warrant another gem.
With devise,you get so much more functionality and also allow you to offer a native login/password if you so desire.
- knuckle_cake 16y agoWe married OmniAuth with Authlogic to handle username/password (we're still on Rails 2, so no Devise for us). It wasn't too bad. Handling the validations for users was the tricky part, but Authlogic offers a ton of help in this area... way more than I expected.
- pibefision 16y agoI stick with devise too, but I don't understand why the oauth2 functionalty it is not on the master gem. You need to import it from github to have this.
- cullenking 16y agoUgh, I just tried devise and tossed it out within an hour. Way too much automagic, way too difficult to use it in any way but their scaffold. Still looking for a clean way to do facebook/twitter stuff however, so I'll checkout omnisocial and omniauth.
- dmix 16y agoThere's no need to use a complex plugin to provide logins with Facebook/Twitter. Use the oauth2 gem and write it by hand. My FacebookAuth controller is only 20 lines of code and it works perfectly. I've set up fb/twitter logins in 4 different apps and have tried all the gems/plugins.
- cullenking 16y agoThanks for the tip :)