We have user management, role management, and tenant concepts for multi-tenant applications. We use organizations in Auth0. For Okta, we mostly use it for internal SSO to provision users to internal tools.
External reviews
External reviews are not included in the AWS star rating for the product.
Integrates well with other tools and services, scales well and maintenance is managed by AuthO
What is our primary use case?
How has it helped my organization?
What is most valuable?
Auth0’s multifactor authentication enhances our security posture. They are GDPR compliant, and they provide us with a way to host in multiple regions. We use a European region to be GDPR compliant.
For performance, we can also choose different regions, like China or North America. They are also HIPAA compliant, but we don’t deal with HIPAA. They are ISO certified, so it’s easy for us to convince our security team. They manage key rotation and things like that on their end in the backend, which helps us.
What needs improvement?
Auth0 doesn’t have a great way of providing self-managed user management tools. If I have to provision my customers to manage their tenants, they don’t do it out of the box.
We are wrapping a solution around it to make that happen. There are some marketplace plugins available, but they are not so great. We have developed our own custom solution to expose user management to our customers.
For how long have I used the solution?
I have been using it for around seven years. I use the latest version.
What do I think about the scalability of the solution?
It’s highly scalable. We just have to pay more for more users.
How are customer service and support?
For enterprise, I would rate technical support a nine out of ten.
For any kind of lower starter package, I would rate the technical support somewhere around six out of ten.
So, on an average it is an eight out of ten.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
Within our organization, we use only Okta. We have hooked it up to Active Directory. That’s our single sign-on here.
Okta is mostly provisioned and used through DevOps. Role management and user grouping are mostly easy. There are directional integrations as well, including Azure AD and other tools. We get out-of-the-box solutions to integrate with actionable tools that we are using.
It's straight out of the box. So, the deployment time is almost half an hour to an hour in our case.
It will probably take one day to integrate. We also use IAC for automation. Once that is done, we mostly forget about it.
We have to do user management, like provisioning the users, de-provisioning, when they leave the organization and so on.
How was the initial setup?
It’s easy to integrate and deploy.
We use the cloud solution. We don’t deploy anything. We use the cloud solution, and we have automated the configuration. That is the deployment that goes on. Like, if we are adding a new tenant and things like that, it all happens through infrastructure as code.
The general deployment and integration took us around one day. Probably one day because we requested it from the DevOps team, and they have to get in touch with someone from the tooling side, and they get it done. So we usually hear back within a day that it’s done.
The point is that we did all the heavy lifting in the initial days. After that, we hardly notice anything. It’s all working well together. The only thing is that we have to wrap up a solution for user management. Other than that, I don’t see any issues.
We don't do the maintenance. It's Auth0 that manages the maintenance. We don’t usually do anything. They have great availability SLAs. We don’t even notice if there are any updates and things like that.
What was our ROI?
It’s definitely beneficial. If we had to develop our own and manage it, it would take years of development and maintenance. In those terms, it’s definitely beneficial.
But once you cross that barrier of being a startup and growing, and if you have to move to an enterprise solution, that’s where it becomes expensive. But at that point, I think you’ll be okay to pay anyway.
What's my experience with pricing, setup cost, and licensing?
The pricing depends on the tier you are in. If you’re in enterprise support, there’s always someone who can support you. But if you’re in lower tiers or starter tiers, we have crossed that barrier anyway.
In the initial days, if you’re not aware of how the OpenID solutions work, it’s probably hard to get started. Once you cross that barrier, it becomes easy.
But you have to pay extra for technical support, which makes sense, but adoption might become harder for people who might not have experience with either Auth0 or Okta before.
What other advice do I have?
As a developer, I would rate it at nine out of ten. That’s because it’s very flexible. Developers can easily learn the system and get used to developing on it, like configuring automation, configuring integration, and things like that.
But, again, it’s for developers. You should know how the API integrations work and things like that. But if you are a user in general, I think I would rate it at six or seven, probably seven, because if you’re not a developer, you need to spend time exploring more.
Also, the scoped user management for a specific customer is not available out of the box with Auth0. So that’s something which, if you are a product manager, you would definitely look at. But if you’re a developer, that’s just an opportunity to build something on top of that.
Which deployment model are you using for this solution?
Good for easy social login integration
Terrible Customer Support
* System is clunky with poor UI for developing a customised login screen
Auth0 is a proven entity
Simple and Easy to use UI
Top-tier authentication solution
The support solution through email and extensive documentation has been very helpful to configure things to our needs.
The reliability of Auth0 are impressive providing high uptime and seamless feature activation such as multi-factor authentication to single sign-on .
Integration with existing systems and customizing authentication flows is easy and seamless boosting the day to day productivity of developments. Auth0 provides the flexibility needed to meet diverse business needs within the company and accross apps.
Has good documentation but improvement is needed in MFA and application configurations
What needs improvement?
There are indeed areas where the product could improve. For instance, Okta offers various application configurations, enabling access management, which the tool could consider implementing. Additionally, it lacks a third-party application for provisioning, a feature that Okta provides.
The tool's MFA is not as good as Microsoft Authenticator or Okta. It relies on email-based MFA, where it sends a code for verification. However, it lacks mobile apps for MFA like Microsoft Authenticator or Okta's mobile client.
What do I think about the scalability of the solution?
It is very scalable because it provides a new environment for companies based on their number of users and other factors. The tool can take a lot of users.
How are customer service and support?
I haven't used the tool's technical support yet, but it has good documentation and an online community for support.
How was the initial setup?
The solution's deployment is easy.
What's my experience with pricing, setup cost, and licensing?
The tool is cheaper compared to competing solutions. Those alternatives tended to be more expensive. Consequently, Okta purchased it because it was considerably cheaper. The solution even offered some free services while still providing excellent functionality.
However, I'm unsure about the current pricing structure since Okta acquired it. Okta aims to make money, and it has faced security issues in the past.
What other advice do I have?
The tool's universal login feature impacted user experience mostly in the social login aspect. This includes accessing platforms like Facebook or WhatsApp using a Gmail account, which has become standard and is no longer seen as rocket science. When you log in, the company generates an SSO token, often from Azure AD. I rate the overall solution a seven out of ten.
A cloud solution to build log-in and sign-up experiences with ease of use
What is our primary use case?
Developers use the solution to build log-in and sign-up experiences. Auth0 provides an API key that is integrated with the code. We provide sign-in and sign-up instead of making our sign-up, sign-in, invite-user, and forgot-password. We buy Auth0 and integrate it; they run it on their cloud.
What is most valuable?
The solution offers simplicity of use. They have too much enterprise onboarding when you want a B2B login. The first quick start is the easiest thing. You have too many tutorials and YouTube guides to help you integrate it with your code.
What needs improvement?
It is expensive and not friendly to small developers. On the other hand, Clerk is user-friendly for smaller companies.
Auth0 could become more easier. B2B organizations need to catch up with the price. Multi-tenancy needs to be less expensive, and the ease of use and onboarding must also be better. Three tenants are allowed for every account. They have to improve their organizational features.
For how long have I used the solution?
I have been using Auth0 for one year. We are using the cloud version of the solution.
What do I think about the stability of the solution?
The product’s stability is fine.
I rate the solution’s stability a nine out of ten.
What do I think about the scalability of the solution?
Our clients' products have close to 200-250 active users. It is charged based on the number of active users. It has more significant customers like Jira.
I rate the solution's scalability a nine out of ten.
How are customer service and support?
Customer service used to be very responsive. Now, the community support is helping us for a long time. Whatever you are looking for, you will get it in the community support forum. Auth0 has community forums, help documentation, and Q&A. The user community of Auth0 is very supportive when you need help. The dedicated support forum is overwhelmed. It's becoming harder to reach someone unless you have a bigger account.
How would you rate customer service and support?
Neutral
Which solution did I use previously and why did I switch?
We have used Keycloak for a very long time.
How was the initial setup?
Auth0 has an SDK that calls their servers. We have to install the SDK in our codebase, and our developers must integrate it with our sign-in and sign-up pages. It takes the least amount of time compared to alternatives. It is well-documented and is the best solution in the market.
What's my experience with pricing, setup cost, and licensing?
The product is expensive.
I rate the product’s pricing a seven out of ten, where one is cheap and ten is expensive.
Which other solutions did I evaluate?
We are evaluating SuperTokens and Lock. If Auth0 becomes expensive, we can host another solution.
What other advice do I have?
It is a good product if you are a B2C or B2B solution or any app or consumer product.
Overall, I rate the solution an eight out of ten.
Which deployment model are you using for this solution?
Auth0 employs hostile/predatory pricing tactics
Fairly straight forward and good product overall.
- Easy to use but also very customizable once you get familiar with the platform
- Great documentation and examples
- Pricing has increased dramatically since being aquired by Okta
- Rigid pricing structure