Need advice about which tool to choose?Ask the StackShare community!
Auth0 vs OAuth.io: What are the differences?
What is Auth0? Token-based Single Sign On for your Apps and APIs with social, databases and enterprise identities. A set of unified APIs and tools that instantly enables Single Sign On and user management to all your applications.
What is OAuth.io? OAuth That Just Works. OAuth is a protocol that aimed to provide a single secure recipe to manage authorizations. It is now used by almost every web application. However, 30+ different implementations coexist. OAuth.io fixes this massive problem by acting as a universal adapter, thanks to a robust API. With OAuth.io integrating OAuth takes minutes instead of hours or days.
Auth0 and OAuth.io belong to "User Management and Authentication" category of the tech stack.
Some of the features offered by Auth0 are:
- User and Password support with verification and forgot password email workflow
- Painless SAML Auth with Enterprises
- Integration with 20+ Social Providers
On the other hand, OAuth.io provides the following key features:
- Quickly integrate API providers
- More than 100 providers available
- Secured encrypted API
"JSON web token" is the top reason why over 47 developers like Auth0, while over 3 developers mention "SDK's" as the leading cause for choosing OAuth.io.
Hey all, We're currently weighing up the pros & cons of using Firebase Authentication vs something more OTB like Auth0 or Okta to manage end-user access management for a consumer digital content product. From what I understand so far, Something like Firebase Auth would require more dev effort but is likely to cost less overall, whereas OTB, you have a UI-based console which makes config by non-technical business users easier to manage. Does anyone else have any intuitions or experiences they could share on this, please? Thank you!
Hey, we've had implemented Firebase auth in less than two days. Their doc is amazing and I don't understand why you think that it will take more effort than Auth0. Prices are really good (free, except if you use more than 10k/sms month).
We need to migrate our authentication system to an external solution. We have a Vue.js frontend and a set of Services (mostly in Python) that talk to each other through APIs. This platform is multitenant, having all tenants in the same DB (MongoDB) and discriminating between them with a parameter value. So I'll be grateful if someone can share their experiences with any of these three options!
If these three are your options, I would recommend going with Auth0. They have all functionality available as developer API (Okta e.g. not) so you can manage your instance with Infrastructure as code and can also easily add functionalities relatively easily with the API. They are also really powerful if we're talking about ABAC (Attribute based access control). You can also enrich your access token with custom claims from your MongoDB, that can be probably really useful, as you said that you're dealing with multi tenancy.
We're using Auth0 in combination with Fauna Fauna is a database, so it would challenge you're mongodb. But Faunadb is the first database that implemented a full end user ABAC system directly in the database. (And also a lot easier than the ABAC systems from Okta or Auth0). This helps us, to use Auth0 only as identity platform and doing all the authorization with enriched claims over Fauna. With that you can skip in a lot of the cases you're backend, and you can request directly from the frontend your database (Blazing fast). Also, you can replace in some years Auth0 a lot easier with some upcoming cheaper (Auth0 was bought by Okta for a hilarious price) and "easy to use" passwordless identity provider like Passage.id
Currently, Passport.js repo has 324 open issues, and Jared (the original author) seems to be the one doing most of the work. Also, given that the documentation is not proper. Is it worth using Passport.js?
As of now, StackShare shows it has 29 companies using it. How do you implement auth in your project or your company? Are there any good alternatives to Passport.js? Should I implement auth from scratch?
I would recommend Auth0 only if you are willing to shell out money. You can keep up with their free version only for a very limited time and as per our experience as a growing startup where budget is an issue, their support was not very helpful as they first asked us to sign a commercial agreement even before helping us t o find out whether Auth0 fits our use case or not! But otherwise Auth0 is a great platform to speed up authentication. In our case we had to move to alternatives like Casbin for multi-tenant authorization!
Using Auth0 and JWT with a simple session management server is easy and takes care of a lot of the hassle of setting up authentication. We feel safe having Auth0 handle and store our user data knowing their databases are way more secure than anything we could have setup ourselves. They also provide great tools like WebHooks and action events to pull critical metadata to our API when we need it.
I started our team on Amazon Cognito because I was a Solutions Architect at AWS and found it really easy to follow the tutorials and get a basic app up and running with it.
When our team started working with it, they very quickly became frustrated because of the poor documentation. After 4 days of trying to get all the basic passwordless auth working, our lead engineer made the decision to abandon it and try Auth0... and managed to get everything implemented in 4 hours.
The consensus was that Cognito just isn't mature enough or well-documented, and that the implementation does not cater for real world use cases the way that it should. I believe Amplify has made some of this simpler, but I would still recommend Auth0 as it's been bulletproof for us, and is a sensible price.
Pros of Auth0
- JSON web token70
- Integration with 20+ Social Providers31
- It's a universal solution20
- Amazing Documentation15
- Heroku Add-on11
- Enterprise support8
- Extend platform with "rules"7
- Great Sample Repos7
- Azure Add-on4
- Easy integration, non-intrusive identity provider3
- It can integrate seamlessly with firebase2
- Great documentation, samples, UX and Angular support2
- On-premise deployment2
- Will sign BAA for HIPAA-compliance1
- Active Directory support1
- SAML Support1
- Great support1
- OpenID Connect (OIDC) Support1
Pros of OAuth.io
- Integration with 100+ Providers3
- Useful screenshots1
- Add your own provider1
- Core oauthd open source1
- Extreme simplicity1
- Heroku add-on1
Sign up to add or upvote prosMake informed product decisions
Cons of Auth0
- Pricing too high (Developer Pro)14
- Poor support7
- Status page not reflect actual status4
- Rapidly changing API3
Cons of OAuth.io
Sign up to add or upvote consMake informed product decisions
What is Auth0?
What is OAuth.io?
Need advice about which tool to choose?Ask the StackShare community!
Sign up to get full access to all the companiesMake informed product decisions
What tools integrate with OAuth.io?
Sign up to get full access to all the tool integrationsMake informed product decisions