External reviews
External reviews are not included in the AWS star rating for the product.
Awesome product
What do you like best about the product?
Super easy to implement on front-end and backend.
What do you dislike about the product?
Some API limitations (pagination, ability to query all users), Auth0 Lock vs Auth0 Hosted login page, Ideally all organisations would prefer customised login screen with their own domain, which is not possible if you want to use Auth0 hosted login page and you are using development account.
What problems is the product solving and how is that benefiting you?
Single sign on, very easy to enable/disable multiple SSO without having to deploy actual software.
- Leave a Comment |
- Mark review as helpful
Very useful
What do you like best about the product?
I like the way we can set up the settings, very easy!
What do you dislike about the product?
Nothing, I like it very much. The way we set up the permissions is amazing.
What problems is the product solving and how is that benefiting you?
We are solving authentication issues and security.
Recommendations to others considering the product:
Get advantage of all the customizations, including the login page aspect.
I appreciated the straigntforwardness of Auth0, but found the documentation iffy.
What do you like best about the product?
I loved the back-end libraries you all provide, especially `auth0/java-jwt`. The library's API was straightforward and to-the-point; it was super easy to get up and running on an existing server. (Also, it's very testable!)
What do you dislike about the product?
The documentation is expansive but unfocused. There were a lot of long-form articles, but it was hard to determine which were applicable to my use case. I would have benefited from a definitive description of the API, but it was tricky to find any documents like that. I'd appreciate if you could make the documentation easier to navigate—a table of contents would do wonders!
Also, I was a little sad that a GUI was the only way to control Auth0's settings—it would be nice if there were some form of plaintext config file we could use. That way, we could manage our Auth0 setup with version control, and put any changes through code review. :-)
Also, I was a little sad that a GUI was the only way to control Auth0's settings—it would be nice if there were some form of plaintext config file we could use. That way, we could manage our Auth0 setup with version control, and put any changes through code review. :-)
What problems is the product solving and how is that benefiting you?
We were a group of undergraduate students working on a class project. This was the first time any of us had dealt with authentication; Auth0 made dealing with identity, if not painless, then at least manageable for a group of first-timers who were out of our depth. Thank you!
Recommendations to others considering the product:
Auth0 provides some example code for how to use their libraries with RxJS; we found these examples to be very buggy. If you're going to use Auth0 with RxJS, I'd recommend writing your own bindings.
Auth0 is very well to deal with identity. A reliable and scalable service.
What do you like best about the product?
I like the API is very intuitive.
And also I like Auth0 reports, it helps me to understand the identity data on a project.
And also I like Auth0 reports, it helps me to understand the identity data on a project.
What do you dislike about the product?
Maybe the performance of react components, I felt it slowly.
What problems is the product solving and how is that benefiting you?
The problems that I solved is to not build things on a database to manage users identification, and integrate socials api for sign in
It's easy to work and provides enough safety
What do you like best about the product?
Dashboard and easy to work, complete and strong.
What do you dislike about the product?
I think search should be easier, as example when you need to find an user, you should select what kind of field you'll search, I think it should show search by any kind of type.
What problems is the product solving and how is that benefiting you?
We're handle our login and we note it's really safe.
Recommendations to others considering the product:
It's usefull and safe, I guess it's a great tool in order to be a company safer.
Great and fast experience
What do you like best about the product?
Very fast to setup my login in my website. A lot of step by step tutorials in a lot of languages. Also the forum was very helpful in some little issue.
What do you dislike about the product?
Nothing. I really recommend using auth0.
What problems is the product solving and how is that benefiting you?
All the login and the password store. Also linking login with other platforms.
I recomended to use Auth0 is a great and easy to implement in my applications
What do you like best about the product?
Is very easy and have many configurations
What do you dislike about the product?
Price, I would like if the price will be less.
What problems is the product solving and how is that benefiting you?
Only for add the authorization
Recommendations to others considering the product:
Is very Easy to implement
Truly frustrating experience with account management and support
What do you like best about the product?
Auth0 seemed like a great option for us as we were a relatively small engineering team that didn't want to build identity resolution internally. We did shop around and it looked like Auth0 was a good choice for us to grow into. It did for the most part deliver on our needs for a couple of years.
What do you dislike about the product?
Their tiering for pricing is very much not aligned with a small-medium sized growing company. No options for bolt ons of needed functionality but without the need for volumes that their enterprise tier is priced for.
In particular, all we wanted was to give our users another option for multifactor authentication (i.e. SMS or email). The software let us do that, but there was a cryptic message that upon reading closer does say you're not supposed to turn that on unless you're enterprise.
What is this? some kind of honey trap? I understand free trials, bolt ons, etc. But particularly for a feature that could have security implications, should you really let your customers wander into using something that you will yank from them?
Trying to work with them to turn this off with as little disruption to our customers as possible has also been full of surprising frustration. The data is in their database about which of our customers use the functionality we want to turn off. However, apparently there's no way they can help us to access that.
It's not data that is exposed in the user export, rather only in the user interface that we're expected to write our own script to 'scrape' user by user.
That's just the technical side of frustration.
The communications from business development managers and account managers has been rude and unhelpful.
I get the 'you get what you pay for argument', maybe our contract isn't that valuable to them, but there's no way I'd recommend paying the enterprise value if this is the type of organization we would be working with.
In particular, all we wanted was to give our users another option for multifactor authentication (i.e. SMS or email). The software let us do that, but there was a cryptic message that upon reading closer does say you're not supposed to turn that on unless you're enterprise.
What is this? some kind of honey trap? I understand free trials, bolt ons, etc. But particularly for a feature that could have security implications, should you really let your customers wander into using something that you will yank from them?
Trying to work with them to turn this off with as little disruption to our customers as possible has also been full of surprising frustration. The data is in their database about which of our customers use the functionality we want to turn off. However, apparently there's no way they can help us to access that.
It's not data that is exposed in the user export, rather only in the user interface that we're expected to write our own script to 'scrape' user by user.
That's just the technical side of frustration.
The communications from business development managers and account managers has been rude and unhelpful.
I get the 'you get what you pay for argument', maybe our contract isn't that valuable to them, but there's no way I'd recommend paying the enterprise value if this is the type of organization we would be working with.
What problems is the product solving and how is that benefiting you?
We've used Auth0 as an identity provider for our B2B application. We've realized the typical benefits you'd expect from an identity provider in authentication flows for users as well as machine to machine.
Recommendations to others considering the product:
Identity providers aren't the type of software you want to be switching very often. I would strongly advise those thinking about using Auth0 to understand that they have a good product for the entry level low price point. However, as your company grows and you want to scale the functionality you use, this is probably going to cause you headaches with Auth0's price tiering.
There are many other providers that are much clearer with their tiering and offer similar if not superior functionality.
There are many other providers that are much clearer with their tiering and offer similar if not superior functionality.
Very easy to set-up
What do you like best about the product?
I like the most the Login Page Customization
What do you dislike about the product?
I don't like that there is no mobile app for the user management
What problems is the product solving and how is that benefiting you?
I am using Auth0 as Identity provider in my KeenBeer application. I don't have to handle with the infrastracture and different protocols implementation
Seamless integration with Auth0 to speed up build time
What do you like best about the product?
It's another item that we don't have to build
What do you dislike about the product?
It's not easy to use the same Auth0 with multiple application with different branding
What problems is the product solving and how is that benefiting you?
Auth service. Need no build independent service on our end
Recommendations to others considering the product:
Think of your needs, and see whether Auth0 fits or not
showing 121 - 130