As an integrator, I work with Okta Platform.

Okta Platform can be used for IAM and IGA; it is a cloud-based solution for Identity and Access Management, as well as Identity Governance and Access.

As an integrator, I find Okta Platform user-friendly with a good number of connectors, making it easy to integrate with applications, and it is easy for SSO implementation and MFA implementation.

Lifecycle Management is configurable in Okta Platform; you can configure the joiners, movers, and leavers process with this product.

Okta Platform is a cloud-based platform, so you do not have to take care of installations as you would with on-premises solutions for SailPoint or Oracle Identity Management, which is a big difference.

Based on requirements, context-aware policies of Adaptive MFA are configurable, which is a plus point, as you can configure it based on certain requirements, such as adaptive authentication based on behavioral patterns and logging in from one place to another.

It is time-saving, which is definitely linked with money; a lesser number of users are required to do the manual work, so it has that impact on money as well.

I have not encountered any negative points for this product.

For log monitoring, after a certain period of time, logs are deleted, such as after three months, and you have to configure it using a separate or external SIEM connector, such as Splunk or Cortex XSOAR, because after 90 days, the logs will be deleted, so we have to take an export manually or add one external log monitoring solution.

If the organization is big, I can say Okta Platform is affordable; however, for small-scale industries, I would not recommend it, but for medium and enterprise organizations, it is good.

I have been using Okta Platform for approximately one to one and a half years.

Okta Platform is a stable product.

Okta Platform is a scalable product.

I can rate Okta Platform support at approximately eight or nine out of ten.

I have worked with Oracle Identity Management and SailPoint as other access management tools before.

I have not worked with Universal Directory in my case, and I have not worked on it recently.

Okta Platform is an IGA solution, so in terms of PAM capabilities, it is not working as PAM for storing passwords or secret vaults, such as Delinea or CyberArk; it is a completely different product.

I don't have many details about Okta Workforce Identity. I use the tool just to sign in to different applications that we have. We basically set up Okta Workforce Identity in our mobile phone. We do the scanning part and then enter our official email address and acknowledge that. They will send a code to the mobile phone. Once that code is authenticated, we are good enough to use that tool going forward. That's the initial setup we do on Okta Workforce Identity.

Okta Workforce Identity is really useful because all internal users that we have in our transfer server have now moved to it. In the progress, it's a suite, as it's a part of MOVEit Automation as well as MOVEit Transfer. On the MOVEit Transfer, all internal users in our company have moved to Okta Workforce Identity single sign-on option. The benefit was addressing issues where people were using incorrect passwords. When they continuously put incorrect passwords, their IP would get locked and their account would get locked. Additionally, there were very few users who kept passwords in secret tools or KeePass tools. Most of them were putting the passwords either in mobile phones or in OneNote or text documents where the data could get breached easily. To deal with all these issues, Okta Workforce Identity is a perfect tool where internal applications can be signed in using your authentication tool itself. It functions as two-factor authentication.

I am using Okta Workforce Identity for login purposes only.

The best feature is the speed and execution of Okta Workforce Identity. The moment you click on single sign-on, you immediately get the notification on your mobile phone, then you do the authentication and within a second you get authenticated. The entire customer experience is very good. The user interface is pretty simple, straightforward, and really good.

Multi-factor authentication in Okta Workforce Identity is very useful so people who do not have access or are trying to access using just a user ID and password will be completely blocked because of this two-factor authentication. You will get the code, and as your device is authorized in the system, only that device can be used for the authentication purpose. A third person trying to access or hack your data will not be able to do that anymore. Additionally, you don't have to remember your passwords going forward. Previously, every 60 days or 90 days, passwords kept changing. With the two-factor authentication or single sign-on option in Okta Workforce Identity, you don't have to remember it anymore or write down passwords in plain text. If something goes wrong, we have the IAM team which can unlock your account immediately if you have issues.

Currently, in Okta Workforce Identity we get the two-digit authentication code. Instead of getting the two-digit authentication code, if we had an option to do fingerprint verification, that would be beneficial. We have already secured that only the device where we have installed Okta Workforce Identity can do the authentication. However, if that phone or device gets stolen, somebody else can log into the system using that code. If there was a fingerprint option, then only the person who has already added their fingerprint on their mobile phone could access it. This would provide double protection.

