Okta Platform Reviews

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. 

The basic idea behind the Customer Identity product is to put in multifactor authentication for clients to make sure that people are properly managed.

It is normally used by people involved with marketing technology.

What it's done for our clients is it's reduced the number of staff they need in order to manage their campus and their partner community services. For example, users can automatically reset their own passwords if they need to, and they've got multifactor authentication so they can easily access the service and they're properly identified.

Using this product helps with the relationship between users and their account managers as well, because account managers can be sure that people are getting access to the services they need.

We are not using all of the features. We primarily use it to manage the community onboarding and offboarding of users, and it's quite a simple solution for that.

The initial setup could be easier to do.

We implemented Okta Customer Identity approximately two years ago.

This is a very scalable solution. We currently have 150,000 users.

The technical support is very helpful. They provide you with a customer success manager and they've got access to all of the resources needed to solve problems.

We do most of our own support but when we need help, we can easily get access to someone.

The initial setup is difficult because you're setting it up with your own portal. This means that you've got to have the code in the portal to do the integration, which is what makes it a little bit more difficult. That said, there is a lot of good guidance available online.

By comparison, Okta Workforce Identity doesn't require any technical skills whatsoever, but if you're a developer, then you will be developing your own code.

It is probably best to use a third party to help with the deployment. You can do it yourself but it's a steep learning curve.

This product is quite cheap on a per-user basis. We pay 23 pence (approximately $0.30 USD) per user, annually, for 150,000 users.

My advice for anybody who is implementing this solution is to make sure that it is properly prepared, as a project. Good preparation is needed so do your homework.

I would rate this solution a nine out of ten.

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.

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. 

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.