Auth0 Platform

I use Auth0 Platform  for Identity and Access Management . Additionally, I use it for several different cases for end-users to log in and for internal users to log in. I have used Azure  Business to Consumer as well as Entra ID. However, when a project comes up and I have the choice to work with Auth0 Platform , I really prefer to use Auth0 Platform for logins and for user management.

When comparing Auth0 Platform with Azure , you have to do a lot of things yourself if you want it to work and look and feel in a certain way. With Auth0 Platform, that comes more out of the box. You can see that it is focused on giving this experience to the user but also to the developers. There is a lot possible and there are a lot of features within Auth0 Platform. It is an all-in-one solution for this. The ease of use as a developer is what I appreciate the most.

Regarding how Auth0 Platform secures applications, I have configured Auth0 Platform for logging into apps and also to a mobile app, so several things. I use Auth0 Platform by using OAuth and OpenID Connect. What I especially appreciate is that for single sign-on, it has a lot of options. Everything seems to be there and everything seems to be working. I have not encountered a single sign-on with a third party that did not work or was not compatible. When looking at the applications, most are headless. I have an API and a frontend, a backend and a frontend, and some backends are microservices.

When we started in Europe, there was no European data center. That is there now, which solves a lot of problems that we had then. However, to be more compliant and easier to recommend for customers that are government organizations and do not want anything to do with American companies, that is difficult. The same applies to Azure. Having European data centers helped, but it might not be enough for some. Data and data protection are important things. Even now, it is a pain to back up to an offline location or it is hard to back up everything to your own data center or your own location. That is still a hard thing. I have to build that all myself and I have to use the APIs, and for backing up, I need all the data, so that is a pain. It would be nice to have that out of the box so that I could have an offsite backup that is not in Auth0 Platform Cloud.

Regarding the backup I mentioned before, I was puzzled that there was not something already in place to do this. I found out through their support that I indeed had to build this myself.

I have been using Auth0 Platform for about five or six years. It was a couple of years before Okta bought Auth0 Platform.

Auth0 Platform is perfect. I have had no problems there.

The project with the most customers had maybe 5,000 end-users, and that was never an issue. I am not sure how many were concurrent. For my cases, it is all fine. It is very good overall, but I am not Netflix, so for Netflix, I am not sure.

This was more consultancy support rather than support because there was an issue. It was more helping me understand how I should solve my case. I have not had support because there was an issue. For this consultancy, I had a call with Auth0 Platform here in the Netherlands, or Okta here in the Netherlands. I had a call with two people, and that was very pleasant and clear and good.

I have used Azure B2C, as I mentioned before. Before that, I used the old world approach of doing it myself with OAuth and OpenID Connect, and also on-premise Active Directory. I also used Keycloak.

In my opinion, Auth0 Platform is right in the middle of those options, and that makes it, I am a little biased, but that makes it for me the best solution. With Azure, you have it maybe more out of the box with other products that you are using in Azure, but it has limitations that Auth0 Platform does not. Keycloak is the most not out-of-the-box option, where you have to do a lot of things yourself and configure yourself and host yourself. That is also nice in some cases and can be nicer if you have a case that requires that. However, if not, I would go with Auth0 Platform because it is both managed and it does a lot of things out of the box.

To fully deploy it and have it all working and use infrastructure as code, I think a week would be fair. Now, it would easily be done in a day because I already have all this knowledge.

I was working with a rather large team, so to have the knowledge spread across my team, three people worked on that. However, if you have a small team, it could easily be done by one.

Auth0 Platform does provide return on investment.

I want to back up to an offsite location, so that is something I built. I prefer to do everything with infrastructure as code. When there are new features or new things, I like to go on top of that and update my infrastructure as code with the new features. Things are also changing, so some things might phase out and get replaced by newer features. I then have to do some maintenance, but it is not a lot. With Keycloak, it would be more.

I am not the right person to speak about this in detail. So far, I did not have a case where the pricing was an issue, so I think it is all right. I know that it is cheaper to do in Azure, and I have had discussions in the company with some customers where I thought maybe I should go Azure there. However, in the end, it did not work out that way and I still went with Auth0 Platform. However, I do not have the details.

