Customers' workforce often operates within multiple scenarios and setups. For instance, some customers may use Microsoft Active Directory. For example, out of 5,000 employees, only 2,000 might be integrated into AD, while the rest could have access managed directly within specific applications by their respective owners. Users are burdened with managing multiple usernames and passwords, needing to input both separately whenever accessing an application. Moreover, there's a lack of visibility regarding which users possess privileged access, and whenever users change roles, it becomes challenging for customers to update access across various application layers due to the absence of centralised control. To address these issues, Okta Workforce Identity offers a solution. By consolidating identity and access management into a centralised repository, it streamlines access control, providing users with appropriate access levels based on their profiles. This centralised approach simplifies management for customers, enhancing security and efficiency.

Okta controls all the users. It has context-based access from the user and type of device. It identifies the risk and can do a step of authentication when that user is trying to access some sensitive application from an unknown device.

Okta offers single sign-on for those who prefer Microsoft or a single sign-on solution. They have integrated multiple applications with Azure. It still follows the old practice of creating usernames and passwords within the application for some legacy applications. We aim to address this issue by presenting an alternative. Instead of managing multiple username and password combinations. Azure can also integrate with IBM solutions. This creates a unified point of access once they adopt solutions like IBM's within their organisation.

If Okta Workforce Identity has a strong integration with other OEM solutions and can leverage intelligence from those OEMs to enable automatic restricted access for users, it would be highly appreciated. For instance, if it can integrate with DLP and EDR solutions, and if the DLP detects suspicious user activities, it should automatically restrict access to sensitive applications or prompt for multi factor authentication.

I have been using Okta Workforce Identity as an integrator.

The product is stable.

It is highly scalable. More than 2,000 users are using this solution. It is being used by some customers for their end customers, such as online e-commerce portals.

We work with all types of clients, but this particular solution is tailored for mid-scale enterprise customers. They should have at least 5,000 users and several hundred applications for this solution to be effective. The environment and the persona should be at a mature stage. In some organisations, there will be an IT manager, senior IT manager, and head of IT, who will be responsible for both infrastructure and security.

Whenever we need information, we receive the required support from Okta. So, if I need clarification regarding integration, communication, or any related matters, I can get support from the local IT team.

The initial setup requires the expertise of the professional services team.

Okta Workforce Identity is expensive due to currency differences, particularly between INR and USD.

I rate the product’s pricing a seven to eight out of ten, where one is cheap and ten is expensive.

MFA must be implemented to access critical applications. Cost management is essential, as it's impractical to cover payments for all users across all applications. Therefore, a risk-based approach is necessary, where MFA is implemented selectively based on requirements from the same vendor or platform. This facilitates easier deployment, management, and provides a single dashboard view for identifying and managing risks effectively. It also enables the identification of the riskiest users within the organisation.

Overall, I rate the solution an eight out of ten.

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.

We can integrate two-factor authentication with the applications. Two-factor authentication is used for mobile applications like OneDrive.

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.

I have been using the solution for more than five to ten years.

The tool is not free. However, Microsoft is free. So, people prefer Microsoft.

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.

I am just an end user of the product, so I don't know how the product is used in remote force management in our company. I use the product to help me log on to our company's security systems.

When I was traveling, I could get my OTPs through the tool's app, through my cell phone number or via an SMS,which makes it a flexible product. The tool is helpful even in areas involving emails. It is possible to use the product in another country and add an extra layer of security to it, proving that it can be a really secure platform.

I use the tool at a low level, so it does what I need it to do for me.

The product does not offer enough integration capabilities. I want the tool to provide more integration capabilities in the future.

I have been using Okta Workforce Identity for two years.

Stability-wise, I rate the solution a ten out of ten.

It is an easily scalable solution. When it comes to the scalability features, the product has many options for people in different countries, offices, and remote locations.

I believe that there are around 1,500 users of the tool in my company.

I did contact the product's support team when my password got locked out. I could even reset the whole password from Okta easily through the tool's internal app. The support team was good.

The product's initial setup phase is straightforward.

The solution is deployed on the cloud since it is used at a company-wide level in South Africa.

