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.

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 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. 

Okta Workforce Identity is easy to use and has a lot of components.

The product's connector framework needs improvement. There should be automated aggregation and complete classification processes included in it.

We have been using Okta Workforce Identity for five months.

It is a stable product.

It is a scalable product. It provides flexibility to increase the number of users. Our customer environment has 5000 to 6000 users.

The initial setup is straightforward. We deploy it on the cloud. The product has good documentation to refer to for implementation. We require two engineers and one manager to execute the process.

The product has a user-based license model.

We evaluated SailPoint, IBM, and Oracle. Our customer migrated from Okta to IBM for more features.

I rate Okta Workforce Identity a five out of ten. If you don't have critical use cases and do not want a full-fledged IGA solution, Okta is a good product. However, if you want to use certification, access requests, and an extensive connector framework, Okta does not provide it.

I find the provisioning features and the integration with other applications useful.

The solution’s policies are difficult to understand due to the policy methods. They use authentication. The solution’s workflow is also difficult and not very active. They need to have proper documentation on it. In the next release, I would like to see the workflows being more digestible.

I have been using the solution for six months.

The solution is stable.

The solution is scalable. We are a medium-sized company and we use it full scale. There are around 200 users for the solution. It also requires two admins.

The solution’s customer support is fast, reliable, and helpful.

We didn’t do the deployment because it was difficult. We had to rely on an in-house team.

Our in-house team deployed the solution.

The solution’s pricing needs to be reasonable. You are dealing with a lot of components and the pricing is component-based.

I would rate the solution an eight out of ten. I am pretty much satisfied with the solution since it works properly. Anyone looking to implement the solution needs to read the documentation carefully. They also need to have a bit of experience before that.