I started using Okta Workforce Identity four months ago in our company.

I didn't have any single sign-on technologies before Okta Workforce Identity. I started with AWS and then adapted Okta Workforce Identity.

The initial setup of Okta Workforce Identity is straightforward. We haven't encountered any issues because if we had, we might have gotten emails from the security or the IAM team who handled the installation. Nothing went wrong. It was pretty smooth.

I have seen ROI from Okta Workforce Identity. It was a great implementation. Initially, we had multiple places where we had to store links in browsers to access different applications. We don't have to do that any longer now. We have our dashboard to log in via Okta Workforce Identity. Once logged in, it shows our company's portal where we see different applications. When you click on an application, you automatically get signed into that particular website.

Most of our internal applications are getting migrated to Okta Workforce Identity. We started initially with AWS, then we added Confluence. We also migrated the internal rewards point feature. The entire migration is being done in a phase-wise manner. Currently, 15 applications have been migrated with only a few remaining that we use daily.

I haven't used the Lifecycle Management feature in Okta Workforce Identity. The decision to go with Okta Workforce Identity might have been due to the best customer experience and favorable long-term license deals.

I would recommend Okta Workforce Identity because it's a security standard. Two-factor authentication is always better than using user ID and password. The entire world is now dealing with data and we have to secure it as much as possible. For file transfer, we are using encryption and decryption. Similarly, for accessing internal applications or internal websites, I would recommend using Okta Workforce Identity or any related tool which can provide two-factor authentication as it's a standard nowadays.

I rate Okta Workforce Identity 9 out of 10.

One of the majorly used use cases for Okta Workforce Identity is the assignment of different SaaS applications, which are cloud-based, and using them with single sign-on. Users don't have to remember the password for each and every online cloud-based application. They just need to sign in with one email and password. This is one of the major benefits of using Okta Workforce Identity.

One of the best features of Okta Workforce Identity is its integration with different SaaS applications, which makes it a better product than the competitors.

The multi-factor authentication feature in Okta Workforce Identity is very good. It has its own verification app as well. It is very good in authentication, and we can use hardware keys, software keys, or any authenticator, majorly known authenticator app, for multi-factor authentication.

The provisioning and deprovisioning features of Okta Workforce Identity are very good. We can automate them as well, and we can provision users, groups, applications, and provision tools based on specific groups as well. The product is very good in that as well.

I believe that if we integrate the workflows section into the main Okta Workforce Identity dashboard, it can be very useful.

We have been using Okta Workforce Identity for about 4 to 5 years now.

In terms of the initial setup and deployment, I find it to be very easy. We have to set it up for the first time, and it has a very straightforward implementation. We have the pictorial and video guides on the Okta Workforce Identity websites on how to deploy it, how to set up employees, how to provision them, how to create groups, and how to set up devices. Each and everything is documented, and it's pretty much straightforward to use.

Okta Workforce Identity is a stable product. We had an issue with the Okta Workforce Identity dashboard once in 2023 when we had an outage, but it recovered in a few minutes.

We have never felt the need to contact the Okta Workforce Identity support team. It has been up and running. We had an issue with the Okta Workforce Identity dashboard once in 2023 when we had an outage, but it recovered in a few minutes.

We weren't using any single sign-on application or solution before choosing Okta Workforce Identity. This was our first product that we implemented in our company.

In terms of the initial setup and deployment, I find it to be very easy. We have to set it up for the first time, and it has a very straightforward implementation. We have the pictorial and video guides on the Okta Workforce Identity websites on how to deploy it, how to set up employees, how to provision them, how to create groups, and how to set up devices. Each and everything is documented, and it's pretty much straightforward to use.

I don't have the exact quotation or the exact pricing details for Okta Workforce Identity, but everything comes at a cost. However, when it gives you scalability and reliability, then I don't think the pricing matters.

I believe we have a lot of features in Okta Workforce Identity and I don't think we should be having more features in it as it's currently packed with a lot of features.

I believe we have a lot of features in Okta Workforce Identity and I don't think we should be having more features in it as it's currently packed with a lot of features. On a scale of one to ten, I would rate Okta Workforce Identity a nine out of ten (9.9).

We are currently using Okta Customer Identity as a managed service platform. We are building a platform where our customers can subscribe to different products of Okta Customer Identity, such as Access Manager, Entity Manager, and Okta Privileged Access. Our customers purchase subscriptions and create a PO number, which we use to perform technical implementations.

