Okta Workforce Identity stores all your applications in a portal. It saves passwords, eliminating the need to remember them. In addition, we use 1Password as a backup in case someone forgets their password.
System Engineer at Principia
An user-friendly solution that helps to store passwords in one place
Pros and Cons
- "I like the tool's workflows, which is user-friendly. It can integrate with different applications. I particularly like that users are delighted to access their applications without the hassle of entering their username and password each time. It truly enhances user-friendliness."
- "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."
What is our primary use case?
How has it helped my organization?
In my organization, people thank me for integrating the product. Integrating applications with the solution makes it simple to access various applications. You can easily navigate through a list of 50 applications, click the one you need, and log in.
What is most valuable?
I like the tool's workflows, which is user-friendly. It can integrate with different applications. I particularly like that users are delighted to access their applications without the hassle of entering their username and password each time. It truly enhances user-friendliness.
What needs improvement?
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.
Buyer's Guide
Okta Platform
March 2026
Learn what your peers think about Okta Platform. Get advice and tips from experienced pros sharing their opinions. Updated: March 2026.
884,976 professionals have used our research since 2012.
For how long have I used the solution?
I have been working with the product for eight years.
What do I think about the stability of the solution?
The product works at times, and sometimes it doesn't. You will have to change the conditions when it doesn't work.
What do I think about the scalability of the solution?
Okta Workforce Identity is scalable. My company has 650 users for it.
How are customer service and support?
The tool's tech support is hard to get a hold of. Also, you would speak to a robot who knows a lot of information, doesn't listen to your questions, and misguides you.
Which solution did I use previously and why did I switch?
I have worked with Microsoft Azure, Slack, Teams, and Adobe Creative Suite. Microsoft Azure and Okta Workforce Identity allow applications to be implemented similarly. The process involves having an extension for the application, often a download file. However, it's important to note that while this implementation works on PCs, it might work on Macs.
How was the initial setup?
The tool's deployment is straightforward. You begin implementing applications once you've established your IDP. Deployment doesn't need a team of people. It can be done with the help of one person. Setting it up and integrating applications typically takes about a week, with additional time required for a more extensive list of applications, ranging from 50-100.
The product is not difficult to maintain once you have integrated it.
What other advice do I have?
I would rate the product an eight out of ten. My advice would be to exercise caution when implementing applications. Incorrect configurations may lead to issues, such as not having the correct username and password saved when clicking on the title. Additionally, when working with workflows, paying attention to the order of conditions is crucial. The tool is user-friendly, and you can have your applications in one place. This makes it less confusing for the users.
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.
Information Technology System Administrator at General Assembly
Ability to work with a wide range of applications and security mechanisms
Pros and Cons
- "As far as our security team is concerned, the ease of implementing multifactor authentication is definitely the biggest value for our organization."
- "Some limitations in scalability. Each application we work with can be completely different, resulting in highly variable implementation processes."
What is our primary use case?
I have implemented a number of applications as far as accessing them through their IDPs. And they're an identity provider; they also provide some alternative active directory slash l dash services. And I have purchased those for getting user data onto other systems.
It's very straightforward. The automation that they have and the way that they let you assign applications to groups or to users and do things dynamically, it is very straightforward other than just that there's a lot of nuance because of the breadth of applications out there that they can work with. It's more a matter of knowing how to work with the security mechanisms in place, such as SAML or OAuth, these may require specific expertise.
What is most valuable?
As far as our security team is concerned, the ease of implementing multifactor authentication is definitely the biggest value for our organization. Additionally, the single sign-on services provided by Okta allow users to log in to their Okta account and access a variety of other applications. That's why we implemented Connect to leverage this feature more efficiently across MacOS.
What needs improvement?
There are areas for improvement. One thing that seems odd to me is the lack of a built-in way to export all user data. They have a solution available on GitHub that they basically endorse, and it's developed internally, but for some reason, it's not integrated into their product. So, that's a peculiar aspect.
Instead, the support says they don't offer it but provide an alternative solution that we have to manage separately. So, it's a situation where they don't want to include it in their product, but they offer assistance outside of it? It's unclear what kind of support you would need for it. It just works.
Another area of improvement is scalability.
For how long have I used the solution?
I have been working with Okta for two and a half years.
What do I think about the stability of the solution?
Okta is pretty stable. Occasionally, we encounter notifications indicating some issues, but that has happened only once or twice in the two years I've been using it.
There have been situations where our own users were temporarily affected by disruptions in the cloud, but those incidents lasted only for a couple of hours. Taking into account a 99.9% uptime SOA.
What do I think about the scalability of the solution?
I would rate its scalability seven out of ten. There are definitely challenges we encounter, not related to the number of users but rather in terms of implementing various applications. Each application we work with can be completely different, resulting in highly variable implementation processes.
It ultimately depends on the specific use cases you have and the tools you utilize. It's important to find the best solution tailored to your needs.
We have around 500 users utilizing Okta Customer Identity.
How was the initial setup?
The initial setup is fairly easy. I would estimate it to be at least an eight in terms of ease of setup.
The actual setup and configuration can be done in half a day or less. However, the main challenge lies in communicating with users and getting them to adopt and use it, rather than the technical setup itself.
It's more about informing everyone about the new requirement, that instead of logging in to each application separately, they can now log in to the Identity Provider (IDP) and utilize its Single Sign-On (SSO) capabilities to simplify the login process for all applications.
What's my experience with pricing, setup cost, and licensing?
Okta's pricing is right where it needs to be and right in the middle of the market. You can pay them extra for services for assistance in implementing certain applications. You can hire one of their engineers to work with you and ensure successful implementation.
And that's something worth considering because they have expertise in their product and can get the job done more efficiently. It's worth paying for their services to ensure the solution is implemented successfully rather than struggling internally and failing to get it done.
What other advice do I have?
Overall, I would rate Okta a nine out of ten because there is always room for improvement. However, it is best in class as far as doing the things it does. And it's something that I've implemented with multiple businesses.
And it's really well-regarded. Yes. There are alternatives out there. Like, they all do somewhat different in each thing, whereas Okta seems to really be trying to cover all the bases as far as providing solutions that integrate with people's OSBAP, people's active directory, companies that wanna get serverless, touching on, the zero test network security that they're really kind of playing in the center of that zone.
Which deployment model are you using for this solution?
Public Cloud
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Buyer's Guide
Okta Platform
March 2026
Learn what your peers think about Okta Platform. Get advice and tips from experienced pros sharing their opinions. Updated: March 2026.
884,976 professionals have used our research since 2012.
Senior IT Engineer at Instawork
A stable and scalable tool that allows for application control on a single console
Pros and Cons
- "It is a very stable solution."
- "The only area of concern in the solution stems from the fact that my company needs some help regarding the setup phase from a partner."
What is our primary use case?
I use Okta Workforce Identity in my company since it supports single sign-on (SSO).
Okta Workforce Identity is good for helping control all applications in one console.
What is most valuable?
The most valuable feature of the solution stems from the fact that one can create a lot of workflows with the product while also being able to add Jamf software. One can also add a lot of applications with Okta Workforce Identity so that employees can use and access them from a single console. During employees' onboarding or offboarding processes, it is very easy to activate and deactivate their access.
What needs improvement?
The only area of concern in the solution stems from the fact that my company needs some help regarding the setup phase from a partner.
For how long have I used the solution?
I have been using Okta Workforce Identity for five years. My company is a customer of Okta.
What do I think about the stability of the solution?
It is a very stable solution.
What do I think about the scalability of the solution?
It is a scalable solution.
Around 1,000 people in my company use Okta Workforce Identity. Whatever accesses we provide in our company are provided through Okta.
How are customer service and support?
Whenever my company has raised a ticket with Okta's support team, we always receive immediate support. I rate the technical support a ten out of ten.
How would you rate customer service and support?
Positive
What about the implementation team?
For the initial setup phase of Okta Workforce Identity, you need a person from Okta to help you. In general, you may require Okta's partner's help with the initial setup phase.
What's my experience with pricing, setup cost, and licensing?
Price-wise, Okta Workforce Identity is a cheap solution. The overall cost depends on the license since you can negotiate with Okta or any of Okta's partners only if you opt for many licenses.
What other advice do I have?
I have not seen any disadvantages in Okta Workforce Identity. From whatever I have seen and experienced, I can say that Okta Workforce Identity is a good tool.
If you have more than 500 or 1,000 employees in your company with limited IT personnel, then you can use Okta Workforce Identity since it allows you to give access to your employees with just one console. If any employees decide to leave the organization, then it is very easy to deactivate or remove their access from your network. Okta Workforce Identity helps save bandwidth and time.
Once you get the console, it is very easy to access or add applications, reset the password for users, and reset the authenticator. If you have access to KT or knowledge transfer, it is very easy to understand Okta Workforce Identity.
I rate the overall solution a ten out of ten.
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Service Delivery Manager at Cambridge Technology Enterprises (CTE)
Has multi-factor authentication and 99.9% service availability
Pros and Cons
- "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 training is too costly."
What is our primary use case?
Okta provides island access management solutions, which means that anyone who needs an IIM solution can get it through Okta. For example, if you have 30-40 applications and users that need to log in to all of them, Okta can integrate all of the applications into a single point of access where users can log in once and use the same session for all of their applications. Okta also provides multi-factor authentication and other security policies to protect your users and applications.
What is most valuable?
We have multiple SSO protocols that we use for our different data centers. This is just one example of how we use Okta workforce identity to address our hybrid workforce needs. Apart from SSO, we also have Active Directory integrations that allow us to integrate with customer active directories and use active directory passwords for application sign-in and runtime authentication. This is called daily header authentication. This allows us to provide a centralized identity management platform for our users, regardless of where they are located or what applications they need to access. 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.
What needs improvement?
Currently, it has two-factor authentication. In addition to biometrics, it should offer three-factor authentication. Also, the training is too costly. Okta could reduce the training cost to make it easier.
For how long have I used the solution?
I have been using Okta Workforce Identity as a service provider for four years.
What do I think about the stability of the solution?
I rate the solution’s stability a ten out of ten.
What do I think about the scalability of the solution?
The solution’s scalability is huge. It has 99.9% service availability. We cater this solution to enterprises. I rate the solution’s scalability a ten out of ten.
How was the initial setup?
The initial setup is easy. Once you understand the steps, it's straightforward. There are three steps: enrolling users, removing tenants, and updating field metadata from outside the application and SaaS integration. Deployment depends on the number of occasions, testing, and the users. If you have 30,000 users, you will need two months. I rate the initial setup a ten out of ten.
What other advice do I have?
The solution is suitable for everyone, but it is locked up for a total number of years. Overall, I rate the solution a ten out of ten.
Disclosure: My company has a business relationship with this vendor other than being a customer.
Regional Security Officer at a comms service provider with 10,001+ employees
A highly scalable and stable solution that is easy to use and provides a single sign-on feature
Pros and Cons
- "The end user's ease of use is the most valuable feature."
- "The integration process takes a bit longer than we would want it to."
What is our primary use case?
We use the product for a variety of applications to establish the basic functionality of single sign-on for the company. We are looking for more use cases for our users. We are a marketing company. We have a high turnover rate. The processes are key to us. We are exploring how we can take advantage of Okta to help us streamline processes.
How has it helped my organization?
We used to have around 12 systems that had unique logins. There were too many central repositories. Now, we can log in using a single presenter.
What is most valuable?
The end user's ease of use is the most valuable feature.
What needs improvement?
We faced a bit of an issue integrating the product with some applications. The integration process takes a bit longer than we would want it to.
For how long have I used the solution?
I have been using the solution for around three years.
What do I think about the stability of the solution?
I rate the tool’s stability a nine out of ten.
What do I think about the scalability of the solution?
I rate the tool’s scalability a ten out of ten.
How was the initial setup?
The initial setup was complex. It was not Okta’s issue. We are a holding company with over 30 Active Directory. There were complexities on our side. The product is deployed on the cloud.
What was our ROI?
It’s a long-term game. We don't expect to see a return on investment very soon.
What's my experience with pricing, setup cost, and licensing?
The solution is really expensive. We are struggling a bit.
What other advice do I have?
People considering the product must not only think about whether the tool will solve their immediate problem. They must think of all the things they want in the future before deploying the tool. Overall, I rate the product a nine out of ten.
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Database and Systems Manager of the IT department at Humanitree
Easy to implement with great synchronization of services and helpful support
Pros and Cons
- "It offers very helpful support. The technical team is very helpful."
- "The solution is very expensive."
What is our primary use case?
We are primarily trying to uncover the differences between this product and JumpCloud.
How has it helped my organization?
Okta has its own Active Directory, which is the main core of your identity and from Okta, you can easily reply to other services, like Google Workspace. You can synchronize everything.
What is most valuable?
It is very easy to implement. We just followed the documentation and followed the steps to connect to our services. They have all of these recommendations in place. If you follow the process, it's very straightforward.
The synchronization of services is very easy.
It offers very helpful support. The technical team is very helpful.
It is scalable.
The solution is always very stable and reliable.
What needs improvement?
I'm not sure what areas need improvement. They are at the top in terms of identity management. I can't find any shortcomings.
We don't need any additional features as it covers more than our needs. It's a massive tool.
The solution is very expensive.
For how long have I used the solution?
We have tried a 30-day trial and implemented in our lab.
What do I think about the stability of the solution?
The stability is great. I'd rate it eight out of ten. There are no bugs or glitches. It doesn't crash or freeze.
What do I think about the scalability of the solution?
We have temporary accounts right now. We have six or eight accounts and the same number of devices.
The scalability is pretty good. I'd rate it eight out of ten. It can expand.
How are customer service and support?
Technical support is excellent. They are helpful and responsive.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
I've also used JumpCloud and have started to compare these two solutions.
How was the initial setup?
The initial setup is complex. However, you have all of the documentation and if you follow the directions, you can manage the setup well. It will be done correctly. Also, if you need help, their support is also available, and they are quite helpful.
We had two people handling the deployment.
What was our ROI?
It might take a lot of time to achieve an ROI. However, it simplifies a lot of duties. Likely, you'd see a return in the future.
What's my experience with pricing, setup cost, and licensing?
We are using the 30-day free trial.
The solution is expensive. I'd rate it one out of ten in terms of affordability.
What other advice do I have?
I cannot recall the version we were using. However, my understanding is that the trial version is the same as the full solution.
You do have to follow the documentation for your specific case. Okta is a massive tool. It covers a lot of use cases and likely will cover more of the company's actual needs. It's a good idea to be specific about your needs.
I'd rate the solution ten out of ten.
Which deployment model are you using for this solution?
Public Cloud
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Site Reliability Engineer at a tech vendor with 10,001+ employees
Single specialist has managed smooth deployment and supports reliable access control
Pros and Cons
- "If anyone asks for a suggestion, I will definitely suggest Okta Platform."
What is our primary use case?
I work for a review website for enterprise IT. We publish reviews for other people to read, either publicly or anonymously. We also work directly with Okta Platform, and they are interested in user feedback regarding what people like and what people dislike about their product. I am actively using Okta Platform.
What is most valuable?
Okta Platform team told us about a feature called Universal Directory. I have tried using it.
What do I think about the stability of the solution?
Okta Platform performs well regarding stability, lagging, crashing, and downtime.
What do I think about the scalability of the solution?
Okta Platform can be scaled across different applications, platforms, and even for dashboard missions. It performs well regarding scalability.
Which solution did I use previously and why did I switch?
I have not tried using any alternatives to Okta Platform or similar solutions.
How was the initial setup?
Okta Platform pricing and deployment are easy.
What about the implementation team?
One person can handle the deployment for a new client. Deploying Okta Platform does not require any maintenance on my end.
What other advice do I have?
I do not have any partnerships with Okta Platform; I am just a customer. I will refer Okta Platform if scenarios arise. If anyone asks for a suggestion, I will definitely suggest Okta Platform. I would give Okta Platform a rating of nine out of ten because no software deserves a perfect score, but Okta Platform comes very close.
Disclosure: My company does not have a business relationship with this vendor other than being a customer.
Last updated: Feb 28, 2026
Flag as inappropriateIT Manager at Clear Channel
Reliable platform with simple setup process
Pros and Cons
- "The product’s most valuable feature is multifactor authentication."
- "It is challenging to obtain a comprehensive backup."
What is our primary use case?
We use the product to manage access and identify several applications.
What is most valuable?
The product’s most valuable feature is multifactor authentication. It has an easier integration and configuration management process than Microsoft Entra ID. We can integrate it into different platforms.
What needs improvement?
An area for potential improvement in Okta lies in the absence of a dedicated feature for backing up the configuration of our tenants. It is challenging to obtain a comprehensive backup. We have to manually document all the configurations. They could provide a built-in tool for creating backups mitigating potential issues or crises.
For how long have I used the solution?
We have been using Okta Workforce Identity for five years.
How are customer service and support?
The technical support services are good. They respond to the queries immediately.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
Compared with Okta Workforce Identity, Microsoft Entra ID is challenging to use in terms of integration and troubleshooting.
How was the initial setup?
The initial setup is simple. I rate the process an eight out of ten. It takes a few weeks to complete the integration for different projects. It is a reasonable time.
The deployment team includes administrators for the applications, as they are responsible for configuring integrations from their side. The administrator plays a crucial role in integrating the Active Directory. The project may require a collaborative effort of approximately three to five individuals. It requires two engineers for maintenance.
What other advice do I have?
The single sign-on (SSO) capability in Okta has significantly streamlined the user experience. It provides an ease of accessing applications. The subsequent access to other applications within the same browser is automatic, eliminating the need to initiate the multi-factor authentication (MFA) process repeatedly. We can define trusted sources and policies depending on the security requirements.
The centralized approach to managing everything from a central point has streamlined administrative tasks, eliminating the need to navigate through different systems for user and role management. It is one of the best solutions. We find a lot of information on their support website.
The overall reliability is commendable, as the platform strategically replicates its systems across various clouds, minimizing the likelihood of service disruptions. Over the past five years, we have not encountered any problems with the service.
I rate it a nine out of ten.
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: March 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
Microsoft Entra ID
Prisma Access by Palo Alto Networks
Cloudflare One
SailPoint Identity Security Cloud
CyberArk Privileged Access Manager
Zscaler Zero Trust Exchange Platform
Cato SASE Cloud Platform
Workspace ONE UEM
Omada Identity
Saviynt Identity Cloud
Check Point Harmony SASE (formerly Perimeter 81)
Fortinet FortiAuthenticator
Ping Identity Platform
Cisco Duo
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?





















