Okta Platform Reviews

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. 

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.

We've been using this solution for SSO and consolidation of IDs.

This solution brought us the SSO perspective, and this is the main reason we're using it.

The only thing I like about Okta Workforce Identity compared to other solutions in the market is that it's an easy resource that you can get, even if you're working with many users, but there is a lot to learn about it.

There are many things that Okta has to improve on. I understand that Okta has a lot of apps, like any other provider, e.g. Microsoft apps, IDP apps, or cloud identity apps.

The problem with Okta is that they create the app and they never update. In this fast-paced industry where versions keep getting updated, Okta is really slow at times.

None of the Okta applications that they create, for example, in my case: I have used the cloud identity of Microsoft apps and now I'm using the off tabs. What I found is none of the single Okta apps that we have worked and did not create an issue. They are not fully mature. So it's that aspect that can be improved, which Okta is investigating. Their application support and not having updates for those applications also need to be improved. These are the things that surprised me and I was not able to understand from Okta.

Okta's customer support should be improved.

Okta should work with certain providers, e.g. the Google cloud, the AWS cloud, the Microsoft cloud, and they should evaluate the integration point because what happens is if your organization has SSO which relies on Okta, all of these three clouds and the Okta app are far from perfect. You are not able to get the right setup based on how your security is trying to define it vs what the application can support. You'll end up using the default interface Okta provides with those apps.

I understand Okta could say that if they shouldn't worry about it because if AWS wanted to support Okta, then AWS should be the one providing us the app and support, but Okta should try to understand the users, do surveys from the different automation using Okta, and use different apps because those apps are very critical. They are far from perfect, so Okta has the worst implementation.

I've used this solution in the last 12 months. We've been using it for six years.

This solution is stable and reliable. We didn't find the solution itself hard to use.

The scalability of this solution is bad. Scalability has two or three different meanings to it.

Is it scalable from the infrastructure side of it? The answer is yes.

Is this scalable from the business perspective? The answer is no. For example, the B2B and the B2C solutions that others provide, those aspects in Okta are completely lacking.

For example, if I have the Microsoft Azure Active Directory, I have the B2C, B2B, and the phase rate, so I have a way to not only support my enterprise but my end customers in a very fast manner. In the case of Okta, that whole path is a nightmare to work with.

I didn't like Okta's support. They say they have very good support, but the moment you create a ticket, they will tell you that they provide the app, but they cannot provide support because we connected the app to another environment, or to another side of the spectrum. This seemed very odd to me.

First, we are using the application you specified, then you say you cannot support this application just because the value provided is outside of this application, so you cannot troubleshoot or help us to troubleshoot if we open a ticket. Every single time it's a chicken and egg type of situation. From that perspective, Okta's support is horrible.

The setup was straightforward. Nowadays, all the other IDPs are the same way, too. I didn't find a single IDP that had no experience at the level, and all of them can stand up at the same time, within the same time frame.

With Okta, on the other hand, the requirement to have the ID server in between, whether it's the cloud-based ID server specified, or the on-prem base, like ours: It's on-prem, but what I found was that we were not able to do it even after following all the guidance unless we had a dedicated Okta person to help us do it. It was a different situation with Microsoft and cloud IDP which were easy to set up, as we were able to do it ourselves just by following the documentation.

We implemented the solution through an integrator consultant. They are fine. They are doing the job on a daily basis.

This solution is costly.

With Microsoft, you get the exact same information that Okta gives out of the box: free, because that's what Microsoft does, and even if I compare to other cloud IDPs, with Okta, access may offer free access for startups, and if you have fewer users, it's okay. Pricing is decent. The moment you talk about the enterprise level, for example, we were talking about implementing Okta across the US with multiple customers, and the cost they gave us was two million dollars. The cost is not justified for the single assets of this solution, so Okta is bad in those terms.

We've been evaluating Microsoft Azure Active Directory. It's still in the POC phase, and it's been three or four months. We have very particular requirements, e.g. a mix of multiple IDPs with Okta, and Azure Active Directory is one of them, but that is the only one where we don't have the solution. We are trying to do the POCs first to ensure that they are able to meet our needs.

