Okta Workforce Identity Reviews

We use the solution for our single sign-on applications. It resolves password issues.

We use it for authentication and 90% of our SaaS app. 

We use it for on and off-boarding users. It syncs with our on-premises master directory to set them up and take them off.

We like that the solution helps us to streamline multifactor authentication.

It's got great SSO and good provisioning and de-provisioning. 

The product is easy to set up. 

It is stable.

The solution can scale very well.

I've been pleased with its capabilities overall. 

Support could be a bit faster.

I've used the solution for five years. 

The solution is stable. I'd rate its reliability ten out of ten. 

It's extremely scalable. It'd rate the solution's ease of expansion ten out of ten. 

We have 1500 users on the solution currently.

Support is good. However, sometimes it takes them a bit longer to deal with issues. 

Positive

We previously used a different solution. We moved to Okta as the GUI is very user-friendly, and the solution is simple to use. 

The initial setup is very easy. It's not complex. 

The deployment took a matter of three to four days for our hybrid setup.

K+Okta's team helped us deploy the solution. They made it very easy.

We have gotten an ROI in terms of time savings. We've seen 20% to 30% ROI, as it is saving us a lot of time. 

The pricing is a bit expensive. I'd rate it four out of ten in terms of affordability. It's a bit more expensive than our older solution.  

Okta charges per user, and that can make it costly if you are a big company.

We are customers and end-users. 

I'm using the latest version of the solution. 

I'd rate the solution eight out of ten. The pricing is a bit high, and they do charge per user. There are other options that are a bit less expensive. 

Okta Workforce Identity is used for MFA and SSO and it satisfies application authentication.

Okta Workforce Identity has helped our organization by allowing us to work remotely in a secure environment.

The most valuable features of Okta Workforce Identity are SSO, MFA, and beneficial feature sets.

Okta Workforce Identity could improve the way passwords are reset and how it interfaces with Microsoft.

Okta Workforce Identity acquired Auth0 and they should have a solution with integration between the two.

I have been using Okta Workforce Identity for approximately five years.

Okta Workforce Identity has been stable in our usage.

The scalability of Okta Workforce Identity is good, it scales up well. We do not have any issues with slowness, outages, or when we need to increase users.

We have approximately 2,500 users using this solution and their roles vary from administrators, end-users, and highly-trained individuals.

We plan to increase usage, and it will be global.

The technical support is good, we have always had an effective response.

The initial setup was straightforward. The deployment took approximately two months.

I would rate the initial implementation of Okta Workforce Identity a four out of five.

We used Okta to do the implementation. Our experience with them was good, everything went well.

We have two people who do the maintenance and support of the solution.

The price of Okta Workforce Identity is competitively priced. We pay annually for the use of the solution.

We evaluated Microsoft Azure before choosing Okta Workforce Identity.

Microsoft Azure was not closely compatible with their features and support.

My advice to others is to look for an independent tool that goes across applications because you have to look at Apple and Microsoft toolsets. A good independent solution that is hardware agnostic is Okta Workforce Identity.

I rate Okta Workforce Identity nine out of ten.

We are a solution provider and Okta is one of the products that we implement for our clients. I am a solution architect and help to design the system.

Most of our clients have a hybrid architecture where they want to use a single sign-on. They have some applications on-premises, whereas others are on the public cloud. This means that they have a two-tier or three-tier architecture.

Our clients are happy because prior to implementation, they had a very distributed architecture. Okta has allowed them to consolidate with respect to identity management, which increases their operational efficiency.

This product has the features that every customer is looking for.

The most valuable features are ease of operation and visibility.

This product is easy to deploy and easy to manage.

There are cost benefits to using this solution.

The integration with third-party tools needs to be improved. Mainly, the open-source APIs for Splunk would be helpful, as that is where they aggregate most of the data. If this process can be streamlined then it will definitely help.

I have been working with Okta for the past three years.

This is a stable product.

This solution is scalable. Our clients are large, Fortune 500 businesses.

Okta has very good support and I would score them high, at nine out of ten. I am definitely happy with them.

Prior to working with Okta, our clients had native solutions.

The initial setup is straightforward.

We currently have one customer deployed on AWS and another on Azure.

I am the solution architect and our in-house team does the implementation.

As part of the process, our clients did a couple of POCs. Symantec was one of them, Okta was another, and there was a third product that they evaluated. During this process, they had success criteria defined, and Okta did well with most of it.

The metrics included the operation and cost benefits, the business value, and the support.

Every customer has a different need and a different requirement. For anybody who is considering this product, I think they should do a pilot POC to make sure that it works well in their environment. 

I would rate this solution a nine out of ten.

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.

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.

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.

Okta is a stable product.

Currently, scalability is a top priority, but there are no issues with adding many users to Okta.

Before Okta, I manually created portals using a username and password stored in a database. Okta introduced a different process.

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.

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.

The primary use cases are SSO, user management, and SSO integration with various cloud services, including AWS, GCP, GitHub, etc.

