What is the difference between OmniAuth Identity and Devise?

I studied authentication options for my Rails application. I need to have username and password authentication along with the ability to associate the user with his Facebook, Twitter, Foursquare, etc. identifiers. For this purpose, I usually find people using Devise and OmniAuth. But OmniAuth 1.0 comes with the OmniAuth Identity strategy for username / password. So what is the advantage of using Devise? Could this lead to unnecessary complexity compared to authentication only for Omniauth?

+5
source share
1 answer

With OmniAuth-Identity, you can create a user and authenticate with OmniAuth. OmniAuth-Identity is another provider for authentication, and you cannot link it to other providers like twitter, facebook, etc. This is mentioned at the very end of http://railscasts.com/episodes/304-omniauth-identity .

If you need this link, you should use Devise + OmniAuth (see http://railscasts.com/episodes/235-omniauth-part-1 ).

+4
source

All Articles