The reports I downloaded were very informative. The things that we were trying to do is generally the One ID and software entitlement. Our customers find them more useful than the Microsoft Azure side of it. They know that the functionality exists and they are able to use that functionality, but the intuitive nature of managing the entitlement was not there. We also had a requirement where we wanted to mix the Okta in between, for the SSO, so I was trying to collect as much information as I can get and that information was helpful.

Whenever you search for the Okta documentation, for example, if we search for cloud IDP and Microsoft-related documentation, it's only on Microsoft's site we get the help we need, including help from the community. Okta's community, when you Google it, is lacking because it only contains help or information about Okta products because Okta users are only able to use the product in a standard way.

This surprised me especially because Okta has such a good name, but the bottom line is, if you ask me as a decision-maker or the one who influences decisions in our organization, if I was going to choose Okta as our SSO provider, my answer will be flat NO.

The initial implementation of this solution took three months. It's a very simple and standard implementation, so that's never been a problem.

A hundred users are currently using this solution in our organization. It doesn't require heavy maintenance.

Working with Okta can be restrictive, and this is where Okta doesn't shine.

This solution is being used extensively in our organization. Increasing its usage will depend on whether they are able to convince the Infotech folks, and that's what's happening.

The advice I would give to others looking into implementing this solution is for them to first try to understand it. They should not confine themselves to selecting Okta, thinking that it's the end solution. They should look at their future needs too because once they implement Okta without considering their future needs, they will have to do a lot of hacks and tricks. Before they even delve into Okta, they have to first think about their future and how much this solution will cost in the long run.

This solution meets the need, but that's all, so I'm rating it a six out of ten.

We use this solution as a platform for identity and multifactor authentication of the entire platform which is integrated with the active directory so cell phones can be used for multifactor authentication. We have multiple domains and two segregated businesses. We onboard third party applications to Okta and users that need specific applications. The two groups have access to the 11 applications that they need.

The key feature of the solution is the multifactor authentication itself. The app provides a seamless way for users from anywhere to be able to connect. It also offers risk intelligence in terms of track analytics which can determine suspicious log-ons and lock them, preventing breaches. 

There are sometimes issues with the voice authentication methods when users receive calls and they're not able to get the verification codes. That needs to be improved. A troubleshooting dashboard would be helpful in terms of pinpointing issues as opposed to running a search query switch. 

I've been using this solution for three years. 

In general, stability is good, although occasionally we do encounter issues and need to log a call with Okta support in order to resolve the problem.

This solution is very scalable. We have about 15,000 users globally and several different domains. The solution also provides for cross domain functionality. We've adopted this solution 100%. 

Initial technical support is not very responsive, it's only after escalation that we get proper support.

We primarily deployed the Okta servers in the on-prem environment and then we integrate them with our IT Directory. From the Okta side, they configure the kit and perform the  configurations and the IQ. Deployment is quite straightforward. We had around 15 people helping with deployment, some from governance and the others from the our identity and security team. The entire implementation took around six months for our 15,000 users. 

It's important to have a good plan in place, identify your needs and make sure you have a good integrator. 

I rate this solution a nine out of 10. 

We use this product to control access to applications.

The most valuable features are identity management and OpenID.

At this time, Okta is doing really well and covering every aspect. Everybody in the company knows Okta and how to work with it.

The support for YubiKey is really good because you don't actually have to type in your username and password. Everything is taken care of, automatically.

There are some issues with the interface that can be improved.

I have been working with Okta Workforce Identity for more than three years.

The stability is good.

This is a scalable solution and we have more than 10,000 users.

They provide a lot of support but there are still places where we get stuck.

Prior to Okta, we were working with Active Directory.

We are using Azure for authentication and I really like Okta compared to that. Okta is more extensive than the product from Microsoft Azure.

The initial setup is really easy.

We have three people for maintenance.

The price of this product could be lower. It's just like Box, where when it first came on the market the price was lower. Once people started using it, the price increased.

I am looking forward to seeing what Azure Active Directory has to offer. Microsoft is giving Okta competition in terms of pricing and other features.

In summary, this is a good product but it is not perfect. There are some areas that need improvement.

I would rate this solution a nine out of ten.

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.