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 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.

Today we use home basic authentication and authorization, and we would like to move away from cloud and use some kind of IDP to improve authentication and authorization for our customers. So, for example, we can use the social logging feature in Auth0 to improve the customer experience.

The price modelling is a bit confusing on the site and can be costly. So if you use one measure like active user format, you need to talk to the support from Auth0 to check the price.

The Management API could be improved so it's easier to get user information.

When they introduced the Organizations feature they did support different login screens per organization. However, they introduced a dependency between this feature and another called the New Universal Login Experience. The New Experience is a more lightweight login screen, but it is much less customizable. For example, today, we are able to fully customize our login screen and even control the background image according to the time of day. We have code to do that. But we are not able to write code anymore in the New Experience.

We really want to take the Organizations feature, but on the other hand, it is coupled with the limitations of the New Experience. That is why we have put the Organizations feature on hold. It is lacking some customization abilities.

There could be an easy integration with IoT devices for the product.

The product could use a more flexible administration structure in the next release. It could be improved by extending the administration model. 

The documentation and getting started guide is excellent for JWT and client-side authentication. However, I think they can do a better job in explaining what you're supposed to do next in order to correctly follow an idiomatic approach to using the solution beyond simply passing a JWT token to a server and having the server check then signature to validate the token.

This is a costly solution and the price of it should be reduced.

The feature improvement I would like to see in Auth0 is around authorization. They can borrow Stormpath's (their primary competitor) notion of groups and organizations built-in on their API. Currently Auth0 takes a different approach, i.e., it uses rules to store authorization-related info on the metadata.

There is a possibility to improve the machine-to-machine authentication flow. This part of Auth0 is not really well documented, and we could really gain some additional knowledge on that.

The tool's price should be improved. 

The product support for multi-tenancy could be improved further, and advanced authorization capabilities could be included in the next release.

In the past, there was an issue with the multi-tenant where there wasn't the ability to manage them. For example, if you have three tenants you couldn't have different managers, but that has been sorted out through the release tool.