Okta Platform Reviews

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.

We implemented this solution for all employees within our environment. So, the entire single sign-on is through Okta for all of our employees through all applications.

Okta enables us to authenticate my users on cloud and SaaS applications such as Workday through Okta workflows.

I would like for the onboarding process for new solutions to be simplified because, right now, it is a very lengthy process.

We experienced some technical glitches that need to be resolved. 

I go into further detail below in the 'stability' section.

We implemented the solution one year ago.

The solution is pretty stable but we have experienced some glitches. We use Zscaler for our security encryption protection. Whenever Zscaler expired, Okta would stop working. We were able to fix this by storing the credentials and local mission that that we would be able to authenticate without Zscaler.

The solution is scalable both on-premise and on cloud. We currently have 36,000 users.

We have not had any major challenges over the past two years; however, they do offer quality customer service to all tickets.

The initial setup was straightforward.

We had a partner help us which made the implementation even easier. We have also outsourced a support party, Data Consultancy Services, to manage the solution for us - they have about three to four engineers manage the solution for us.

We are able to look at our ROI from this solution as an intangible benefit. The solution requires a lot of human capital but offers us security so in our opinion we have received a high ROI as this is something that we have planned for and invested in.

This is an expensive solution but the security makes it worthwhile.

I would rate this solution an eight 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.

We are using Okta for authentication. It provides identity. We are using it as an identity provider. Single sign-on is the primary use case here. We use it for our customers and our employees.

I'm using it as a single sign-on. Pretty much it is solving my purpose of having to not remember so many passwords. 

It is very seamless. You have access to ten different apps, which are hosted on-premise or in the cloud. A single sign-on really helps me to make things faster.

It s easy to set up.

The solution works well. I can't speak to any areas of improvement. 

In the future, we'd like to see the product implement more security features, like, for example, zero-trust.

We've been using the solution for the last three years. 

The product is very stable. There are no bugs or glitches and it doesn't crash or freeze. it's reliable.

It's a cloud service, so you pay for the license and you will get that level of entitlement. Scaling is never a problem. Just you need to pay for the extra subscription. That's all. 

We have 8,000 employees that use the product currently. 

It's been used quite regularly, especially during the pandemic when many people had to work from home. 

I have not used any other solution, although I do know there are many other players in the space. 

It's a cloud service. The setup is just a touch of a button. It's very easy for an end-user to use it. For administrators, there might be a few other things they need to carry out, however, for end-users, it's just a touch of a button. Nothing is needed from the installation perspective.

I'd rate the solution four out of five in terms of ease of setup.

I'm not involved in the procurement and I'm not maintaining it, therefore, I am not really sure about the cost.

I'm just a user, just an employee who is using this identity provider, and it is completely managed by our administrators.

I'd recommend the solution to other users. 

I would rate the solution eight out of ten.

This solution has a lot of capabilities and features. 

The cost per user for this solution is really high and could be reduced. 

We have experienced some challenges in integrating this solution with Scope and Cognito. 

This is a stable solution. 

This is a scalable solution. 

We have been satisfied with their customer support.

Neutral

I would rate this solution a nine out of ten.