Okta Platform Reviews

We are a solution provider and Okta is one of the products that we implement for our clients. I am a solution architect and help to design the system.

Most of our clients have a hybrid architecture where they want to use a single sign-on. They have some applications on-premises, whereas others are on the public cloud. This means that they have a two-tier or three-tier architecture.

Our clients are happy because prior to implementation, they had a very distributed architecture. Okta has allowed them to consolidate with respect to identity management, which increases their operational efficiency.

This product has the features that every customer is looking for.

The most valuable features are ease of operation and visibility.

This product is easy to deploy and easy to manage.

There are cost benefits to using this solution.

The integration with third-party tools needs to be improved. Mainly, the open-source APIs for Splunk would be helpful, as that is where they aggregate most of the data. If this process can be streamlined then it will definitely help.

I have been working with Okta for the past three years.

This is a stable product.

This solution is scalable. Our clients are large, Fortune 500 businesses.

Okta has very good support and I would score them high, at nine out of ten. I am definitely happy with them.

Prior to working with Okta, our clients had native solutions.

The initial setup is straightforward.

We currently have one customer deployed on AWS and another on Azure.

I am the solution architect and our in-house team does the implementation.

As part of the process, our clients did a couple of POCs. Symantec was one of them, Okta was another, and there was a third product that they evaluated. During this process, they had success criteria defined, and Okta did well with most of it.

The metrics included the operation and cost benefits, the business value, and the support.

Every customer has a different need and a different requirement. For anybody who is considering this product, I think they should do a pilot POC to make sure that it works well in their environment. 

I would rate this solution a nine out of ten.

We mostly use it for MFA for logging into our Windows RDS environment and a web-based application called Tableau. We are using the latest version.

The MFA part is the best. MFA provided most of the security that we were looking at with respect to the second level of authentication. Okta Workforce Identity provides a number of options with respect to multifactor authentication, such as the app, phone call, and text. These options provide different ways of logging in for users, and they were a lot more than what we needed. This is certainly a very good feature of Okta Workforce Identity. 

They also have single sign-on (SSO). When we bought Okta Workforce Identity a year and a half ago, I was also looking at SSO, but not much documentation was available for SSO. The documentation for SSO should be a little more robust for somebody who is implementing it for the first time. 

I have been using Okta Workforce Identity for almost one and a half years.

It is stable. I never faced any issues with its stability.

I have not scaled it much. The company for which we implemented this solution is into data mining or data analytics. They had multiple users. Most of the users were data scientists. I was the only one looking at it in terms of management.

There were a couple of occasions where I needed some support while setting it up for our RDS environment. Their technical support was educated enough with respect to the product. They were able to help us out and resolve the issue pretty quickly. I would say they are good on the support part.

Setting up the MFA for Windows RDS was very straightforward. Using it with Tableau was not very straightforward. It was a bit complex, but the documentation was handy enough to set it up.

I believe it competes well. The pricing is pretty competitive. I know that Microsoft also provides something similar with its MFA and identity services. 

It has been sufficient for our needs. I haven't seen any issues, so I would say it is a good product. If there was anything, the users would have complained, but I haven't received any complaints with respect to Okta Workforce Identity from the users. 

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

We are using this solution for access management and user provisioning. We are also using it for user and group synchronization and as a password for authentication.

The pass-through authentication is very useful. You don't have to set up another ADFS. Instead, you can just authenticate your resources for services from the cloud to AD on-premises through the pass-through authentication. There is no password hash saved on the cloud, which is the part that I like the most.

The functioning of Azure AD Connect for both user and group synchronization is very smooth.

I would like to see the provisioning simplified. When it comes to certain tasks, such as where it is activated on-premises, Azure AD is simpler than Okta.

SSO functionality needs better client support.

I have been working with Okta Customer Identity for two years.

We have had no issues with respect to stability.

The scalability is good.

I have been in touch with the technical support from Okta and they are very good. They answered my questions quickly and supported me very well.

The initial setup is straightforward.

Once we started, we received help from the Microsoft team and it was really good. We were able to complete the installation easily.

I would rate this solution a nine out of ten.

SSO and MFA: To extend Identity Authentication on the existing IAM identity and account operations to the multiple domains for administrative and help desk personnel. Improve consistency of the identity management processes across the organization and improve compliance with governance mandates.

