Auth0 vs. Azure Multi-Factor Authentication (Discontinued)

Great for user authentication and access priviledge management. We are using it for both our commercial and financial clients and Auth0 meets all the regulations and due diligence required to close deals with these enterprise customers. Given their tiered pricing structure, we don't see a scenario where Auth0 would not be appropriate for the solution it provides.

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

• RBAC is simple, straight forward and easy to manage
• Integrations of Social Login are simple to configure and the Auth0 documentation shows step by step how to configure it
• Rules/Hooks provide customization to the Auth0 flow, making it a great solution to define how we allow our users to login into our applications

Incentivized

• Ease of use
• Interoperability
• Industry standard

Incentivized

• Price point for ALL features can get a bit pricey. But they have a startup plan which helps big time. Developer plans start at $23/mo and do not include all features.
• Actions, rules, hooks, and email customization are great features, but the UI is a bit tough sometimes, not very responsive to screen size and code editors are cut off in a difficult place to maneuver.

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

The excellent rating I am giving is because this app is more user-friendly for b2b use cases than other apps in providing RBAC for the application the user will consume. The permission always needs to be granular level otherwise incase if something happens then the blast radius would be larger than we think, this auth0 is helpful in keeping the blast radius as small as possible.

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

We went with Auth0 over Okta due to price concerns and the overall simplicity of Auth0. We chose Auth0 over Amazon Cognito because Cognito has very poor documentation and client library support. Auth0 offers a service that hits the sweet spot for organizations with small development teams and limited finances.

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

• SAML SSO is a breeze - this alone saves a lot of dev/support hours.
• We are not worried by hackers and chasing security protocols and standards, I guess about half a day job of a developer.
• Telling customers we can connect them with what ever they have whether its social / SAML / OIDC put us in flexible position

Incentivized

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

Incentivized