We performed a comparison between AWS Directory Service and Okta Workforce Identity based on real PeerSpot user reviews.
Find out in this report how the two Identity and Access Management as a Service (IDaaS) (IAMaaS) solutions compare in terms of features, pricing, service and support, easy of deployment, and ROI."AWS Directory Service is secure."
"The most valuable feature is ease of use."
"The support is very good. I would rate the technical support as a nine out of ten."
"We like the fact that it's got such great redundancy."
"Provides good performance and availability."
"The most valuable feature is that because it's all in the cloud, you don't need to manage the infrastructure."
"Two-step authentication is very useful and important."
"AWS has eliminated the downtime we waste when our on-premises resources go down."
"The solution can scale very well."
"We can automate the process of adding users to Okta if they are activated in Active Directory, or if they are added to the database of applications or Active Directory in the last couple of days."
"The initial setup of Okta Workforce Identity is straightforward. I was able to get an environment ready within half a day."
"The product’s most valuable feature is multifactor authentication."
"The provisioning functionality has been the most valuable. This solution has good performance, fast integration and is very responsive."
"It made things a lot easier, especially with passwords."
"We find the solution to be stable."
"The MFA part is the best. MFA provided most of the security that we were looking at with respect to the second level of authentication. Okta Workforce Identity provides a number of options with respect to multifactor authentication, such as the app, phone call, and text. These options provide different ways of logging in for users, and they were a lot more than what we needed. This is certainly a very good feature of Okta Workforce Identity."
"Some of the security protocols are difficult to understand."
"To get CloudWatch to monitor your memory and storage, you have to do some configuration within your server, which sometimes results in errors."
"Our only complaint is that you cannot integrate your Exchange server. Or, if you are planning to install an Exchange server on your Amazon EC2 instance, then you need to configure Active Directory on EC2 instance. We would like for this limitation to be lifted."
"We had a problem with the schema uploading and setting up the directory when we are migrating our users from on-premises to cloud infrastructure."
"AWS Directory Service needs to improve processing."
"The AWS Directory Service should be easier to integrate."
"The solution lacks certain features."
"I would like to grant partial access to a table contained in a database without having to provide full access to the whole database."
"The solution can be quite expensive."
"It's not compatible with on-premises installations, unless you host it as a SaaS. We were not able to do that. For example, imagine a scenario where the cloud is not available. Then, Okta will not work for you. That use case will readily fail because it doesn't have an on-premises installation that you can use to authenticate or provide identity and access management. If you have a purely on-premises solution that is not connected to the internet, then this will not work. This is one area that can be improved."
"UD attribute mapping, Okta group rules, and dynamic usage could use improvement. It also needs more in-depth functionality and features to integrate with RADIUS solutions."
"There should be automated aggregation and complete classification processes included in it."
"Okta Workforce Identity could improve provisioning it can be made simpler."
"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."
"We've not had any problems with Okta."
"It can have more API integrations."
AWS Directory Service is ranked 9th in Identity and Access Management as a Service (IDaaS) (IAMaaS) with 12 reviews while Okta Workforce Identity is ranked 2nd in Identity and Access Management as a Service (IDaaS) (IAMaaS) with 57 reviews. AWS Directory Service is rated 8.6, while Okta Workforce Identity is rated 8.6. The top reviewer of AWS Directory Service writes "Extends AD identity and management capabilities to AWS resources". On the other hand, the top reviewer of Okta Workforce Identity writes "Extremely easy to work with, simple to set up, and reasonably priced ". AWS Directory Service is most compared with Microsoft Entra ID, Microsoft Entra External ID, Google Cloud Identity, SailPoint IdentityIQ and Omada Identity, whereas Okta Workforce Identity is most compared with Microsoft Entra ID, Google Cloud Identity, SailPoint IdentityIQ, Saviynt and Auth0. See our AWS Directory Service vs. Okta Workforce Identity report.
See our list of best Identity and Access Management as a Service (IDaaS) (IAMaaS) vendors.
We monitor all Identity and Access Management as a Service (IDaaS) (IAMaaS) 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.