Okta Customer Identity is a SaaS-based application, making it easy to configure compared to competitors. It offers around eight thousand five hundred out-of-the-box connectors, providing an edge over other tools. It eliminates the need for configuring connectors using REST APIs as they are readily available. The Entity Manager is integrated with SSO, and Okta Customer Identity offers a wide range of protocols for federated single sign-on and token exchange. Okta Customer Identity also provides excellent documentation and training resources.

In Okta Identity Governance and Okta Privileged Access, some features are still being developed. Integration with Active Directory servers, Cisco routers, and switches is not currently available. Additionally, integration with platforms like DB2 and Oracle or SaaS-based databases is still in progress. These features need further development for full functionality.

The support from Okta Customer Identity is excellent, and I would rate it eight out of ten.

Okta Customer Identity is known for its easy configuration and deployment.

Okta Customer Identity is considered cheaper compared to other tools in the market, such as IBM and CyberArk products. Further details on costs would require consultation with our sales team.

I compared Okta Customer Identity with solutions like IBM Security Access Manager and CyberArk. While CyberArk is a fully functional tool with all features, Okta Customer Identity is more affordable and offers comparable functionality.

I rate Okta Customer Identity as nine out of ten. The Privileged Access Manager part is still in development but is expected to be in line with competitors like CyberArk or BeyondTrust soon.

In Okta Customer Identity, I primarily respond to application handling with around three thousand applications. This includes handling internal applications for permanent employees and third-party applications for contractors. I also work on certification renewal annually and the setup of SSO pages to enhance security.

The most valuable aspect of Okta Customer Identity is the server's reliability, especially for directory and node management. I set up different directories for traffic redirection, ensuring backup when a data center faces issues and maintaining seamless operations.

There is room for Okta Customer Identity to improve by increasing the reliability for the server end, creating more directories, and focusing on internal users rather than external or contract-based ones. Additionally, extending idle session times from ten milliseconds to at least forty-five seconds would be beneficial. It is also suggested that patches be applied annually rather than quarterly.

I have been working with Okta Customer Identity for nine months.

I would rate the stability of Okta Customer Identity as eight. It has allowed us to manage identity signals effectively, though some customers are resistant to certain procedures, making stability slightly challenging.

I rate the scalability of Okta at nine. I have a clear understanding of the architecture and processes involved, which allows for effective scaling to manage user privileges, application logins, and leveraging tools like Splunk for efficient data management.

We have a strong internal support system including application support, data center, and IDM teams. However, direct interaction with Okta's technical support is minimal as we typically manage internally.

Before using Okta Customer Identity, I did not utilize a different solution for these use cases.

The initial setup of Okta Customer Identity took about five hours and required a team of three.

We needed three people for deployment and now require about four people for maintenance, including rotations among five to six employees.

The pricing for Okta Customer Identity is very economical. It is much cheaper compared to Oracle Access Manager, and the company focuses on internal training to mitigate additional certification costs.

We evaluated Microsoft Azure as another option, but both Okta and Azure are quite similar in functionality.

Overall, I rate Okta Customer Identity as nine. Although there are some areas of improvement, its pricing and scalability make it a preferred choice for managing user identity and applications.

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 solution is used to eliminate a VPN, provide identity authentication, and single sign-on (SSO). We use Zscaler authentication to manage endpoint logins, endpoint report management, and single sign-on for applications.

The most valuable feature is the identity access authentication.

There is a need for Okta to provide an end-to-end solution without needing a separate product like Zscaler for multifactor authentication. Additionally, Okta should enhance its endpoint defensive capabilities, as we currently use BeyondTrust for Elevator Access Management.

I have been working with Okta Workforce Identity for four years.

The solution is rated as a nine in terms of stability.

Okta is not designed fully for scalability.

Okta provides good support. While we are unable to have it in-house, we can raise a ticket, and they support us well.

We utilize Okta and Zscaler for multifactor authentication.

The setup process is very user-friendly and has no issues.

Our internal team underwent training materials and configured the implementation successfully.

The pricing is very high, which is an area for improvement.

I recommend Okta Workforce Identity to others, particularly for mid-sized and large enterprises.

I'd rate the solution nine 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.

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.