We performed a comparison between Auth0 and Okta Customer Identity based on real PeerSpot user reviews.
Find out in this report how the two Customer Identity and Access Management (CIAM) solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."It supports identity federation, FSO and multi-tenancy."
"The valuable features are that it is extremely secure and that it's developer-friendly."
"The most valuable feature is interface application integration, but we haven't fully used it yet. We'll need it in the future for a few potential clients."
"It is very scalable because it provides a new environment for companies based on their number of users and other factors. The tool can take a lot of users."
"It is easily connected and easy to put our app in single sign-on."
"The most important thing for me is compliance. Everything that they have developed in Auth0 is already certified by many regulators such as ISO. So, we do not need to take care of that. We have the shared responsibility model to share assets with other products we are using in the cloud."
"The most valuable feature is that it is simple to integrate, irrespective of your codebase."
"I simply use the JWT from the client on the server side to process requests and push updated profile data to a database/queue as needed and end the process without having to persist data in the web server (sessions)."
"As far as our security team is concerned, the ease of implementing multifactor authentication is definitely the biggest value for our organization."
"There is no password hash saved on the cloud, which is the part that I like the most."
"The most valuable feature of Okta Customer Identity is its SSO because it's very easy to use and it's user-friendly. Even the admin portal of the solution is very user-friendly, and you can walk through it with ease. Okta Customer Identity is not a complicated solution, and even the workflow automation feature is very, very easy to understand."
"We primarily use it to manage the community onboarding and offboarding of users, and it's quite a simple solution for that."
"The end user's ease of use is the most valuable feature."
"I think all the functions of the solution are vital and important because life cycle management is important for some companies. The Single Sign-On feature is fantastic for different customers and advanced server access is really good for access to the servers."
"The solution has great multifactor authentication."
"It is very seamless."
"The product support for multi-tenancy could be improved."
"In the past, there was an issue with the multi-tenant where there wasn't the ability to manage them."
"I think they can do a better job in explaining what you're supposed to do next in order to correctly follow an idiomatic approach to using the solution beyond simply passing a JWT token to a server and having the server check then signature to validate the token."
"The tool's price should be improved."
"When they introduced the Organizations feature they did support different login screens per organization. However, they introduced a dependency between this feature and another called the New Universal Login Experience. The New Experience is a more lightweight login screen, but it is much less customizable. For example, today, we are able to fully customize our login screen and even control the background image according to the time of day. We have code to do that. But we are not able to write code anymore in the New Experience."
"There could be easy integration with IoT devices for the product."
"There are indeed areas where the product could improve. For instance, Okta offers various application configurations, enabling access management, which the tool could consider implementing."
"The price modelling is a bit confusing on the site and can be costly."
"What I'd like to see improved in Okta Customer Identity is the process of exporting users. Currently, it lacks this feature, and you have to use a third-party tool to export users from the group. Exporting users should be very easy, though I did notice that Okta Customer Identity is being upgraded from time to time, and I've been seeing much improvement in it compared to the previous years."
"The product must be provided for free."
"This solution would be improved by adding biometrics features."
"In the future, we'd like to see the product implement more security features, like, for example, zero-trust."
"There is an access request system that is very limited access to the systems available for end-users. The access request should improve in Okta Customer Identity."
"Some limitations in scalability. Each application we work with can be completely different, resulting in highly variable implementation processes."
"All of the governance functionality and privileged account management could be improved."
"I would like to see the provisioning simplified."
Auth0 is ranked 1st in Customer Identity and Access Management (CIAM) with 14 reviews while Okta Customer Identity is ranked 5th in Customer Identity and Access Management (CIAM) with 13 reviews. Auth0 is rated 8.2, while Okta Customer Identity is rated 8.4. The top reviewer of Auth0 writes "Has good documentation but improvement is needed in MFA and application configurations ". On the other hand, the top reviewer of Okta Customer Identity writes "Ability to work with a wide range of applications and security mechanisms". Auth0 is most compared with Microsoft Entra ID, Amazon Cognito, Frontegg, Cloudflare Access and ForgeRock, whereas Okta Customer Identity is most compared with Microsoft Entra Verified ID, ForgeRock, Microsoft Entra External ID and Frontegg. See our Auth0 vs. Okta Customer Identity report.
See our list of best Customer Identity and Access Management (CIAM) vendors.
We monitor all Customer Identity and Access Management (CIAM) reviews to prevent fraudulent reviews and keep review quality high. We do not post reviews by company employees or direct competitors. We validate each review for authenticity via cross-reference with LinkedIn, and personal follow-up with the reviewer when necessary.