Okta Workforce Identity Reviews

I did about six months' worth of work on it. It was more towards getting our lab set up, getting the certification done, etc.

It makes it very easy to onboard and offboard accounts. When someone quits, one of the hardest things for an admin to do nowadays is figuring out the 37 accounts that this person had and getting rid of all of them. With Okta, it is not that difficult. You can eliminate a lot of that admin time in one shot, which is important on the security aspect of things. If you miss one or two accounts, they can backdoor you.

Its integration components are most valuable. It integrates with everything in some way. There are some products, such as O365 or AD, with which it completely and 100% integrates. So, you can seamlessly create accounts across the board with some of these products. For some of the products with which it doesn't completely integrate, you can do some kind of interfacing. 

The only aspect in which it can be improved is that the interface could be cleaner. I found this even when I was trying to do my certification exam because the certification is hands-on. You find yourself fumbling around a little bit to find simple things. This happens even when you start to get familiar with the product.

Stability-wise, it is pretty rock solid. Its stability also depends on your access to the internet. We didn't see one instance where we felt that we were going to lose access. It is completely or 100% cloud-based.

We've seen Okta scaled to thousands and thousands of endpoints. You would have a couple hundred thousand before you go, "I wonder if that would work". Even then, you can run different instances based on geography, and they would tie in together. So, its scalability should be one of the least important concerns for a company.

My advice would be to look at the entire spectrum of your web apps as well as your on-prem integrations as you start to plan. If you don't plan it out initially, it gets really hard to fix some of these things at the backend. You should get a good, firm list of all the applications that you would like to integrate with and see which ones integrate seamlessly. From everything that we've read up on, they do a lot in terms of API support. So, for what they don't provide readily or out of the box, they could probably customize an API.

I would rate it a strong eight out of 10. It was the best product that we saw in its space. I didn't do a lot of comparisons on it.

We find the solution to be reliable for our customers and it is nice that it is cloud-based and can be accessed from anywhere. It allows for smooth administration. The dashboard is so simple and the solution can be integrated with other vendors, even Cisco. This is why we have chosen to be resellers of the product. 

I do not see much room for improvement. I have not encountered any issues with the solution, though it may be worth checking this with the technical team involved in its implementation. 

This said, it is scalable for midsize companies and infrastructure but, owing to the regulations we have in place in Egypt, not every enterprise-sized company. This means the solution did not comply with everything in the financial sector, such as with our central bank. As such, one who is working in the financial sector must resort to another solution or, at the least, another one in addition to Okta Workforce Identity. 

The solution should have greater on-premises availability, not just cloud and more package customization in its processing. 

I have been using Okta Workforce Identity for six or seven months.

The solution is stable.

The solution is scalable for midsize companies and infrastructure. 

While I can't speak on behalf of my colleagues, I have not made use of technical support. 

The pricing is reasonable.

While I don't have specific advice for those looking to implement the solution, I feel a visit is warranted for one who needs a cloud solution for SSO and identity management. 

I rate the solution as a seven to eight out of ten. 

We are an authorised reseller partner

Its simplicity and integration with various vendor-agnostic platforms are the most valuable features. 

API Securities Solution

I have been engaged with Okta for more than 2 years, have seen the latest version.

It is highly stable. They claim 99.9% uptime. We never came accross downtime and performance issues

Okta is not only a single sign-on platform but also Life cycle management, the core of the Identity Management platform. Okta access gateway can publish on-premise legacy applications to the cloud. 

They are very good. The Okta system engineers involved in presales engagement have sound knowledge on Okta platforms and IAM in general. What I have noticed personally is that Okta provides them with extensive training before assigning them to the Job. It helps them in understanding the technology well before starting with the job.

Its initial setup is straight forward. Okta tenant creation can be done quickly. Adding users and applications to the okta platform has customer dependabilities. Integration and going live with O365 also takes a little bit more time than other apps because of internal rollout and user training. It is not an Okta problem but needs customer Microsoft teams active involvement 

Okta Service Partner

I would recommend a phase-wise approach and not doing everything in one step. You can start with the basics of single sign-on and MFA and then proceed to life cycle management. I would also recommend starting with the lest critical applications and then add critical ones to the SSO platform. It is a journey, and we need to start small and slowly migrate it. Adaptive MFA provides proactive defence against login and credential abuse.

I would rate Okta Workforce Identity a ten out of ten.

We primarily use the solution to access cloud solutions and VDI. 