I give Auth0 Platform a review rating of 8.

My main use case for Auth0 Platform  is as an authentication service for apps that I build.

I have an app that has retail users who require a log in. My app provisions them both in my local database and creates an identity in Auth0 as well. They create their password and use that subsequently every time they want to log in.

Auth0 Platform 's best features include automating the entire login stream in a secure way, providing storage for user credentials, offering a robust password reset facility that users can use by themselves without involving any of my support personnel, and providing a log of all user interactions in terms of logins, logouts, and password resets.

Auth0 Platform positively impacts my organization because, in terms of development work I do, I don't have to spend really any time at all on authentication features or password reset features or anything that Auth0 Platform automates for me.

Auth0 Platform's documentation is excellent, their support organization is excellent, their code is robust, and it's certified as secure.

I have been using Auth0 Platform off and on for about ten years.

Auth0 Platform is stable.

I have had no problems whatsoever with Auth0 Platform's scalability, but I don't really have a large number of users yet.

Auth0 Platform's customer support is excellent.

I rate the customer support a nine on a scale of one to ten.

I did not previously use a different solution.

Auth0 Platform is deployed in my organization by embedding the client SDK in my application, which is deployed to the cloud, allowing users to access my application by connecting to the cloud service and logging in.

Auth0 Platform's pricing, setup cost, and licensing are excellent, and they provide a large free tier that is beneficial to companies with applications just starting to scale their user base.

I evaluated whatever were the range of similar services available at the time before choosing Auth0 Platform, but Auth0 Platform was the best and continues to remain one of the best.

My advice for others looking into using Auth0 Platform is to familiarize themselves with the underlying protocol standards, in this case OAuth. I rate this review ten out of ten.

We have multi-tenant applications. We initially conducted POCs with other providers including Cognito and some open-source providers, as well as Auth0 Platform . We chose Auth0 Platform  because it provides excellent multi-tenant tenancy support, such as creating multiple organizations and having separate users within each organization, which aligned with our application requirements.

Auth0 Platform offers good support and community resources, along with APIs and SDKs. We have Next.js in the frontend and FastAPI in the backend. We used Auth0 Platform SDKs to handle all communication with Auth0 Platform from the frontend. After we receive tokens, we use those tokens in the APIs. From the backend, we use Auth0 Platform public keys to authenticate the token and retrieve user information.

We implemented Auth0 Platform workflow with two-step verification using authorization code with PKCE. Auth0 Platform generates automatic verification codes whenever users log in. This verification code is sent again after receiving authorization codes to obtain the actual token, which is an encrypted token. When we pass this token to APIs, we retrieve published keys to obtain token information and signatures, which are verified before access to backend system APIs is granted. Everything is handled by Auth0 Platform. From a security and compliance perspective, we receive JWT tokens that we verify using the keys, which secures our backends. We have a central gateway where we route APIs, and on the gateway, we have added Auth0 Platform token verification. If verification passes, we allow access to the application layer; otherwise, we deny the request with appropriate codes like 401 or 403.

From a compliance perspective, we did not want to store user IDs and passwords. We used passwordless authentication through email OTP or phone OTP. We also implemented enterprise connections such as Google Workspace  and Microsoft Azure  AD. The organization support feature allows us to define users based on organizations. Passwordless authentication is a particularly good feature when compared with other platforms.

Auth0 Platform offers good support and community resources, along with APIs and SDKs. We used Auth0 Platform SDKs to handle all communication with Auth0 Platform from the frontend. After we receive tokens, we use those tokens in the APIs. From the backend, we use Auth0 Platform public keys to authenticate the token and retrieve user information. The community support was particularly helpful when we encountered obstacles during implementation. We received excellent support from the community when we were stuck. The SDKs provided a plug-and-play experience with minimal changes required to start working with Auth0 Platform from the frontend.

Auth0 Platform is a large company, which results in less flexibility in their applications. We encountered a few issues, and when we consulted the community, they did not have answers. We had to modify our workflow to adjust to their current system.

