Auth0 Reviews

Auth0 is used as an identity provider for our new SaaS platform to manage the identity of users.

Auth0 is cost-effective because it provides all the features we need, and it was very easy to integrate into our platform. The documentation is comprehensive, and their support team is highly helpful.

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.

We use the solution for API security and management. We implement our solution with almost ten to fifteen vendors' APIs, like Salesforce and HubSpot. 

It involves generating leads, invites, adding contacts, and opportunities, mostly challenging with Salesforce integration due to limited documentation.

The solution is cost-effective and beneficial in terms of security. It enhances secure API requests, improving user management efficiency.

We use the tool for Single Sign-On (SSO) feature.

Auth0, being deployed on the cloud, provides all the functionality in a single place. We don't need to maintain machines, inventory, or procurement. It has a lot of customization and out-of-the-box features as well. We can quickly plug it into products like Active Directory or other identity broker solutions.

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.

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.

We are building a software as a service platform of products, and we wanted our customers to be able to have the same seamless experience in terms of how they log into our products. We wanted it to be secure, and we didn't want to use our own development resources in building our own solution. We wanted something that is secure and ready at the beginning of our development so that we have a very short time to market. We wanted it to be a very extensible solution and building something on our own wasn't an option for us. We wanted something that was already there. We also wanted a company that is highly committed to delivering state-of-the-art solutions for identity management.

It is deployed in the cloud. This is a software as a service. So, our workloads work in the cloud. We are mostly using AWS, but we also have Azure and GCP. We are a multi-cloud company.

I was able to pass the ISO audit smoothly. When they asked me for identity management, I just told them that it is Auth0, and it was passed. So, it has helped with compliance.

We are using Auth0 Rules during the authentication process to contact our internal APIs and extend the token that Auth0 generates with additional information that comes from our database. Auth0 Rules are pretty important because by using Auth0 Rules, we are able to shorten the development time. We didn't need to do any workarounds and so on. We could quickly deploy some code into Auth0, and our use case was covered in less than one day. We are also using Actions, which is the new thing that came after Rules and Hooks.

It provides the flexibility and the customizability that we need. I did a webinar on Auth0 in AWS, and I said that we know that the software-as-a-service products are not designed to cover 100% of use cases. They are just trying to solve 90% of them, but with Auth0's Rules engine, Actions engine, and many different features, I am able to code something around Auth0. So, I can bend the existing functionality exactly for my use case. For me, this extensibility of the software or the software as a service model is very important because then I know that I won't face any roadblocks that I cannot really go around.

It allows us to tailor the user experience flow. We find the user experience with Auth0 really great, and we could customize it exactly as per our needs. The new features that they released during the last year since we have signed the contract have been helpful. The additional hosted login page that splits the authentication into two different steps and the Auth0 organization features are really great for us.

It has saved us the development time and money by not having to deal with authentication or identity management. It has shortened the development time and saved a lot of money for us. We did a case study on Auth0, and we had a 300% return on investment in terms of money. We have also reduced the development time by about two months. We also don't need people dedicated to our own solution, which is an ongoing process of saving money.

It has helped us in setting up authentication without having to hire additional staff. We were able to do that with our own resources. We don't need to have a dedicated team that is working only on identity management.

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.

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.