The access management with Okta revolves around the establishment of a single authentication store (reducing the number of accounts), which will allow the migration of existing applications to federations, or a common identity store. It will also establish a suite of centralized authentication services that can be used for future applications and systems platforms.

• Enabled MFA to access federated applications as well as increased user satisfaction through improved provisioning times and more reliable processes. 
• Reduced costs associated with paying for AD accounts for customers who use corporate applications (currently 4000+ customer IDs exist within the AD forest – these require a license at a substantial cost to the organization). 
• Increased productivity through centralization of IAM Authentication - Authorization operations to a single tool (ISIM), and better operational resiliency with distributed administration (Common tasks can now be handled by a more diverse set of individuals across the organization.

SSO and MFA for improved end-user experience, and protection against password spray attacks, account password self-service. Extend Identity Authentication and authorization management operations. Extend the existing IAM identity and account operations to divisional administrative and help desk personnel. This improves the consistency of the identity management processes across the organization. Obfuscating the AD account infrastructure from the application infrastructure to reduce risk and vulnerabilities associated with tying externally facing applications to corporate accounts.

• Passwordless authentication. 
• Integration with the user provisioning infrastructure to track all entitlement changes; simplify the modeling of the role and access definitions at every stage of the user life cycle.  
• Automation of the entire entitlement and role review process, in alignment with business needs and requirements as stated by business leaders and managers. 
• Oversight in the form of dashboards reconciling and centralizing information for immediate insight into the status of access reviews and certification processes.

3 years.

They work really well.

I did not have another access management solution in place prior to implementing.

It was straightforward for access management with SSO and MFA. It was complex to implement password synchronization between AD domains.

We implemented directly with the solutions provider.

We evaluated IBM Access Manager but decided to go with a cloud-based product.

Intergated on-prem and cloud applications on multi-tier domains and user identity accessing applications hosted on cross domains. Full fleged automation using AD and Okta groups for app assignment. 

Lifecycle Management of apps on our Okta tenant. 

• Central administration of Apps
• Auto activation of user accounts/ Just-In Time Provisioning
• Global App availability
• Less or No Administration required

1. Active Directory Sync, as its useful for pre-assigning apps, can also be used for de-provisioning apps for exiting users

2. Shared apps with common password can now be managed centrally without revealing the credentials

3. User and Apps Management

4. Desktop Single Sign On

5. Auto-provisioning

6. Flexibility to integrate In-house applications

7. Password Self Service

8. Support non-domain users

9. Group based app assignment (okta, AD, pushgroup)

10. Adaptive MFA

11. Workflow for app requests

Command line access

Reporting

Since 2015

It's very stable we have 99.999% uptime on the base

Very high and secure, we have more than 170+ apps secured for sso

Customer Service:

9 out of 10

Technical Support:

9 out of 10

Yes, we had previously used a different solution which was replaced by Okta. Non-scalability was the major drawback of our previous solution.

Initial setup is straightforward, simple and easy to manage

Some apps needed assistance from Okta support team.

Setup is simple if you are an AD admin, cost comparison is nominal compared secured access

KB article from Okta is very detailed just spend some time on the okta

The primary use case of this solution is for access management, multi-integration, and passwordless access.

The most valuable feature of this solution for most customers is access management.

There are also some different views on Biometrics.

This solution would be improved by adding more biometrics features. One example is Cyberside Biometrics.

The technical support is good but needs to improve in their response time.

In the next release, I would like to see biometrics, multi-factor authentication, and to rely more on the mobile or something different on CyberSide.

I have been using this solution for one year.

Normally we deploy it on public Cloud, so it should be scalable.

I have been told that it's quite easy to integrate on Cloud. The scalability then depends on the third-party Cloud provider.

Our latest customers have over two hundred thousand users in a medium-sized company.

The technical support is good but not very responsive regarding my needs in getting details. They are difficult to reach and to get them involved.

I was not a part of the initial setup, but the feedback that I received was that the initial setup was quite straightforward.

Normally we do the implementation ourselves. We are one of the largest integrators worldwide.

My advice to others is to be aware of their current infrastructure.

The integration points have to be very clear to the customer to facilitate the main integration. Otherwise, it makes things very complex.

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