Pricing is a significant issue we faced. As a small company, we need SSO  login and other login methods. However, accessing SSO  logins requires subscribing to the enterprise plan. Auth0 Platform does not offer basic plans with a few SSO connections that we could try. We must subscribe to a major plan to access most of their features. While this works well for larger companies, for small companies or those conducting POCs, this affects our budget allocation for other initiatives.

Additionally, if we need to serve users in the US, Canada, Europe, and potentially India, we require the ability to keep data in specific countries. Creating multiple Auth0 Platform tenants for data residency requirements is only available in enterprise or higher plans, not in basic plans. Auth0 Platform does not currently have an Indian tenant to serve Indian users. We must use a US or other available tenant and keep Indian user data there. We had a requirement to create an Indian tenant, but since it is not available, we proceeded with a US tenant.

We have been using Auth0 Platform for approximately two years. We received startup credits for one year, and after that program expired, we transitioned to enterprise billing.

We have been using Auth0 Platform for approximately two years. We have not experienced any downtime during this period. Auth0 Platform is already compliant with security and other requirements. We have not encountered any reliability issues, and Auth0 Platform appears reliable for our use case.

Auth0 Platform handles all scaling on their own. We do not need to worry about scaling on their end. We set up our Auth0 Platform tenant, and they handle all logins and scaling. We receive tokens, and how we pass and verify those tokens is what we need to scale from our backend. We can scale our system horizontally. Auth0 Platform is already managed by their team, and we do not need to worry about it. It is a plug-and-play solution.

We spent approximately one or two days setting up the platform. Since then, we have not needed to worry much. Auth0 Platform has been working as expected, and we only need to scale our system. We do not touch Auth0 Platform for day-to-day operations. It is a one-time setup. There might be changes needed based on requirements, but we do not make changes to Auth0 Platform on a day-to-day basis. We do not have to worry about Auth0 Platform operations; we only need to scale our system.

The support team is very good. We faced some issues and raised tickets. Our support team responded immediately and was very responsive. In one instance, a support representative joined a call and explained and resolved the issue. The support team provides immediate support.

We initially conducted POCs with other providers including Cognito and some open-source providers before selecting Auth0 Platform. We chose Auth0 Platform because it provides excellent multi-tenant tenancy support, including creating multiple organizations and having separate users within each organization.

The setup process is straightforward. We used Auth0 Platform SDK and backend support from the community. It required only a few lines of changes to make it work.

We implemented Auth0 Platform workflow with two-step verification using authorization code with PKCE. Auth0 Platform generates automatic verification codes whenever users log in. The verification code is sent again after receiving authorization codes to obtain the actual token, which is an encrypted token. When we pass this token to APIs, we retrieve published keys to obtain token information and signatures, which are verified before we gain access to backend system APIs.

Auth0 Platform is a famous identity provider. When we onboard clients and they ask about our tech stack and security approach, and we mention that we use Auth0 Platform for their login flow, they are already familiar with it. We do not have to explain much about it. This is beneficial when we onboard clients and explain our architecture because they recognize that Auth0 Platform is a large platform with compliance and security measures in place. This represents a good investment.

We used AWS  to host the backend system.

We evaluated one open-source tool and AWS  Cognito before selecting Auth0 Platform.

If companies have a good budget, they should definitely use Auth0 Platform. However, for small companies with limited budgets, Auth0 Platform's basic plan has limited features, so budget considerations are important. If companies are comfortable with their budget, there are no other issues. For larger companies, Auth0 Platform is a good choice to move forward with.

We spent approximately one or two days setting up the platform. Since then, we have not needed to worry much. Auth0 Platform has been working as expected, and we only need to scale our system. We are satisfied with the solution and do not touch Auth0 Platform for day-to-day operations. It is a one-time setup. There might be changes needed based on requirements, but we do not make changes to Auth0 Platform on a day-to-day basis. We do not have to worry about Auth0 Platform operations; we only need to scale our system. Our overall rating for this solution is 8 out of 10.