Auth0 is awesome and if you aren't using it (or at least something similar) you should be.
Overall Satisfaction with Okta
Auth0 was implemented as part of a public facing SPA we were building as a trial of a new service.
Unfortunately, the project was paused indefinitely before it could be completed due to a shift of priorities, but the Auth0 implementation was incredibly easy and relieved us of a lot of headache that would come with handling authentication and authorization ourselves.
Their documentation is extensive, detailed, and easy to understand, implementation can be done in hours (for more experienced users, maybe even minutes), and the service is rock-steady stable.
I would never not recommend Auth0 to a friend or colleague setting up a new app or service.
Unfortunately, the project was paused indefinitely before it could be completed due to a shift of priorities, but the Auth0 implementation was incredibly easy and relieved us of a lot of headache that would come with handling authentication and authorization ourselves.
Their documentation is extensive, detailed, and easy to understand, implementation can be done in hours (for more experienced users, maybe even minutes), and the service is rock-steady stable.
I would never not recommend Auth0 to a friend or colleague setting up a new app or service.
Pros
- Implementation is easy
- Extensive documentation for pesky edge cases
- Broad range of features to cover all use cases
Cons
- Explaining why incorporating a 3rd party service for authentication is necessary to less technical users is challenging, especially when discussing additional costs
- Massively reduced dev time
- Significant security boost
- Were the app deployed, there would be additional cost
I found Auth0 to be much more user friendly, and had better documentation for my specific use case, though I have heard good things about Okta as well.
Comments
Please log in to join the conversation