Okta Platform Reviews

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.  

Our organization only uses Okta for single sign-on. Everybody is working from home, so we need a multi-factor authentication solution for remote users. We have around 70,000 users. 

Okta integrates well with other solutions. Once you have integrated an application into Okta and onboarded a user, they will be onboarded for just-in-time provisioning. 

The error logging could be improved. Okta doesn't provide enough details when you are troubleshooting an issue. It's often difficult to fix it from our end, so we always need additional support from Okta.

I have worked with Okta for two years.

I rate Okta six out of 10 for stability. We don't see many bugs, but the product doesn't support some of our custom requirements. We have to submit feature requests that they implement later. 

I rate Okta six out of 10 for scalability. In January, they were doing something on their side, and a cell was down. The US was completely down, and most users had problems logging into. Okta confirmed that auto-scaling was not happening properly from their end.

I rate Okta support eight out of 10. 

Positive

The company used RSA before I joined. I believe they switched because they preferred a SaaS platform, and RSA was late to adopt this model. RSA is excellent as an on-prem solution, but they didn't transition to the cloud until later. 

I rate Okta eight out of 10 for ease of setup. It's a SaaS product. You can configure it in a few hours. It takes additional time if you use on-prem agents. Active Directory has some other agents that must be integrated. It will take additional time. Otherwise, it won't take much time. You need three people at most to deploy it. Usually, one person deploys the solution, and two other people are on standby. 

I rate Okta Workforce Identity eight out of 10. 

We use Okta Customer Identity mostly for SSO (Single Sign-On), and we also use it for user and application management, in particular, for SaaS applications.

Okta Customer Identity improved the company when we used it for user identity management because we were able to manage our user provisioning and de-provisioning through the solution very efficiently.

If users are joining the organization or if they're in the onboarding phase, we can take care of the applications and all other requirements through Okta Customer Identity.

When users are leaving the organization or when they're in the off-boarding phase, we use the de-provisioning feature in Okta Customer Identity for those users.

We're very happy with the solution and its features.

The most valuable feature of Okta Customer Identity is its SSO because it's very easy to use and it's user-friendly. Even the admin portal of the solution is very user-friendly, and you can walk through it with ease.

Okta Customer Identity is not a complicated solution, and even the workflow automation feature is very, very easy to understand.

What I'd like to see improved in Okta Customer Identity is the process of exporting users. Currently, it lacks this feature, and you have to use a third-party tool to export users from the group. Exporting users should be very easy, though I did notice that Okta Customer Identity is being upgraded from time to time, and I've been seeing much improvement in it compared to the previous years.

I've been using Okta Customer Identity for three years now.

Okta Customer Identity is a stable solution.

Okta Customer Identity is a scalable solution.

Okta Customer Identity has good technical support, and on a scale of one to five, I'm rating support a four.

I would rate the initial setup for Okta Customer Identity as four out of five. Deploying it was very easy.

We deployed Okta Customer Identity with the help of a third party. We deployed the solution and received help from their support team, which was very supportive during deployment. We were able to deploy the whole environment in a very, very easy manner. We just opened a ticket then the Okta support team helped us in setting up the solution.

I have no information on Okta Customer Identity ROI.

I'm unfamiliar with the licensing costs of Okta Customer Identity.

I evaluated Microsoft Azure AD.

I'm using the latest version of Okta Customer Identity.

My company has a partnership with Okta Customer Identity.

Two thousand people use Okta Customer Identity within the company, mostly engineers. Three people take care of the deployment and maintenance of the solution: one junior engineer, one system engineer, and one architect.

There's a plan to increase the number of users of Okta Customer Identity in the future.

My advice to people looking into implementing the solution is to go ahead and implement it. Okta Customer Identity is a very good technology to work with, with a very knowledgeable support team. You'll get instant support, and the team is very supportive.

My rating for Okta Customer Identity is eight out of ten. I'm not scoring it a ten because of some gaps. It's fine for me right now, but in the future, I would like to see improvements in the solution.

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

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.

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.

We are using Okta Customer Identity for single sign-on. For example, if there is an organization that wants to have a user use one credential, user name, and password, and log into multiple applications. Then in that case you can use the Okta Customer Identity single sign-on tool.

The most valuable features of Okta Customer Identity are there is no infrastructure cost, integrated, has plenty of documentation, and is user-friendly.

There is an access request system that is very limited access to the systems available for end-users. The access request should improve in Okta Customer Identity.

I have been using Okta Customer Identity for approximately two years.

Okta Customer Identity is stable.

I have found Okta Customer Identity to be scalable.

We have many people using this solution.

The technical support of Okta Customer Identity is very prompt in responding.

The initial setup of Okta Customer Identity is easy. Once we have the application registered we can use it. It does not take long.

Our solution team implements the solution and since it is a SaaS solution it is simple.

Okta Customer Identity is not an expensive solution.

I would recommend this solution to others.

I rate Okta Customer Identity an eight out of ten.