We performed a comparison between Auth0, Okta Workforce Identity, and Symantec Siteminder based on real PeerSpot user reviews.
Find out what your peers are saying about Microsoft, Auth0, Okta and others in Access Management."It has a lot of customization and out-of-the-box features."
"It has improved our organization by providing login authentication for a mobile app."
"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)."
"The valuable features are that it is extremely secure and that it's developer-friendly."
"The most valuable feature of the product is scalability."
"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."
"It is easily connected and easy to put our app in single sign-on."
"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 a very scalable solution."
"The support for YubiKey is really good because you don't actually have to type in your username and password."
"The provisioning functionality has been the most valuable. This solution has good performance, fast integration and is very responsive."
"Okta integrates well with other solutions. Once you have integrated an application into Okta and onboarded a user, they will be onboarded for just-in-time provisioning."
"Other than Okta being an easy and awesome integration tool, one of the best features it has is the provisioning and deprovisioning, which makes management way easier. You don't need to be too technical to understand how it works."
"Valuable features include UD, SSO functionality, MFA and Adaptive MFA functionality, ability to link multiple Directory databases with UD."
"It is a very stable solution."
"What I found most valuable in Okta Workforce Identity is that it worked together with VMware Workspace One, so there was this device check at the same time. My company used the trusted device method that enabled you to define that only the trusted devices including the Workspace One agent were able to access the applications directly without an additional authentication step."
"All of our applications get a point, click, and you are in, while we increase security at the same time."
"It is reliable."
"Ease of use is very good, for administrating it. It's very well known."
"Symantec Siteminder Is both scalable and stable."
"It's agent-based. It's convenient to deploy and integrate."
"The most valuable feature is the Federation part of Single Sign On, which is customizable and is easily integrated with any customer application or any third party application."
"We almost never have outages nor see slowdowns."
"As our identity model continues to mature, probably the Federation is most valueable."
"There is a possibility to improve the machine-to-machine authentication flow. This part of Auth0 is not really well documented, and we could really gain some additional knowledge on that."
"The product support for multi-tenancy could be improved."
"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."
"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."
"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."
"This is a costly solution and the price of it should be reduced."
"The error logging could be improved. Okta doesn't provide enough details when you are troubleshooting an issue. It's often difficult to fix it from our end, so we always need additional support from Okta."
"Application updates are lacking. Customer support needs to be improved."
"The solution's user interface needs to be improved and made easy."
"The solution lacks an on-premises deployment model so it can't offer a hybrid solution. It would be ideal if clients had options that weren't just cloud-based."
"Okta Workforce Identity can improve by having more features in governance."
"The product does not offer enough integration capabilities."
"I would appreciate it if Okta Workforce Identity becomes more user-friendly. Its API technology is complicated. Certain applications may pose challenges in terms of integration, especially when they require IDP technologies that aren't easily codable. While I can't provide specific examples, some applications may not integrate with Okta Workforce Identity."
"Support could be a bit faster."
"I think they need to integrate some of the newer types of authentication into the product. I'm not seeing the innovation when it comes to biometrics in the product."
"We would like to the OAuth be more stable, more issues being fixed rather than not."
"The initial setup was complex, painful. But that is to be expected of any new setup. When you're a big bank like us, any kind of migration to a new product is hard. I expect it to be painful, and it was painful. But it's not something that you can avoid."
"The tech support has not been very good for us so we don't use them anymore. We have had some issues. Nobody is perfect."
"The main thing is we do not have the traceability and good monitoring that CA can provide us to capture problems when they occur."
"If the reporting feature can be integrated into SSO itself that will be an icing on the cake."
"All the problems that we reported actually have never been resolved. We could not capture enough information for CA to be able to debug the problem."
"Some of the new protocols, like OAuth 2.0, could be improved."
Earn 20 points
