Why to setup authentication as Auth0
September 03, 2021

Why to setup authentication as Auth0

Akash Majumder | TrustRadius Reviewer
Score 7 out of 10
Vetted Review
Verified User

Overall Satisfaction with Okta

Basically, previously, we are using Google Firebase for auth and Red Hat LDAP serve. Due to the high resources and private cloud, it's hesitant to configure and make all things work together. After we changed to Auth0, it's was easy to just connect and done. One year back, I have also implemented it in an organization for their user auth services and really to say it worked well.

Pros

  • Fully coded auth service.
  • Just API-connection.
  • Easily deployable and low pricing.

Cons

  • Sometimes it's buggy on the frontend.
  • Uses an AD.
  • GIT Pill secure auth
  • For perfect user auth management.
  • SSO and auth.
Firebase: Pricing is too high and the efficiency and store option is not an ROI point. Okta: Too high pricing. Lack of secure code not good for mobile application auth.

Do you think Auth0 delivers good value for the price?

Yes

Are you happy with Auth0's feature set?

Yes

Did Auth0 live up to sales and marketing promises?

I wasn't involved with the selection/purchase process

Did implementation of Auth0 go as expected?

Yes

Would you buy Auth0 again?

Yes

We can use it as an alternative to all other products like Firebase Auth. Why? Auth0 has its specialty for authentication and is most focused on it so bugs will be reduced by 90% compared to others.
  • Low pricing point
  • Easy to connect
  • Simple UI AND UX
  • Have logs and records like AD

Auth0 Feature Ratings

ID-Management Access Control
6
ID Management Single-Sign On (SSO)
8
Multi-Factor Authentication
7

Configuring Okta

I don't think this is a great word to say about it because it depends on the usage of what you are going to do with it. In my experience, it's great for a quick setup but lack of over configuration which made it slow for work, although everything else works well.

Comments

More Reviews of Auth0