The most valuable aspects of the solution are the integration with external websites one-factor authentication.

The solution lacks an on-premises deployment model so it can't offer a hybrid solution. It would be ideal if clients had options that weren't just cloud-based.

The stability of the solution is fine.

I've never contacted technical support. I've only ever used web pages to assist me with questions, and that has been enough.

We previously used Workspace One Access Solutions from VMware. In fact, we're using it as well as Okta, so we never really switched.

The initial setup is almost completely straightforward. The identity action is complex, so it makes it just a bit difficult.

Customers should use an integrator to help assist in the initial setup.

This solution is very good. Okta is, in my opinion, one of the leaders at the moment on the Polish market. However, there is some limited usability because of the requirements.

We use the cloud deployment model.

I'd rate the solution nine out of ten.

• SSO integration with an on-premise Active Directory environment
• Universal Directory synchronization and leverage UD to integrate with other cloud federated applications
• O365 SSO integration

O365 integration, moving away from straight LDAP integrations for applications that reside in the cloud to true SAML functionality. Provides better security posture by using SAML and MFA.

• UD
• SSO functionality
• MFA and Adaptive MFA functionality
• Ability to link multiple Directory databases with UD

UD attribute mapping, Okta group rules, and dynamic usage could use improvement. More in-depth functionality and features to integrate with RADIUS solutions.

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.

It has got a big network of apps that easily integrate into it, making deployments a lot faster than traditional identity platforms. So, the use case will be companies that are looking to be on a cloud journey for cloud adoption strategies. It also suits companies that have on-premise applications and would like to make them web-based, essentially, access them on one portal. Thus, allowing companies to ensure that they can pretty easily manage access to these applications by their users.

The ease of deployment, ease of use, and speed of delivery is what I like about Okta Workforce Identity.

It is very easy to use. For a lot of software, you need to be trained extensively and have a very technical background. Okta Workforce Identity is quite simple.

You can integrate any software into Okta. They've got a network of 7,000 applications that easily integrate into it.

It would be pricing, which is a tough one because it goes against Microsoft. A lot of companies say they're a Microsoft partner, and they get all their software for free.

Okta is like a luxury product, and it's not the most affordable one. I would say if they could work on pricing, it would help. Other than that, they've done great strides in developing a product that is really good. The companies that do see the value tend to invest in it.

I have been using this solution for the last two years. 

They're really great stability-wise. The last year they've had like 99.9% uptime. They're really good for SLAs and things like that.

Scalability is probably one of its best attributes.

They're pretty good. I know they're a big organization, and they have a lot of clients. So, it's a place where they're always looking to improve, but from my side, it's been really good.

It's pretty straightforward. If you need it, you get great support from Okta as well.

They provide a lot of datasheet information and step-by-step ways to deploy the solution. They're doing really well on this front.

For deployment, right now, it's me and one more person. If we need any additional support, we get it locally in South Africa from a distributor who has a technical team skilled in Okta. Whenever I need more support, I go to them or directly to Okta, or the client can pay yearly fees for additional support if they need it.

It could be a bit too pricey for small companies. Okta Workforce Identity can add a lot of benefits, but smaller companies may not have a lot of applications that need to be managed by Okta Workforce Identity. In larger organizations, there are more departments, applications, and users to manage. Okta Workforce Identity adds a bit more value to those bigger organizations.

In addition to standard licensing fees, there are also additional costs for things like additional support and so on.

Okta Workforce Identity can be suitable for smaller companies, whereas Okta Workforce Identity is suitable for a bit bigger companies, but they serve different purposes.

Essentially, Okta Workforce Identity is for medium and large companies. I would say for companies with at least 50 users, but then these companies should really see the value in Okta Workforce Identity. I guess when you start talking about 200 employees upwards, that's where Okta Workforce Identity really starts creating a lot of value.

Okta has recently created a business value assessment. Those who are starting the process and looking into Okta must be open-minded to the value assessment with the Okta team or with the person at the company that is selling the solution to them. Just be patient, see the value, and not be so caught up in thinking that Microsoft is a great product. I think Okta is way better.

I would, a hundred percent, recommend Okta than Microsoft. Essentially, Microsoft wants you to stay within their stack, whereas Okta is neutral. You can integrate any software into Okta or any application, whereas Microsoft takes a bit longer, or they may not support the integration and so forth.

I would rate Okta Workforce Identity 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.