Okta Workforce Identity Reviews

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 platform’s most valuable feature is the universal directory, where we can create different identities and build policies. It is flexible and easy to install.

They could provide collaboration with Microsoft for conditional access and other features. They could work on reducing bugs as well.

We have been using Okta Workforce Identity for five years.

We receive technical support through third-party suppliers. They provide good support services.

The platform can be deployed on the cloud.

The product generates a return on investment in terms of documentation quality and support services provided by Okta.

The product is expensive compared to other vendors.

We are evaluating a few products for our customers.

The impact on user provisioning and de-provisioning processes with Okta Workforce Identity varied depending on the application. Customized applications help in automatic identification. However, it only facilitates provisioning and not de-provisioning. The security posture has significantly eased various aspects of IAM. The integration capabilities of Okta have provided benefits, especially compared to Azure.

I rate it a seven out of ten.

I mainly use Workforce Identity to give users access to applications.

Workforce Identity's best features include its user-friendliness and easy setup.

In some setup cases, there are issues with attributes not going in properly. We've also had some problems with the firewall causing the data center to slow down.

I've been using Workforce Identity for about a year and five months.

Workforce Identity is stable.

Workforce Identity is scalable.

I previously worked with One Identity Manager and IBM Identity Manager.

The initial setup is easy.

Workforce Identity is well-priced.

I'd advise anybody thinking of implementing Workforce Identity to be careful with their setup roadmap. I would give Workforce Identity a rating of seven out of ten.

As an Okta Identity engineer, I implement Okta for different clients such as banks, telecoms, and insurance companies. These companies need an IAM solution to manage their employees securely and provide them with access to the right applications. Okta is used to automate provisioning and support any errors encountered during and after deployment. 

Companies use Okta Workforce Identity to manage their employees' secure access to applications and to minimize the effort required by IT teams to manage identities. The solution helps organizations allow their employees to log into their applications without re-entering credentials and securely access their applications via MFA.

The most valuable functions are Single Sign-On (SSO) and Multi-Factor Authentication (MFA). These two modules serve as dual components, essential for securing application access for employees.

Okta could improve by making their learning materials more user-friendly. They could also enhance the flexibility of their MFA feature, allowing clients to implement preferred MFA methods without restrictions.

I've been handling Okta Workforce Identity for five years now.

There might be occasional glitches or bugs that need improvement, so I would rate its stability as eight out of ten.

Okta scores a nine out of ten for scalability.

Okta support is efficient, actively responding on time. They deserve a rating of eight out of ten for their technical support.

Positive

I handle CyberArk IAM solutions alongside Okta. I find Okta to be more user-friendly and flexible than CyberArk, especially regarding MFA and SSO features.

The setup process for Okta is relatively straightforward and not overly complex.

Okta is one of the more expensive IAM solutions, and I would rate it an eight regarding cost.

The main competitor to Okta Workforce Identity is CyberArk Identity.

I would recommend Okta Workforce Identity to other users.

I'd rate the solution nine out of ten.