We use it for API authentication, on-premises clusters as well as cluster access, and cloud cluster access.
Senior Director - Principal Architect at a computer software company with 5,001-10,000 employees
Is compatible and interoperable, and easy to implement, learn, and scale
Pros and Cons
- "One of the features that I have found to be very valuable is its interoperability and compatibility with all types of resources, whether it's networking, infrastructure, or applications. That is, it is compatible as well as interoperable, as far as the federated authentication is concerned."
- "If your use case is multi-cloud data centers and hybrid cloud architecture, Okta is a solution to go to."
- "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."
- "It's not compatible with on-premises installations, unless you host it as a SaaS."
What is our primary use case?
How has it helped my organization?
We did not have a unified mechanism for accessing resources or a secure way of accessing resources, and Okta solved that problem for us.
What is most valuable?
One of the features that I have found to be very valuable is its interoperability and compatibility with all types of resources, whether it's networking, infrastructure, or applications. That is, it is compatible as well as interoperable, as far as the federated authentication is concerned.
What needs improvement?
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.
I would also like to see more intelligent analysis of the identity and access management from Okta.
Buyer's Guide
Okta Platform
October 2026
Learn what your peers think about Okta Platform. Get advice and tips from experienced pros sharing their opinions. Updated: October 2026.
921,749 professionals have used our research since 2012.
For how long have I used the solution?
We have been using it for the last seven years.
What do I think about the stability of the solution?
It is fairly stable. However, because it's a SaaS solution, it needs to have connectivity. If the connectivity is down, then Okta Workforce Identity will be down as well.
What do I think about the scalability of the solution?
This is one of the pluses that Okta has. It's easily scalable, both horizontally and vertically.
Right now, we have about 3,500 users.
How are customer service and support?
There was one minor hiccup with technical support, but other than that, the support has been pretty good. I would give them a nine out of ten.
Which solution did I use previously and why did I switch?
We used ForgeRock, and we switched to Okta mainly because of the flexibility that Okta provides.
ForgeRock requires on-premises maintenance. Because most of our applications are now on the cloud, Okta is more user-friendly in that sense.
A couple of years ago, it was 70/30, 70 being on-premises. That's why ForgeRock was the choice. However, it's flipped now to 30/70, and Okta is more useful.
We still use ForgeRock because you can do an on-premises hosting for ForgeRock. Okta doesn't have that capability.
How was the initial setup?
The initial setup is very straightforward; it's a very simple setup. There are some areas for which you need some skills. If you have an SOP, you can just follow it. I would give it a four out of five.
We have three people assigned to the solution for deployment and maintenance.
What about the implementation team?
We deployed it using an in-house team. The initial setup did not take much time; it took about one to three weeks.
What's my experience with pricing, setup cost, and licensing?
Okta has fairly competitive pricing.
Which other solutions did I evaluate?
We evaluated some native cloud services, like AWS and Azure before choosing Okta Workforce Identity.
We also looked at IBM ISAM, IBM Security Access Management, and Oracle ISAM, but they're very rigid products. That's why we went for Okta. They don't have any flexibility, and the cost was also very high compared to that for Okta.
What other advice do I have?
If your use case is multi-cloud data centers and hybrid cloud architecture, Okta is a solution to go to. It's fairly easy to implement as well. It has federated identity and access management, and it works very well with any type of identification authentication. However, if you have on-premises data centers where there are connectivity problems, then it would be better to avoid Okta.
I would rate Okta Workforce Identity at eight on a scale from one to ten because I've found it easy to implement and easy to learn. That is, the onboarding or the learning curve is less. It also has federated identity and access management mechanisms, where you can apply the various resources and workloads that you have. Also, it has very good interoperability and compatibility. It can easily scale too.
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Module lead at a tech vendor with 1,001-5,000 employees
Protects the applications by avoiding cross-site scripting
Pros and Cons
- "You can only log in if you have the access, which protects the applications by avoiding cross-site scripting."
- "The most valuable feature of Okta is its security."
- "Whenever I write Cypress test cases, we encounter problems with logging in through Okta."
- "There is no proper documentation on integrating test cases with Okta, and this issue is troubling whenever I try to implement it."
What is our primary use case?
I have used Okta for security purposes. It grants access only when you have the proper credentials, which I find essential for utilizing new technologies and web applications.
What is most valuable?
The most valuable feature of Okta is its security. You can only log in if you have the access, which protects the applications by avoiding cross-site scripting. Hackers cannot access the system directly. Only after receiving a message from Okta, you can log in, making it highly secure.
What needs improvement?
We are facing one issue with Cypress test cases. Whenever I write Cypress test cases, we encounter problems with logging in through Okta. There is no proper documentation on integrating test cases with Okta, and this issue is troubling whenever I try to implement it.
What do I think about the stability of the solution?
Okta is a stable product.
What do I think about the scalability of the solution?
Currently, scalability is a top priority, but there are no issues with adding many users to Okta.
Which solution did I use previously and why did I switch?
Before Okta, I manually created portals using a username and password stored in a database. Okta introduced a different process.
How was the initial setup?
Initially, it was complicated to set up since I was a beginner and there was no proper documentation. Now that I am more experienced, it is easier to handle.
What other advice do I have?
I need to analyze fully in the future, and if I do not have any concerns, I will share any with you via LinkedIn. As of now, I do not have any additional advice.
I'd rate the solution eight out of ten.
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Other
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Buyer's Guide
Okta Platform
October 2026
Learn what your peers think about Okta Platform. Get advice and tips from experienced pros sharing their opinions. Updated: October 2026.
921,749 professionals have used our research since 2012.
Architect at a tech services company with 1-10 employees
Offers universal directory that offers custom attribute capability and user permissions to read/write on their profiles or hide them
Pros and Cons
- "Okta has introduced the Universal Directory. It has custom attribute capability and user permissions to read/write on their profiles or hide them. Profile sources and identity profile sourcing are two different components that I haven't seen in other products."
- "Okta doesn't have a partial push. It pushes down the full profile schema for lifecycle management or provisioning."
What is our primary use case?
Okta has recently built Okta Identity Engine (OIE). It has a lot more capabilities than the classic engines. The certificate-based system is one thing, and third-party tools like Intune and Jamf for iOS devices. There is a trust relationship between these device management tools, and that contributes to control over the end-user devices.
Scalacity was a company acquired by Okta, and its technology was integrated into Okta's Advanced Server Access (ASA) product.
What is most valuable?
Okta has introduced the Universal Directory. It has custom attribute capability and user permissions to read/write on their profiles or hide them. Profile sources and identity profile sourcing are two different components that I haven't seen in other products.
Okta can import many attributes into the Okta profile and send attributes from the engines. Multiple sources of truths and profile inheritance are done in granular ways. This plays a major role in ABACs going forward.
Okta's MFA features are good. Okta is looking forward with more on the push or less, relying on the Okta Verify factors. It also has extensive capabilities. It's adopting a layer-by-layer upgrade in developing the policies, like MFAs.
Okta has more when it comes to the policy level. It has distinctive features where you can do a mix and combination to have users access applications for various business cases. That's something unique and a selling feature.
What needs improvement?
Okta has a limitation with directory integrations. If you have multiple Active Directory integrations, the user distinguished name (DN) and the manager DN don't get imported properly into the Okta user profile. It has a property of Get AD user's property, but that has limitations when writing an expression language to import changes or updates to user DNs or manager DNs from AD, especially if you have AD master users.
Also, Okta doesn't have a partial push. It pushes down the full profile schema for lifecycle management or provisioning. Even if only one attribute gets updated, even though it is unmapped, it can override other values in the downstream application by nullifying the query. That's the biggest flaw in my experience.
The product releases a lot of brand-new features within the quarterly releases.
For how long have I used the solution?
It's definitely the leading Identity Access Management cloud platform. I have experience with Okta for almost six to eight years now.
I've been an Okta-certified consultant since last year. I got an opportunity to work on the workforce as well as the customer side.
I have experience with more than eight Okta tenants parallelly due to various business cases across my career. Ultimately, this product itself is a pioneer in Identity Access Management.
What do I think about the stability of the solution?
What do I think about the scalability of the solution?
Scalability works very well. I've worked so far with Okta. It's like the heartbeat of that company. If Okta goes down, people are unable to authenticate anywhere. They can't get into applications. So there's a lot of dependency on Okta within the businesses and environments that I've seen so far. It's very critical.
How are customer service and support?
The customer service and support are awesome. They have a CSM assigned for each organization, and they are pretty much responsive to any events that occur. Or if there are any escalations or incidents that impact the business, they're pretty much around in a timely fashion to support the organization.
We have the flexibility with our CSMs to reach them in any manner, email or phone, and they're available most of the time.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
We have long relationships with other vendors for things like Identity Governance and Privileged Access Management. But one thing I've noticed is that Okta has been expanding into wider ranges.
But, there are limits and restrictions to the existing features, which are not fully developed yet. Okta have added a lot of tech in the last couple of years.
What was our ROI?
I'm not a hundred percent sure about the return of interest because it is very much dependent on the size of the organization.
I came from smaller organizations working, like, midscale to, like, large scale. So overall, like, the security breach, like, there are, like, two to three security breaches that have happened, but nothing has been damaged so far for the organization.
So, investing more in Identity access management is a critical investment for any operation as applications are moving to like cloud and SaaS-based. So, there is a dire need to protect the digital identities of enterprise tech employees as well as their customers.
There are a lot of features you can automate. Okta Workflows is a key feature that has a separate pricing than adaptive MFA or SSO. It's a combination, but Okta has features and capabilities to reduce the IT burden. Within my experience, it's been helpful so far with a lot of overhead work that comes with onboarding and offboarding.
What's my experience with pricing, setup cost, and licensing?
The pricing itself is a bit more expensive than the other products in the market so far. Since I know the product is in full demand. But, again, the price texture, features, and everything suits well for small to medium.
But, for larger organizations, it's more expensive than the other platforms. But, usually, licensing is a bit expensive.
What other advice do I have?
I definitely recommend Okta. It has all the features you can utilize to protect any organization's digital entities. Considering a lot of other factors, like cost and the overall features the company wants to use. If you want to use Identity Governance, Identity Access Management, or Privileged Access Management, that's a different story. It's also a different story if you're using other products for different needs.
Overall, I would rate the solution an eight out of ten.
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Architect at a tech services company with 1-10 employees
Good for workforce productivity and customer security and offers MFA features
Pros and Cons
- "Okta has more when it comes to the policy level. It has distinctive features where you can do a mix and combination to have users access applications for various business cases."
- "Okta has a limitation with directory integrations. If you have multiple Active Directory integrations, the user distinguished name (DN) and the manager DN don't get imported properly into the Okta user profile."
What is our primary use case?
It's mostly used for customer-facing applications (Customer Identity Management). API management and self-service flows are the most utilized capabilities. It offers a lot of customization in terms of branding, email notifications, and creating a good end-user experience.
For remote access, we have solutions proposed, like Okta Identity Engine (OIE). It has more capabilities than the classic engines. The certificate-based system is one thing, and third-party tools like Intune and Jamf for iOS devices. There is a trust relationship between these device management tools, and that contributes to control over the end-user devices.
How has it helped my organization?
What is most valuable?
Okta has introduced the Universal Directory. It has custom attribute capability and user permissions to read/write on their profiles or hide them. Profile sources and identity profile sourcing are two different components that I haven't seen in other products.
Okta can import many attributes into the Okta profile and send attributes from the engines. Multiple sources of truths and profile inheritance are done in granular ways. This plays a major role in ABACs going forward.
Okta's MFA features are good. Okta is looking forward with more on the push or less, relying on the Okta Verify factors. But it also has extensive capabilities for Ubiquiti. It's adopting a layer-by-layer upgrade in developing the policies, like MFAs.
Okta has more when it comes to the policy level. It has distinctive features where you can do a mix and combination to have users access applications for various business cases. That's something unique and a selling feature.
For security protocols we use most security protocols, such as OIDC and SAML.
What needs improvement?
Okta has a limitation with directory integrations. If you have multiple Active Directory integrations, the user distinguished name (DN) and the manager DN don't get imported properly into the Okta user profile. It has a property of Get AD user's property, but that has limitations when writing an expression language to import changes or updates to user DNs or manager DNs from AD, especially if you have AD master users.
Also, Okta doesn't have a partial push. It pushes down the full profile schema for lifecycle management or provisioning. Even if only one attribute gets updated, even though it is unmapped, it can override other values in the downstream application by nullifying the query. That's the biggest flaw in my experience.
The product releases a lot of brand-new features within the quarterly releases. There's a feature roadmap for Okta CIM, and most of it is coming in with a lot of users or the customer side.
For how long have I used the solution?
It's definitely the leading Identity Access Management cloud platform. I have experience with Okta for almost six to eight years now.
I've been an Okta-certified consultant since last year. I got an opportunity to work on the workforce as well as the customer side.
I have experience with more than eight Okta tenants parallelly due to various business cases across my career. Ultimately, this product itself is a pioneer in Identity Access Management.
What do I think about the stability of the solution?
It's pretty much stable most of the time, but I have come across a lot more outages recently within Okta.
But, Okta is definitely a very good product.
What do I think about the scalability of the solution?
Scalability works very well. I've worked so far with Okta. It's like the heartbeat of that company. If Okta goes down, people are unable to authenticate anywhere. They can't get into applications. So there's a lot of dependency on Okta within the businesses and environments that I've seen so far. It's very critical.
How are customer service and support?
The customer service and support are awesome. They have a CSM assigned for each organization, and they are pretty much responsive to any events that occur. Or if there are any escalations or incidents that impact the business, they're pretty much around in a timely fashion to support the organization.
We have the flexibility with our CSMs to reach them in any manner, email or phone, and they're available most of the time. Very good.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
We have long relationships with other vendors for things like Identity Governance and Privileged Access Management. But one thing I've noticed is that Okta has been expanding into wider ranges. However, there are limits and restrictions to the existing features, which are not fully developed yet. I think they've added a lot of tech in the last couple of years.
How was the initial setup?
It's always smooth and straightforward to set up, but we can definitely have a bit of complex solutions.
What was our ROI?
I'm not a hundred percent sure about the return of interest because it is very much dependent on the size of the organization.
I came from smaller organizations working, like, midscale to, like, large scale. So overall, like, the security breach, like, there are, like, two to three security reasons that have happened, but nothing has been, like, damage so far for the organization.
So, investing more in Identity access management is a critical investment for any operation as applications are moving to like cloud and SaaS-based. So there is, like, a dire need to protect the digital identities of enterprise tech employees as well as their customers.
There are a lot of features you can automate. Okta Workflows is a key feature that has a separate pricing than adaptive MFA or SSO. It's a combination, but Okta has features and capabilities to reduce the IT burden. Within my experience, it's been helpful so far with a lot of overhead work that comes with onboarding, offboarding.
What's my experience with pricing, setup cost, and licensing?
The pricing model for the Customer Identity product is based on Monthly Unique Users (MUI).
The pricing itself is a bit more expensive than the other products in the market so far. Since I know the product is in full demand. But, again, the price texture, features, and everything suits well for small to medium, for sure.
But, for larger organizations, it's more expensive than the other platforms. But, usually, licensing is a bit expensive.
What other advice do I have?
I definitely recommend Okta.
Every organization needs workforce productivity as well as customer security. The need is definitely there for any enterprise or organization to protect their identity. Customer security also plays the utmost role in protecting customer data.
Overall, I would rate the solution an eight out of ten.
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Solution architect at Infosys
Useful for authorization and other zero-trust authentication
Pros and Cons
- "We can integrate two-factor authentication with the applications."
- "The product must be provided for free."
What is our primary use case?
I use the solution mostly to integrate into Active Directory to get MFA and other IAM features. In Okta, we can get features similar to those in Active Directory. We also use the tool for authorization and other zero-trust authentication.
What is most valuable?
We can integrate two-factor authentication with the applications. Two-factor authentication is used for mobile applications like OneDrive.
What needs improvement?
The product must be provided for free. We cannot substantiate the cost with the features provided by the tool. Microsoft provides similar features for free. I don’t see any extra features in Okta.
For how long have I used the solution?
I have been using the solution for more than five to ten years.
What's my experience with pricing, setup cost, and licensing?
The tool is not free. However, Microsoft is free. So, people prefer Microsoft.
What other advice do I have?
If we wanted to access the Azure portal or any other portal, we used to scan with Authenticator. Once it was approved, we accessed the portals. The product is equivalent to Microsoft’s solution. I used Duo instead of Authenticator to authorize applications. People use Conditional Access Policy. People generally prefer Microsoft because it is free. I will recommend the tool to others. Our recommendations are based on the customer’s requirements, bandwidth, and budget. Overall, I rate the tool an eight out of ten.
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Manager IAM at a computer software company with 11-50 employees
Easy, secure access for your workforce but team access management can be better
Pros and Cons
- "Workforce Identity offers a comprehensive access management solution with multi-factor authentication, total control, and features like app access management, identity governance, and administration tools such as certification and access request management. These are typically found in identity management solutions, but Okta integrates them seamlessly into its user interface."
- "They should focus on improving them to provide top-notch team access management while still offering those typical features."
What is our primary use case?
We have been using this tool for access management. Our client has connected their app's security with Okta Workforce Identity. We have used LinkedIn's libraries to integrate it with various apps, including Oracle and others.
What is most valuable?
Workforce Identity offers a comprehensive access management solution with multi-factor authentication, total control, and features like app access management, identity governance, and administration tools such as certification and access request management. These are typically found in identity management solutions, but Okta integrates them seamlessly into its user interface.
What needs improvement?
They should focus on providing top-notch team access management to companies.
For how long have I used the solution?
I have been working with Okta Workforce Identity for the past 10 months.
What do I think about the stability of the solution?
It has proven to be stable in the time I've used it. If there are any challenges, their support team has been responsive and helpful. Overall, my experience with them has been positive.
What do I think about the scalability of the solution?
It's scalable, but we need to coordinate with Okta's support team or our account manager if we want to increase our workload. Since it's a complete SaaS solution, they can make the necessary adjustments accordingly.
How are customer service and support?
As premium customers, we have the opportunity to schedule calls directly with Okta's expert team members for discussions and support. It's a valuable perk of being a premium user.
How would you rate customer service and support?
Positive
How was the initial setup?
I haven't personally handled the deployment, but I've worked on configuring the printer, which wasn't too complex. As for deployment time and manpower, it's a bit different since Okta Workforce Identity is a cloud-based platform. We don't need dedicated servers as Okta manages integration. We work on our own tenants, and Okta provides preview environments for testing new features. As for maintenance, it's not too difficult, especially for premium customers who can raise support tickets if needed.
What other advice do I have?
I received good support for addressing some bugs, although there were delays in fixing them due to the product backlog and prioritization process at Okta. The resolution time depended on how they prioritized issues, which sometimes caused delays. Overall, I would rate it 7 out of 10.
Disclosure: My company has a business relationship with this vendor other than being a customer. Partner
Java Developer at a consultancy with 10,001+ employees
It's easy to integrate with other solutions
Pros and Cons
- "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."
- "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."
What is our primary use case?
Our organization only uses Okta for single sign-on. Everybody is working from home, so we need a multi-factor authentication solution for remote users. We have around 70,000 users.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
I have worked with Okta for two years.
What do I think about the stability of the solution?
I rate Okta six out of 10 for stability. We don't see many bugs, but the product doesn't support some of our custom requirements. We have to submit feature requests that they implement later.
What do I think about the scalability of the solution?
I rate Okta six out of 10 for scalability. In January, they were doing something on their side, and a cell was down. The US was completely down, and most users had problems logging into. Okta confirmed that auto-scaling was not happening properly from their end.
How are customer service and support?
I rate Okta support eight out of 10.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
The company used RSA before I joined. I believe they switched because they preferred a SaaS platform, and RSA was late to adopt this model. RSA is excellent as an on-prem solution, but they didn't transition to the cloud until later.
How was the initial setup?
I rate Okta eight out of 10 for ease of setup. It's a SaaS product. You can configure it in a few hours. It takes additional time if you use on-prem agents. Active Directory has some other agents that must be integrated. It will take additional time. Otherwise, it won't take much time. You need three people at most to deploy it. Usually, one person deploys the solution, and two other people are on standby.
What other advice do I have?
I rate Okta Workforce Identity eight out of 10.
Which deployment model are you using for this solution?
Public Cloud
Disclosure: My company has a business relationship with this vendor other than being a customer. Partner
Microsoft Azure Engineer at Sycomp
Easy to use, with a user-friendly admin portal; allows efficient provisioning and de-provisioning, and even its workflow automation feature is easy to understand
Pros and Cons
- "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."
- "Okta Customer Identity is a very good technology to work with, with a very knowledgeable support team."
- "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."
- "What I'd like to see improved in Okta Customer Identity is the process of exporting users."
What is our primary use case?
We use Okta Customer Identity mostly for SSO (Single Sign-On), and we also use it for user and application management, in particular, for SaaS applications.
How has it helped my organization?
Okta Customer Identity improved the company when we used it for user identity management because we were able to manage our user provisioning and de-provisioning through the solution very efficiently.
If users are joining the organization or if they're in the onboarding phase, we can take care of the applications and all other requirements through Okta Customer Identity.
When users are leaving the organization or when they're in the off-boarding phase, we use the de-provisioning feature in Okta Customer Identity for those users.
We're very happy with the solution and its features.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
I've been using Okta Customer Identity for three years now.
What do I think about the stability of the solution?
Okta Customer Identity is a stable solution.
What do I think about the scalability of the solution?
Okta Customer Identity is a scalable solution.
How are customer service and support?
Okta Customer Identity has good technical support, and on a scale of one to five, I'm rating support a four.
How was the initial setup?
I would rate the initial setup for Okta Customer Identity as four out of five. Deploying it was very easy.
What about the implementation team?
We deployed Okta Customer Identity with the help of a third party. We deployed the solution and received help from their support team, which was very supportive during deployment. We were able to deploy the whole environment in a very, very easy manner. We just opened a ticket then the Okta support team helped us in setting up the solution.
What was our ROI?
I have no information on Okta Customer Identity ROI.
What's my experience with pricing, setup cost, and licensing?
I'm unfamiliar with the licensing costs of Okta Customer Identity.
Which other solutions did I evaluate?
I evaluated Microsoft Azure AD.
What other advice do I have?
I'm using the latest version of Okta Customer Identity.
My company has a partnership with Okta Customer Identity.
Two thousand people use Okta Customer Identity within the company, mostly engineers. Three people take care of the deployment and maintenance of the solution: one junior engineer, one system engineer, and one architect.
There's a plan to increase the number of users of Okta Customer Identity in the future.
My advice to people looking into implementing the solution is to go ahead and implement it. Okta Customer Identity is a very good technology to work with, with a very knowledgeable support team. You'll get instant support, and the team is very supportive.
My rating for Okta Customer Identity is eight out of ten. I'm not scoring it a ten because of some gaps. It's fine for me right now, but in the future, I would like to see improvements in the solution.
Which deployment model are you using for this solution?
Public Cloud
Disclosure: My company has a business relationship with this vendor other than being a customer. Partner
Principle Product Manager at a tech vendor with 5,001-10,000 employees
Easy to set up, reliable, and offers an easy single sign-on
Pros and Cons
- "It is very seamless."
- "A single sign-on really helps me to make things faster."
- "In the future, we'd like to see the product implement more security features, like, for example, zero-trust."
What is our primary use case?
We are using Okta for authentication. It provides identity. We are using it as an identity provider. Single sign-on is the primary use case here. We use it for our customers and our employees.
What is most valuable?
I'm using it as a single sign-on. Pretty much it is solving my purpose of having to not remember so many passwords.
It is very seamless. You have access to ten different apps, which are hosted on-premise or in the cloud. A single sign-on really helps me to make things faster.
It s easy to set up.
What needs improvement?
The solution works well. I can't speak to any areas of improvement.
In the future, we'd like to see the product implement more security features, like, for example, zero-trust.
For how long have I used the solution?
We've been using the solution for the last three years.
What do I think about the stability of the solution?
The product is very stable. There are no bugs or glitches and it doesn't crash or freeze. it's reliable.
What do I think about the scalability of the solution?
It's a cloud service, so you pay for the license and you will get that level of entitlement. Scaling is never a problem. Just you need to pay for the extra subscription. That's all.
We have 8,000 employees that use the product currently.
It's been used quite regularly, especially during the pandemic when many people had to work from home.
Which solution did I use previously and why did I switch?
I have not used any other solution, although I do know there are many other players in the space.
How was the initial setup?
It's a cloud service. The setup is just a touch of a button. It's very easy for an end-user to use it. For administrators, there might be a few other things they need to carry out, however, for end-users, it's just a touch of a button. Nothing is needed from the installation perspective.
I'd rate the solution four out of five in terms of ease of setup.
What's my experience with pricing, setup cost, and licensing?
I'm not involved in the procurement and I'm not maintaining it, therefore, I am not really sure about the cost.
What other advice do I have?
I'm just a user, just an employee who is using this identity provider, and it is completely managed by our administrators.
I'd recommend the solution to other users.
I would rate the solution eight out of ten.
Which deployment model are you using for this solution?
Hybrid Cloud
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Access Integration Engineer at a manufacturing company with 1,001-5,000 employees
Highly scalable, good support, and useful user management
Pros and Cons
- "The initial setup of Okta Workforce Identity is straightforward. I was able to get an environment ready within half a day."
- "Okta Workforce Identity has helped improve our organization by providing customer identity management, customer onboarding, customer identity stores, workforce provisioning, and single sign-on as one of the primary functions that has been a benefit."
- "Okta Workforce Identity could improve provisioning; it can be made simpler."
What is our primary use case?
I am using Okta Workforce Identity for identity access management.
How has it helped my organization?
Okta Workforce Identity has helped improve our organization by providing customer identity management, customer onboarding, customer identity stores, workforce provisioning. Additionally, single sign-on is one of the primary functions that has been a benefit.
What needs improvement?
Okta Workforce Identity could improve provisioning it can be made simpler.
They are implementing in one of the newer releases certification, attestation, and some role-mining abilities, but I don't know how far along that's going to be. That's a statement that they said they are going to have in the future.
For how long have I used the solution?
I have been using Okta Workforce Identity for approximately three years.
What do I think about the stability of the solution?
Okta Workforce Identity is scalable.
What do I think about the scalability of the solution?
The scalability of Okta Workforce Identity is great. It's a SaaS solution the scalability is one of the built-in expectations with it. It can scale, even though I don't scale it personally with any of the companies I worked with, it can potentially scale to support millions. It's easily scalable.
How are customer service and support?
I rate the support from Okta Workforce Identity a four out of five.
Which solution did I use previously and why did I switch?
I have previously used Oracle Access Management, Microsoft Azure Active Directory, and ADFS. Those would be the major ones. I've been introduced to small ones, such as PingFederate, but I never used those heavily.
We switched solutions because of the architectural design. We chose Okta Workforce Identity for external customers, it's a customer identity platform that we decided to go with.
How was the initial setup?
The initial setup of Okta Workforce Identity is straightforward. I was able to get an environment ready within half a day.
I rate the initial setup experience of Okta Workforce Identity a four out of five.
What about the implementation team?
I have used an integrator and have done the implementation myself for Okta Workforce Identity.
What's my experience with pricing, setup cost, and licensing?
Okta Workforce Identity scales up by the user, and then by the service that you're purchasing.
The solution is not the cheapest but not the most expensive. They are in the middle rating.
I rate the price of Okta Workforce Identity a three out of five.
What other advice do I have?
I rate Okta Workforce Identity an eight out of ten.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Other
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Buyer's Guide
Download our free Okta Platform Report and get advice and tips from experienced pros
sharing their opinions.
Updated: October 2026
Product Categories
Identity and Access Management as a Service (IDaaS) (IAMaaS) Single Sign-On (SSO) Authentication Systems Privileged Access Management (PAM) Access Management ZTNA as a Service Customer Identity and Access Management (CIAM) AI IT SupportPopular Comparisons
Cloudflare One
Microsoft Entra ID
Prisma Access by Palo Alto Networks
SailPoint Identity Security Cloud
Zscaler Zero Trust Exchange Platform
Idira Privileged Access Manager
Control-M
Zendesk
Cato SASE Cloud Platform
Check Point Harmony SASE (formerly Perimeter 81)
Workspace ONE UEM
Ping Identity Platform
Freshservice
Google Cloud Identity
Buyer's Guide
Download our free Okta Platform Report and get advice and tips from experienced pros
sharing their opinions.
Quick Links
Learn More: Questions:
- Which IDaaS solution do you prefer and why?
- Looking for an Identity and Access Management product for an energy and utility organization
- Is SSO safe?
- Which is the best Privileged Account Management solution?
- What are your best practices for Identity and Access Management (IAM) in the Cloud?
- Why is identity and access management (IAM) so important in preventing data breaches?
- What access management tools would you recommend to help with GDPR compliance?
- How to convince a client that Identity and Access Management (IdAM) is essential for risk elimination?
- How is Zero Trust different from the Least Privileged model?
- What are the differences between LDAP and Active Directory?





















