Okta Workforce Identity Reviews

The primary use case is for identity and access management. The single sign-on and access control can be done as a part of Okta. You have APIs to work within Okta and user provisioning.

It's easy to use and straightforward. 

It's my personal opinion, but it was a classic UI and now the UI is different. I was used to the old UI and when I moved from the old to new, I found it a bit difficult.

I have more than a few years experience of working on Okta.

It is stable.

The technical support for Okta is really supportive.

It's on a cloud platform, so all you have to do are the configurations.

As Okta is basically comm center identity and access management, I rate it nine out of ten.

We are using Okta as a service where users can access our services that are maintained in the cloud or on other websites.

We like the access the solution provides to our users. 

The initial setup is pretty straightforward. 

The solution so far has been very stable. 

The scalability has been good.

Technical support is helpful.

Okta can consider to become also a password vaulting manager. We also didn't find an option to setup access to web services that require second factor authentication. Also it's hard to figure out which license is responsible for which features and how are they correlated.

We've been using the solution since February.

The solution is stable. We did not really have any problems. At least, our internal customers, our employees, did not claim that anything happened with Okta. We haven't heard of bugs or glitches. It doesn't crash or freeze. It seems to be reliable. 

It's my understanding that the solution can scale. 

At our company, we have about 500 users on the product.

From time to time we add some other applications that are also in Okta, or we try to add new applications by ourselves, based on templates that are in Okta. We are using Okta on a daily basis, let's say. Maybe not for maintenance, however, our users use it.

We had some contact with technical support at the beginning and it was rather good. We are satisfied with the level of support we can get.

The implementation was rather straightforward. It wasn't too complex or difficult. We had some issues, however, they were solved.

Deployment took about a month or so. 

We had two people handle the deployment. 

We had a session with the reseller, however, we did run a trial a few months earlier. Then, in February, or in December last year, after this trial, we were able to implement it by ourselves.

We pay for the solution on a yearly basis. We recognize it as quite expensive.

We were using a standard license during the trial. We felt that we would get more features. However, there were some misunderstandings with our reseller and the reseller did not know this product very well. Therefore, it was hard at the beginning to get to know which features were covered under which license.

We're just a customer and an end-user.

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

The primarily use of the solution has been for education and to support our Federation identification as well. We also use it for a Google IDM, in that you use it to segregate our Google DCB environment and provide for our engineers.

Overall, the solution works perfectly.

We especially appreciate that it's very easy to manage. For me, as a manager, it brings a lot of value for us and makes our clients very happy.

The initial setup is easy.

The solution really does have all of the features we need.

The pricing could be improved. Right now, it's a bit expensive. They should work to make it more affordable.

In general, the solution isn't really missing any features. It's rather complete. I can't recall anything that would need to be added into future updates.

I've been dealing with the solution for about a year and a half or something like that. It hasn't been too long.

The stability has been perfect. There are no bugs or glitches. It doesn't crash or freeze. It's performance is reliable. We're quite satisfied.

Being a cloud product, and like other cloud products, the solution can scale quite well. If a company needs to expand it, it can do so with ease. It's very accommodating.

Currently, we have more than 130 users on the solution.

I can't speak to the quality of technical support. I've never used them. I couldn't say if they are knowledgeable or responsive. I have no personal experience in the matter.

The initial implementation is not overly complex. It's easy. It's rather straightforward. A company shouldn't have any issues with the setup process.

The deployment is pretty quick. We had everything set up within a week or so. It's not a long, drawn-out process by any means.

The pricing is a bit costly. It could be lower.

We're resellers. We have a business relationship with the organization.

I'm not sure which version of the solution I'm currently using right now.

This, overall, is a very good solution. It can solve a lot of problems related to compliance regulations. We looked at this kind of solution as we don't have a PCI. It works well for us.

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

We mostly use it for MFA for logging into our Windows RDS environment and a web-based application called Tableau. We are using the latest version.

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. 

