TrustRadius Insights for Auth0 are summaries of user sentiment data from TrustRadius reviews and, when necessary, third party data sources.
Business Problems Solved
Auth0, from Okta, has emerged as a versatile solution for secure identity and access management, addressing various business challenges and streamlining authentication processes. Users have successfully implemented Auth0 to enable easy sign-in to work user interfaces, simplifying the login experience and ensuring hassle-free access through features like Auth0 Guardian's button presses or manual code entry. Additionally, Auth0's extensive customization options have allowed users to seamlessly manage user data and integrate with different business directories, facilitating single sign-on across multiple applications. This powerful customization capability has not only enhanced the user experience but also made it easier for businesses to adhere to industry standards and best practices for authentication.
I used Auth0 to integrate social logins and email/password authentication across multiple apps and the API integration was quick and easy and it saved us a lot of development time.
Pros
Auth0 supports biometric authentication and passkeys, which really saves time on multi-factor security setups
their universal login and social login flows made the sign-in experience smooth for users
the documentation is clean and made integration easier without needing to write tons of custom code
Cons
expensive
the free tier felt limited when testing more advanced use cases
Likelihood to Recommend
I would absolutely recommend Auth0 to teams looking for fast, secure login solutions. I’ve even shared it with my friends and social groups, and they’ve also had a good experience.
We use Auth0 for simple and effective user authentication management. Auth0 greatly improves the security of all our web and mobile applications. Even though the pricing can be seemed as tough, the greate customer service and the time saved is worth it. If we were to create our own authentication manager it would take months of development and maintenance.
Pros
Ease of integration with any framework.
Customer support.
Strong security.
Cons
Improved pricing tiers.
Unique user profiles.
Enhanced management API for easier user retrieval.
Likelihood to Recommend
Because of the pricing Auth0 is more geared towards larger and business enterprise web and mobile applications. It is best suited in application where security and user confidentiality is the number one priority. There is no use for it on the open web. I wouldn't recommend for a small project since there are cheaper alternatives in that case.
VU
Verified User
Engineer in Engineering (Computer Software company, 201-500 employees)
We are using Auth0 for 7 years now, looking for a provider to replace our internal login implementation one that keep up with SAML implementations and later on OIDC implementations. This helped our goal of separating authentication from the main platform and forget about security standards updates to keep up with.
Pros
SAML, Social and OIDC connections
Universal login
Availability and Reliability.
Security threats, throttling per user and IP
Cons
User metadata with multiple identities is a mess - first connection set the user attributes while others are set within the identities arrary.
The UI does not keep your filter and you always need to write it again.
Likelihood to Recommend
I don't think there is a use case its not appropriate, it can be used by small mobile app to a huge platform like ours , with proper design for scale and quota considerations, I don't see where it can't fit.
We are using Auth0 in our Organization from last 3 years for ready to use Authentication services. It is very easy to integrate with any type of application. They provide complete security with their services. Customer support is also very responsive. It save lot of time and provide multiple option for Auth service integration.
Pros
Ready to use Auth0 Services
Easy to integrate
Multiple Options
Cons
Price is on higher side.
Likelihood to Recommend
It saves lots of time. It also provide Standard security which save lots of time and make application very secure without extra effort.
We use Auth0 in our organisation for our daily SSO purposes. It is basically used for signing in to our multiple platforms based on our roles in the company. The platform availability is based on our roles and permissions are given by the IT support team. So the first thing we have a touch base with every morning is Auth0
Pros
Single sign on
Multiple factor authentication
Secure sign in
Usable platform
Cons
Sometimes logging in takes a bit longer
The refresh happens sometimes out of no where, very rare but happens
The Okta verify app can be improved, based on UI interactions I have this opinion
Likelihood to Recommend
Well suited - in a security oriented organisation like ours, also for big to medium scale organisations is well and good. Suitable for every situation where signing on once and more focus on work is a priority
not suitable- very rare can’t say, but only for small scale firms due to its pricing but overall too good
VU
Verified User
Engineer in Engineering (Computer Networking company, 1001-5000 employees)
We use Auth0 for providing multi-tenant SaaS service to our customers. We use it primarily for authorizations and for integration into an organization's IdP.
Pros
Integrations
Authentication
Authorization
Cons
Finish thoughts on features
Confusing and obsolete messaging
Reliability of the offering
Likelihood to Recommend
Reliability of the service has been a big challenge as well as [the] evolution of the features. For enterprises both of these are important. A few other things like automation and tooling are nascent or non-existent
VU
Verified User
Executive in Engineering (Computer Software company, 51-200 employees)
In our company we start using Auth0 in the mobile development team to manage authentication. Then, due to good feedback from developers, we decided to adopt it on quite all of our projects
Pros
Signup
Signin
Database integrations
Cons
Easier mobile SDK integration with custom fields
More databases integration
Faster web UI
Likelihood to Recommend
Perfect for big and articulated project, too complex for small and fast project
We are using Auth0 to authenticate end-users with apps that we develop. By using Auth0 as our Identity Provider (IdP) and login/logout solution, we minimize the scope of work required for an application development project that requires authentication. This in turn reduces the amount of time required to come up with prototypes, demos to prospective customers, and eventual time to market. In addition, for some apps that require us to manually provision accounts, having a user database built-in is a big plus.
Pros
User database and management
Hosted login and logout
SDKs for almost every framework
Many tutorials and guides
Cons
More in-depth guides for other frameworks like Svelte
More competitive pricing (eg. vs AWS Cognito, Azure AD B2C)
Pricing details beyond 10K MAUs
Likelihood to Recommend
Auth0 shines when one needs a simple auth solution, particularly for beginners building SPAs, as well as for those building apps on more obscure frameworks like Cordova or Nativescript. Pricing premium is acceptable when a low number of MAUs are expected. Pricing however does not scale well, as other providers like AWS Cognito and Azure AD B2C have priced an order of magnitude cheaper and much more generous free tiers. Essentially the trade-off is developer experience vs cost.
VU
Verified User
Engineer in Engineering (Computer Software company, 1-10 employees)
Auth0 is used by a department to authenticate the users who use our platform, we also authorize the users using the app metadata that Auth0 has. We currently have three applications that use Auth0 for the same purpose. Also, we implemented it in one of our backend services to decrypt the JWT token.
Pros
Authenticate
Personalize login
Create rules
Cons
Roles
Usages of user metadata
Likelihood to Recommend
Well, I find it quite difficult to find documentation or example in real life applications. I remember that the examples for react are quite simple so when we implemented on a production application, we had to make some changes that we didn't consider.