Okta Platform Reviews

We use this solution for MFA and single sign-on.

It's our enterprise-wide identity management system. It identifies all of our users prior to accessing any of our applications.

It assures us that everybody is authenticated prior to accessing any corporate applications.

The most valuable features are multifactor authentication and single sign-on.

It's reliable and it does what it is advertised to do.

The guest user access could be improved. How do we authenticate people that aren't in our Active Directory?

In the next release, I would like to see passwordless access.

I have been using this solution for four years.

We are working with the current version.

This product is very stable and is one of our best applications. It's the most reliable application and it never goes down.

It's a scalable solution and we are able to add users as needed.

We have about 4,000 users and it's all employees and contractors within the company.

Every employee uses this solution every day, multiple times a day, and we plan to increase usage.

They meet our needs. 

We haven't had a problem with technical support answering any of our questions.

We went from using nothing to Okta Workforce Identity.

The initial setup was straightforward.

It was a week-long process to deploy.

We need one and a half persons to do the configuration, maintain this solution for administrators and the development.

We completed the implementation in-house.

We have seen a return on investment by using Okta Workforce Identity.

I can't discuss pricing.

Follow along with what Okta recommends.

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

I am not using the custom identity aspect; I use it only for customers and staff. We wish to sell the customer EIM because, at the moment, they have a SaaS solution. You can use Microsoft Azure to host Workforce Identity.

Okta is a very compliant solution, and it is easy to deploy.

It is not very interesting from a marketing perspective. For this, you can use open source solutions to reflect different groups.

Customer EIM is a new concept, and historically we use the customer EIM for the questionnaires or with focus. We have been using it for about 7 years.

It is a stable product.

It is a perfect solution in terms of scalability.

Technical support is excellent.

All the providers of EIM have the same licensing model. If you have 10 million users or customers of Okta, it is just one payment. However, it is costly in this case. The licensing model is unique to each user. Each user costs 10 euros. Therefore, if you have 10 million users, that's almost 100 million, so it is costly. The model is effective, however. Each user's identity is unique. It is cheaper for small companies and organizations, as they have fewer users. It is dependent on the evolution of your user base. It depends on usage per user, so the more sign-ins there are, the more expensive it becomes, so it works best for smaller companies from a financial perspective.

We considered Arribatec, which is a new startup solution in the market.

If you require identity solutions as a service, I would recommend it, but it is dependent on the use case. I would rate this solution 7 out of 10.

The primarily use of the solution has been for education and to support our Federation identification as well. We also use it for a Google IDM, in that you use it to segregate our Google DCB environment and provide for our engineers.

Overall, the solution works perfectly.

We especially appreciate that it's very easy to manage. For me, as a manager, it brings a lot of value for us and makes our clients very happy.

The initial setup is easy.

The solution really does have all of the features we need.

The pricing could be improved. Right now, it's a bit expensive. They should work to make it more affordable.

In general, the solution isn't really missing any features. It's rather complete. I can't recall anything that would need to be added into future updates.

I've been dealing with the solution for about a year and a half or something like that. It hasn't been too long.

The stability has been perfect. There are no bugs or glitches. It doesn't crash or freeze. It's performance is reliable. We're quite satisfied.

Being a cloud product, and like other cloud products, the solution can scale quite well. If a company needs to expand it, it can do so with ease. It's very accommodating.

Currently, we have more than 130 users on the solution.

I can't speak to the quality of technical support. I've never used them. I couldn't say if they are knowledgeable or responsive. I have no personal experience in the matter.

The initial implementation is not overly complex. It's easy. It's rather straightforward. A company shouldn't have any issues with the setup process.

The deployment is pretty quick. We had everything set up within a week or so. It's not a long, drawn-out process by any means.

The pricing is a bit costly. It could be lower.

We're resellers. We have a business relationship with the organization.

I'm not sure which version of the solution I'm currently using right now.

This, overall, is a very good solution. It can solve a lot of problems related to compliance regulations. We looked at this kind of solution as we don't have a PCI. It works well for us.

I'd rate the solution at a ten 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 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.

My primary use case is to have a single sign-on and to have identity access management. I'm the team management manager and we are customers of Okta. 

Having a single sign-on to all our applications.

With the device applications, when you are checking the logs, you can't hide the device and that's a feature that's missing. I'd like to see MDM source added. 

I have used this solution for a year. 

The solution is good on scalability and stability. 

The company has very good tehnical support and they respond quickly. 

The initial setup wasn't so easy but it wasn't too complex either. We had assistance from Okta for the installation. Implementation didn't take long, maybe two or three days but we had some issues with some applications, and we had to postpone our deployment for about two months because of that. There's no maintenance required. We have about 300 users dealing with the solution in the company and it's used daily. We have no plans to increase usage for now.

I think the approximate cost for the license is somewhere between $20,000-$21,000 a year and that includes everything. 

I think this is a good solution, I would recommend it. 

I would rate this solution an eight out of 10. 

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.