The tool provides a single place of contact for managing users. We only need to manage users in Okta Workforce Identity, eliminating the need to duplicate efforts across different systems. For example, if a user needs to be decommissioned, we don't have to go through all the systems and cloud services; we delete the user in one place. This process is automated with our HR system for both organizations, simplifying user lifecycle management.

The main features we find most valuable are the single sign-on and the OTP authentication. The ability to connect via a PC or a mobile phone makes the process seamless.

The MFA feature enhances regular authentication through the user portal and utilizes one-time passwords generated from QR codes on mobile devices.

We faced some challenges during the Okta Identity Workforce deployment. Integrating with AWS and other cloud services posed some limitations with federated options. For instance, features like automatic user addition from AWS to the tool were missing, requiring manual intervention. The API is limited compared to the manual configuration possible through the UI.

I think Okta Workforce Identity could improve by making its API more robust, ensuring that all UI capabilities are exposed in the API. This is particularly important for integrating with other applications, such as AWS and other cloud providers.

I have been working with the product for six years. 

The licensing model is fine for general service usage. However, the charges for API features and API tokens can be quite high.

I would give Okta Workforce Identity a solid eight out of ten. There's always room for improvement, but overall, the tool performs well and meets our needs. The solution was my first experience with such products. Previously, I had used internal tools like Microsoft 365 and Microsoft Active Directory services within Azure, which were excellent for corporate environments. However, I find Okta Workforce Identity more suitable for startups.

Workforce is used to both manage our identities with multi-factor authentication for the users and it's also used to handle workflow, so onboarding and offboarding, et cetera.

They work well if they're set up properly.

The initial setup is easy. It's also easy to use.

We find the solution to be stable.

The pricing is okay.

There is very little maintenance required. 

We've not come across anything missing. It's under continual improvement. It is actually very good. We've not had any problems with Okta. I'd have to think hard to find anything that was badly implemented.

The stability is good. There are no bugs or glitches. It doesn't crash or freeze. It's reliable. The performance is good.

The initial setup is pretty easy. It is very simple to set up initially and it takes a couple of hours. The multi-factor authentication is simple too and can be turned on as required. The one that takes the most effort is SAML, which is the integration with the service providers. That's full-service integration and that's because a lot of service providers do it all their own way. You have to work with each of them as they come up.

In terms of how many people you need to maintain the product, it depends on how you do it. We're managing it for a couple of customers, and it's just me. However, what I've done is, I've put an API, used the API, and put a front end on that to make it easy to do the onboarding and offboarding. I don't deal with the day-to-day issues, that's done by the HR department.

The client actually installed it. We helped as well, however, as I said, the client handled most of it.

The pricing seems very reasonable. None of the customers have complained about it.

We're using the most up-to-date version of the solution.

As far as Okta is concerned, it's deployed in the cloud.

They're a complex software provider. They're a software as a service, software provider. They have a training service, they have a university, they have a community, and they also use it for outbound marketing.

We've implemented it for the clients and they're quite happy with it.

We're a reseller and integrator. We sell the service and do the implementation, and we're also a user ourselves.

I'd rate the solution a nine out of ten.

I'd advise new users to make sure that you implement it properly. If you buy the service and don't implement it properly, you'll never get the benefits from it. They need to make sure that you are monitoring the logs as well as that tells you if someone's doing anything they shouldn't be doing.

The journey for us is towards Zero Trust. We start with multi-factor authentication, and good password policies, and think about moving to fully integrated, where you can. That's SAML, their integration protocol, or Open ID. The next step is to think about how to make sure that all services, internal and external, are authenticated. Zero Trust implementation is where the world has to go

We use this solution for MFA and single sign-on.

It's our enterprise-wide identity management system. It identifies all of our users prior to accessing any of our applications.

It assures us that everybody is authenticated prior to accessing any corporate applications.

The most valuable features are multifactor authentication and single sign-on.

It's reliable and it does what it is advertised to do.

The guest user access could be improved. How do we authenticate people that aren't in our Active Directory?

In the next release, I would like to see passwordless access.

I have been using this solution for four years.

We are working with the current version.

This product is very stable and is one of our best applications. It's the most reliable application and it never goes down.

It's a scalable solution and we are able to add users as needed.

We have about 4,000 users and it's all employees and contractors within the company.

Every employee uses this solution every day, multiple times a day, and we plan to increase usage.

They meet our needs. 

We haven't had a problem with technical support answering any of our questions.

We went from using nothing to Okta Workforce Identity.

The initial setup was straightforward.

It was a week-long process to deploy.

We need one and a half persons to do the configuration, maintain this solution for administrators and the development.

We completed the implementation in-house.

We have seen a return on investment by using Okta Workforce Identity.

I can't discuss pricing.

Follow along with what Okta recommends.

I would rate Okta Workforce Identity a ten out of ten.

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.

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 providing top-notch team access management to companies.

I have been working with Okta Workforce Identity for the past 10 months.

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.

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.

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.

Positive

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.

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.