Auth0 vs. Azure Multi-Factor Authentication (Discontinued)

Auth0 is very well suited for situations where a JSON web token can be used for authorizing APIs, websites, and mobile devices. It's especially useful if the JWT validation can happen at a gateway layer. It's especially useful if you only need to verify the user's email address or mobile number as the passwordless login is easy to implement.

Incentivized

If your solution falls within their standard use case or you have Office 365 - then it makes total sense. If you need a lot of customization or have a really specific business process that causes you to deviate from the standard flow it usually makes more sense to create a custom solution

Incentivized

• Overall we had very good experience with Auth0. It supports industry standard language or technology for integration. Very good performance.
• It's nice to work with Auth0's APIs and they are flexible.
• The management and configuration dashboard is useful and easy to deal with.

Incentivized

• Ease of use
• Interoperability
• Industry standard

Incentivized

• Auth0 can be somewhat limiting if you want a lot of control over the design of your authentication flow. Custom branding can be done, but it may be limited depending on how you plan to integrate.
• The Auth0 API documentation has proven confusing at times; a single API endpoint's behaviour will change based on inputs and configured settings (e.g. offline_access). Consequently fields that are advertised as being returned in a response might not be there or have different values if you miss a key detail and it can be difficult to debug when this happens. All information required is available in the documentation but requires some digging.
• The toggle to switch tenants feels a bit odd, it works, but I've had a few instances where I didn't realize I was on a staging tenant looking for something that was on the production tenant. Not a big deal, just something to watch out for.

Incentivized

• It can be difficult to work with when deviating off the standard use cases

Incentivized

For our purposes, Auth0 is still one of the best valued RBAC platforms in the market.

Incentivized

- integration and ease of implementation - great over all product support specially for passkey biometric authentication -Auth0 is very reliable to use their API integration for security
verification. It provides best API to integrate our website and application
with Single Sign In option and two step verification option. Sales and technical teams are always there to provide support

Incentivized

There isn't a clear method to get a hold of support when trouble arises if you're on their standard plan. You can file a support ticket and they generally are responsive. I've often been able to find similar questions to the questions I've had when it comes to support in their ticket history, however, some have been closed without a satisfactory conclusion for the original poster.

Incentivized

Auth0 is non-evasive and does not require software download. It is user friendly, seamless, and doesn't require additional actions on the part of the user. IBM Trusteer is none of these things and is based on a technology stack that cannot scale in the same way as Auth0. We believe Auth0 provides a superior solution and is well suited for our own technology stack.

Incentivized

Honestly, they are very similar as is much of their offerings. It really comes down to which ecosystem are you already invested in? It doesn't make a lot of sense to try and interop with every cloud vendor - pick one and use them. While there used to be substantial differences in the cloud platforms, they are at basic parity now

Incentivized

• Development time has been allocated to the more core parts of our business.
• We are confident in the security of our user's accounts and their data.
• Auth0's login flows are customizable which means that we don't have to worry about users being confused when logging in/changing their passwords, and we didn't event have to spend that much time configuring this. (Full in-house development for login could take weeks to get right.)

Incentivized

• Overall, it's a really good value compared to building a custom solution that you have to maintain

Incentivized