Though I am not sure, I feel that during the implementation phase, my company did seek the help of a consultant and our organization's in-house team.

In terms of benefits offered by the product, I can say that the tool has centralized our company's security and internal policies while ensuring that we stay compliant so that the users stay protected. With the product in place, no phishing attacks or any other types of attacks can cause a problem since it is a secure platform.

Though I don't know about the licensing model of the product, I wouldn't be surprised if Okta offers a per user license subscription model.

The employee onboarding process is okay if you use Okta Workforce Identity.

The SSO feature offered by the product is good, easy to use, and user-friendly. The tool also has a password manager as well.

The tool's MFA part comes as one of the strongest features of the product.

I feel that it is a good platform with a good security layer, especially when you are scaling out your business, and you have to manage a lot of areas.

I ate the tool a ten out of ten.

We use the product to manage access and identify several applications.

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.

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.

We have been using Okta Workforce Identity for five years.

The technical support services are good. They respond to the queries immediately.

Compared with Okta Workforce Identity, Microsoft Entra ID is challenging to use in terms of integration and troubleshooting.

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.

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.

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.

We use Okta Workforce Identity for single sign-on (SSO).

One of the most beneficial features of the solution is the user provisioning and the de-provisioning feature. With the solution's universal directory, you can have all the user attribute information in one place. You can store it on Okta instead of in multiple places like your AD, applications, or different IdPs. You can get all the user attribute data onto your Okta, and then you can customize it. Okta allows you to modify the user attributes, which is also one of the useful features of Okta Workforce Identity.

Because it's a password-less authentication for personal sign-on, users don't need to use a password for it. That's how Okta comes into the picture, where it identifies the user based on the certificates for authentication. In that way, it also doesn't reveal the user identity to the applications if there is a man-in-the-middle (MITM) attack.

Okta Workforce Identity uses the System for Cross-domain Identity Management (SCIM) protocol for provisioning and de-provisioning. That is also one of the benefits of having your application's functionality on a platform like Okta Workforce Identity. It's easy from an admin point of view because when you de-provision a user on Okta, it will remove all the access from the respective applications without needing anything at the application level.

Because it's a cloud-based platform, installing the agents is the only integration you need to do in your current environment. You can have their agents installed on your Active Directory servers.

The integration is quite easy for other cloud applications. They have their own catalog of all the applications you can search and integrate. Applications like Microsoft Office 365 and Salesforce are already hosted on Okta. It's just a matter of configuring the applications with your company's metadata into your applications.

The solution's user interface needs to be improved and made easy. It has a lot of repetitive things. The solution should have a single pane of interface for admins.

I have been using Okta Workforce Identity for six months.

I rate Okta Workforce Identity an eight out of ten for stability.

Since it's a cloud-based platform, I haven't faced any scalability issues with Okta Workforce Identity. Our clients for Okta Workforce Identity are enterprise businesses.

I rate the solution an eight out of ten for scalability.

The solution's technical support depends on the service level. Okta has certain packages, like gold or silver levels. If you have a silver-level agreement with Okta, you can get the right support at the right time.

On a scale from one to ten, where one is difficult and ten is easy, I rate the solution's initial setup an eight out of ten.

Okta Workforce Identity is one of the market's leading and stable identity solutions.

Overall, I rate the solution an eight 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.

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.

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.

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.

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.

I have been working with the product for eight years.

The product works at times, and sometimes it doesn't. You will have to change the conditions when it doesn't work.

Okta Workforce Identity is scalable. My company has 650 users for it.

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.

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.

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.

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.

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.

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.

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.

I have been using Okta Workforce Identity for five years. My company is a customer of Okta.

It is a very stable 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.

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.

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.

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.

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.

We use the solution to give access to the server. It verifies and allows users to access the server.

The product is easy to use. I just have to click on the Okta app on my mobile. The verification takes two seconds. We need to verify once we start the software because we use single sign-on.

The stability could be better.

I have been using the solution since April. I am using the latest version of the solution.

I rate the tool’s stability an eight or a nine out of ten.

Around 2000 to 3000 people use the product in our organization.

The deployment was done in-house.

I would recommend the product to others. It is a good solution. Overall, I rate the tool an eight out of ten.