They also have single sign-on (SSO). When we bought Okta Workforce Identity a year and a half ago, I was also looking at SSO, but not much documentation was available for SSO. The documentation for SSO should be a little more robust for somebody who is implementing it for the first time. 

I have been using Okta Workforce Identity for almost one and a half years.

It is stable. I never faced any issues with its stability.

I have not scaled it much. The company for which we implemented this solution is into data mining or data analytics. They had multiple users. Most of the users were data scientists. I was the only one looking at it in terms of management.

There were a couple of occasions where I needed some support while setting it up for our RDS environment. Their technical support was educated enough with respect to the product. They were able to help us out and resolve the issue pretty quickly. I would say they are good on the support part.

Setting up the MFA for Windows RDS was very straightforward. Using it with Tableau was not very straightforward. It was a bit complex, but the documentation was handy enough to set it up.

I believe it competes well. The pricing is pretty competitive. I know that Microsoft also provides something similar with its MFA and identity services. 

It has been sufficient for our needs. I haven't seen any issues, so I would say it is a good product. If there was anything, the users would have complained, but I haven't received any complaints with respect to Okta Workforce Identity from the users. 

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

We use it as an SSO hub for applications to be added/removed from users' profiles and troubleshooting, as well as an active directory. 

I work at a service desk providing IT support to PayU international and Naspers.

It made things a lot easier, especially with passwords. You have one password that you have to remember, not a thousand for each application that you use for work.

We can have all our applications in one central base where you can log into it and access it without having to enter your password for each application. This is because it saves your credentials and updates them accordingly.

On the admin side, we can create our own passwords instead of generating one, which is usually difficult to explain to a user. Otherwise, the application is pretty awesome.

Okta is not just an identity provider (IdP) since, with the help of SAML, it can also be a service provider (SP), which then allows it to integrate with a different identity provider. In other words, it provides SSO. In my organization, we use Okta as a centralized solution for our multiple platforms. With just one login users are able to access any associated platforms without having to log in multiple times.

All our logins work seamlessly without having to log in multiple times. With multiple applications, you tend to forget your credentials for some of the applications. Some applications have different password policies. With Okta, all of these is centralized. You only need one password, one setup, one policy and one login.

Other than Okta being an easy and awesome integration tool, one of the best features it has is the provisioning and deprovisioning, which makes management way easier. You don't need to be too technical to understand how it works.

They also have a good knowledge base that helps end-user to self-serve.

Maybe the interface could use some work but, for the most part, the tool is pretty cool.

I rate Okta 10 out of 10 for being an awesome IdP. The API alone is amazing, not to mention the features and integration they have. Compare to other IdPs, Okta uses a dashboard that displays all the associated/linked services, which is really helpful when you have multiple services. It's really an easy tool and their support is great.

Our customers use it for multi-factor authentication, lifecycle, and workflow.

The most valuable features depend on a customer's needs. Our customers generally find multi-factor authentication very useful.

The lifecycle management part can be improved. It should also have identity governance and the ability to choose a specific factor authentication at the application level.

Its licensing and pricing can also be improved.

I have been using this solution for one year.

It is stable.

We scaled it for some customers. There were no problems.

We are only using professional services at the moment.

It was easy.

It has a yearly subscription. As compared to its competitors, it is quite expensive. It also has a complex licensing model.

I would recommend this solution to others. I would advise others to be aware of the complexity of the license. They should make sure that they have all the features that they want.

I would rate Okta Workforce Identity an eight out of ten.

We used this solution for provisioning more than one and a half LAC users and integrating more than 300 applications. SSO and MFA has been implemented on almost all applications. MFA options used: RSA token, Okta Verify, etc.

Integrating more than 300 applications is quite tough. With the help of Okta and its outstanding user friendly UI, things went fairly easily.

• The ease of JIT provisioning.
• Wide range of MFA options. I prefer "Okta Verify" out of them all.
• Last, but not least, the ease of writing rules.

RESTful Web Service calls and their response seem a bit slow.