Devise vs sso: What are the differences?
Developers describe Devise as "Flexible authentication solution for Rails with Warden". Devise is a flexible authentication solution for Rails based on Warden. On the other hand, sso is detailed as "Buzzfeed's single-sign-on authentication proxy". The authentication and authorization system BuzzFeed developed to provide a secure, single sign-on experience for access to the many internal web apps used by our employees.
Devise and sso belong to "User Management and Authentication" category of the tech stack.
Devise and sso are both open source tools. It seems that Devise with 20K GitHub stars and 4.76K forks on GitHub has more adoption than sso with 2.11K GitHub stars and 109 GitHub forks.
What is Devise?
What is sso?
Need advice about which tool to choose?Ask the StackShare community!
Why do developers choose sso?
What are the cons of using Devise?
What are the cons of using sso?
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with sso?
We use OmniAuth with Devise to authenticate users via Twitter, GitHub, Bitbucket and Gitlab. Adding a new OmniAuth authentication provider is basically as easy as adding a new Ruby gem!
The only drawback I could see is that your OmniAuth+Devise
OmniauthCallbacksController redirection logic can easily get hairy over time. So you have to be vigilant to keep it in check.
Devise handles user registration with low effort. Also is configurable in so many levels, from custom views to create-your-own controllers.
4 years of experience using Devise for User management, authentication, and authorization.