Okta Platform Reviews

We use the solution to give access to the server. It verifies and allows users to access the server.

The product is easy to use. I just have to click on the Okta app on my mobile. The verification takes two seconds. We need to verify once we start the software because we use single sign-on.

The stability could be better.

I have been using the solution since April. I am using the latest version of the solution.

I rate the tool’s stability an eight or a nine out of ten.

Around 2000 to 3000 people use the product in our organization.

The deployment was done in-house.

I would recommend the product to others. It is a good solution. Overall, I rate the tool an eight out of ten.

We use the solution for our single sign-on applications. It resolves password issues.

We use it for authentication and 90% of our SaaS app. 

We use it for on and off-boarding users. It syncs with our on-premises master directory to set them up and take them off.

We like that the solution helps us to streamline multifactor authentication.

It's got great SSO and good provisioning and de-provisioning. 

The product is easy to set up. 

It is stable.

The solution can scale very well.

I've been pleased with its capabilities overall. 

Support could be a bit faster.

I've used the solution for five years. 

The solution is stable. I'd rate its reliability ten out of ten. 

It's extremely scalable. It'd rate the solution's ease of expansion ten out of ten. 

We have 1500 users on the solution currently.

Support is good. However, sometimes it takes them a bit longer to deal with issues. 

Positive

We previously used a different solution. We moved to Okta as the GUI is very user-friendly, and the solution is simple to use. 

The initial setup is very easy. It's not complex. 

The deployment took a matter of three to four days for our hybrid setup.

K+Okta's team helped us deploy the solution. They made it very easy.

We have gotten an ROI in terms of time savings. We've seen 20% to 30% ROI, as it is saving us a lot of time. 

The pricing is a bit expensive. I'd rate it four out of ten in terms of affordability. It's a bit more expensive than our older solution.  

Okta charges per user, and that can make it costly if you are a big company.

We are customers and end-users. 

I'm using the latest version of the solution. 

I'd rate the solution eight out of ten. The pricing is a bit high, and they do charge per user. There are other options that are a bit less expensive. 

We used Okta Workforce Identity for SSO, MFA, life cycle management, as well as the external identity and access management for external customers. We used the solution internally for accessing all applications, so we had an Okta software portal where we could then start any application we wanted.

The biggest benefit my company gained from Okta Workforce Identity is that everything just works securely so that all your managed devices can access all your applications without any hassle because they are trusted devices, but if you want to use your father's or mother's PC to access the company application, then it will ask more MFA (multifactor authentication) steps.

What I found most valuable in Okta Workforce Identity is that it worked together with VMware Workspace One, so there was this device check at the same time. My company used the trusted device method that enabled you to define that only the trusted devices including the Workspace One agent were able to access the applications directly without an additional authentication step.

A room for improvement in Okta Workforce Identity is its price. It could be cheaper. The biggest benefit of the solution is that everything works securely without extra steps, so you're saving on your workforce's time and effort because your applications work smoothly and securely, but you'd need to pay some amount of money for that.

Another area that could be improved, though not necessarily regarding Okta Workforce Identity, is the SSO applications because so many of the source applications charge extra money to put the SSO to work, which means you have to buy a more expensive license. Nowadays, SSO is a mainstream functionality and it should be out-of-the-box in those applications because it's so easy to set up.

I've worked with Okta Workforce Identity since 2014, though I just changed my workplace, meaning I left the company where the solution was being used. I did have experience with it within the last twelve months.

Okta Workforce Identity is a stable solution. It's always on, though once there's been some hiccup in the US time zone that didn't affect my company.

Okta Workforce Identity is a scalable solution.

There were times I needed to escalate some questions to the technical support team of Okta Workforce Identity, and on a scale of one to ten, with one being the worst and ten being the best, I would rate support a nine out of ten.

Positive

Setting up Okta Workforce Identity has to be done gradually because you have to change the log-in methods for every application, meaning you need to turn them on. For example, now you'll start to use Okta Workforce Identity for Office 365. Next, you'll use it for Zendesk. You cannot do everything at the same time, so you have to make a gradual plan over a couple of months, then you turn on all of the new applications for authentications to be done with Okta Workforce Identity.

Deploying the solution took two months.

The implementation of Okta Workforce Identity was done in-house because my company had a lot of ready-made integrations with the solution, but sometimes you need to ask for help from the third-party software vendor, particularly to turn on some features, so your third-party software integrates with Okta Workforce Identity, for example, you'd need to have the SSO feature turned on, etc.

The pricing for Okta Workforce Identity could still be improved or made cheaper. It costs from 50 to 100 euros a year per user.

Okta Workforce Identity has different packages you can choose from, and my previous company had all of them, particularly the full Okta suite. We went with the full suite because you can also use it in the new employee onboarding process, so when you get a new employee, you can authorize Okta Workforce Identity to provision all the applications automatically so that when you create the new user and you put that user into a certain user group, then he gets all the applications provisioned automatically. For example, for Microsoft 365, the solution creates the user, puts that user in the right place, and also adds licensing, so my company was using Okta Workforce Identity as well for the onboarding of new employees.

In the organization I previously worked for, I also used VMware Identity Manager, apart from Okta Workforce Identity. Those two solutions work together, and though they have a little bit of competition, VMware Identity Manager and Okta Workforce Identity complement each other. Okta is the master identity solution while with VMware Identity Manager and Workspace ONE, you can create the aspect of the trusted device so that when you have a trusted iOS, Android, Windows, or Mac device, it will check whether it's trusted, via VMware, and then transfer the authentication to Okta Workforce Identity and everything works just smoothly, so Okta knows that this authentication comes from a trusted device and it can pass further without any additional MFA.

Okta Workforce Identity isn't an on-premises solution.

My company had three hundred users of Okta Workforce Identity at the time.

In terms of maintenance, you just need to make configurations on the console. There was no scripting or coding, so you just have to use the console and know what you're doing.

I would recommend Okta Workforce Identity to others who may want to start using it. My advice for new users is that it's important to understand the trusted device and zero trust methodology, so that when you have devices to manage, for example, with Workspace One, and you combine that with Okta Workforce Identity authentication through VMware Identity Manager, you'll get the full picture. This is so you can ensure that everything works together because knowing only the identity and access management without the device management and trust would be just half the story.

I'm rating Okta Workforce Identity nine out of ten.

We use it for API authentication, on-premises clusters as well as cluster access, and cloud cluster access.

We did not have a unified mechanism for accessing resources or a secure way of accessing resources, and Okta solved that problem for us.

One of the features that I have found to be very valuable is its interoperability and compatibility with all types of resources, whether it's networking, infrastructure, or applications. That is, it is compatible as well as interoperable, as far as the federated authentication is concerned.

It's not compatible with on-premises installations, unless you host it as a SaaS. We were not able to do that. For example, imagine a scenario where the cloud is not available. Then, Okta will not work for you. That use case will readily fail because it doesn't have an on-premises installation that you can use to authenticate or provide identity and access management. If you have a purely on-premises solution that is not connected to the internet, then this will not work. This is one area that can be improved.

I would also like to see more intelligent analysis of the identity and access management from Okta.

We have been using it for the last seven years.

It is fairly stable. However, because it's a SaaS solution, it needs to have connectivity. If the connectivity is down, then Okta Workforce Identity will be down as well.

This is one of the pluses that Okta has. It's easily scalable, both horizontally and vertically.

Right now, we have about 3,500 users.

There was one minor hiccup with technical support, but other than that, the support has been pretty good. I would give them a nine out of ten.

Positive

We used ForgeRock, and we switched to Okta mainly because of the flexibility that Okta provides.

ForgeRock requires on-premises maintenance. Because most of our applications are now on the cloud, Okta is more user-friendly in that sense.

A couple of years ago, it was 70/30, 70 being on-premises. That's why ForgeRock was the choice. However, it's flipped now to 30/70, and Okta is more useful.

We still use ForgeRock because you can do an on-premises hosting for ForgeRock. Okta doesn't have that capability.

The initial setup is very straightforward; it's a very simple setup. There are some areas for which you need some skills. If you have an SOP, you can just follow it. I would give it a four out of five.

We have three people assigned to the solution for deployment and maintenance.

We deployed it using an in-house team. The initial setup did not take much time; it took about one to three weeks.

Okta has fairly competitive pricing.

We evaluated some native cloud services, like AWS and Azure before choosing Okta Workforce Identity. 

We also looked at IBM ISAM, IBM Security Access Management, and Oracle ISAM, but they're very rigid products. That's why we went for Okta. They don't have any flexibility, and the cost was also very high compared to that for Okta.

If your use case is multi-cloud data centers and hybrid cloud architecture, Okta is a solution to go to. It's fairly easy to implement as well. It has federated identity and access management, and it works very well with any type of identification authentication. However, if you have on-premises data centers where there are connectivity problems, then it would be better to avoid Okta.

I would rate Okta Workforce Identity at eight on a scale from one to ten because I've found it easy to implement and easy to learn. That is, the onboarding or the learning curve is less. It also has federated identity and access management mechanisms, where you can apply the various resources and workloads that you have. Also, it has very good interoperability and compatibility. It can easily scale too.

I am using Okta Workforce Identity for identity access management.

Okta Workforce Identity has helped improve our organization by providing customer identity management, customer onboarding, customer identity stores, workforce provisioning. Additionally, single sign-on is one of the primary functions that has been a benefit.

Okta Workforce Identity could improve provisioning it can be made simpler.

They are implementing in one of the newer releases certification, attestation, and some role-mining abilities, but I don't know how far along that's going to be. That's a statement that they said they are going to have in the future.

I have been using Okta Workforce Identity for approximately three years.

Okta Workforce Identity is scalable.

The scalability of Okta Workforce Identity is great. It's a SaaS solution the scalability is one of the built-in expectations with it. It can scale, even though I don't scale it personally with any of the companies I worked with, it can potentially scale to support millions. It's easily scalable.

I rate the support from Okta Workforce Identity a four out of five.

I have previously used Oracle Access Management, Microsoft Azure Active Directory, and ADFS. Those would be the major ones. I've been introduced to small ones, such as PingFederate, but I never used those heavily.

We switched solutions because of the architectural design. We chose Okta Workforce Identity for external customers, it's a customer identity platform that we decided to go with.

The initial setup of Okta Workforce Identity is straightforward. I was able to get an environment ready within half a day.

I rate the initial setup experience of Okta Workforce Identity a four out of five. 

I have used an integrator and have done the implementation myself for Okta Workforce Identity.

Okta Workforce Identity scales up by the user, and then by the service that you're purchasing.

The solution is not the cheapest but not the most expensive. They are in the middle rating.

I rate the price of Okta Workforce Identity a three out of five.

I rate Okta Workforce Identity an 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.

Okta has recently built Okta Identity Engine (OIE). It has a lot more capabilities than the classic engines. The certificate-based system is one thing, and third-party tools like Intune and Jamf for iOS devices. There is a trust relationship between these device management tools, and that contributes to control over the end-user devices.

Scalacity was a company acquired by Okta, and its technology was integrated into Okta's Advanced Server Access (ASA) product.

Okta has introduced the Universal Directory. It has custom attribute capability and user permissions to read/write on their profiles or hide them. Profile sources and identity profile sourcing are two different components that I haven't seen in other products.

Okta can import many attributes into the Okta profile and send attributes from the engines. Multiple sources of truths and profile inheritance are done in granular ways. This plays a major role in ABACs going forward.

Okta's MFA features are good. Okta is looking forward with more on the push or less, relying on the Okta Verify factors. It also has extensive capabilities. It's adopting a layer-by-layer upgrade in developing the policies, like MFAs.

Okta has more when it comes to the policy level. It has distinctive features where you can do a mix and combination to have users access applications for various business cases. That's something unique and a selling feature.

Okta has a limitation with directory integrations. If you have multiple Active Directory integrations, the user distinguished name (DN) and the manager DN don't get imported properly into the Okta user profile. It has a property of Get AD user's property, but that has limitations when writing an expression language to import changes or updates to user DNs or manager DNs from AD, especially if you have AD master users.

Also, Okta doesn't have a partial push. It pushes down the full profile schema for lifecycle management or provisioning. Even if only one attribute gets updated, even though it is unmapped, it can override other values in the downstream application by nullifying the query. That's the biggest flaw in my experience.

The product releases a lot of brand-new features within the quarterly releases.

It's definitely the leading Identity Access Management cloud platform. I have experience with Okta for almost six to eight years now.

I've been an Okta-certified consultant since last year. I got an opportunity to work on the workforce as well as the customer side.

I have experience with more than eight Okta tenants parallelly due to various business cases across my career. Ultimately, this product itself is a pioneer in Identity Access Management.

Scalability works very well. I've worked so far with Okta. It's like the heartbeat of that company. If Okta goes down, people are unable to authenticate anywhere. They can't get into applications. So there's a lot of dependency on Okta within the businesses and environments that I've seen so far. It's very critical.

The customer service and support are awesome. They have a CSM assigned for each organization, and they are pretty much responsive to any events that occur. Or if there are any escalations or incidents that impact the business, they're pretty much around in a timely fashion to support the organization.

We have the flexibility with our CSMs to reach them in any manner, email or phone, and they're available most of the time.

Positive

We have long relationships with other vendors for things like Identity Governance and Privileged Access Management. But one thing I've noticed is that Okta has been expanding into wider ranges. 

But, there are limits and restrictions to the existing features, which are not fully developed yet. Okta have added a lot of tech in the last couple of years.

I'm not a hundred percent sure about the return of interest because it is very much dependent on the size of the organization.

I came from smaller organizations working, like, midscale to, like, large scale. So overall, like, the security breach, like, there are, like, two to three security breaches that have happened, but nothing has been damaged so far for the organization.

So, investing more in Identity access management is a critical investment for any operation as applications are moving to like cloud and SaaS-based. So, there is a dire need to protect the digital identities of enterprise tech employees as well as their customers.

There are a lot of features you can automate. Okta Workflows is a key feature that has a separate pricing than adaptive MFA or SSO. It's a combination, but Okta has features and capabilities to reduce the IT burden. Within my experience, it's been helpful so far with a lot of overhead work that comes with onboarding and offboarding.

The pricing itself is a bit more expensive than the other products in the market so far. Since I know the product is in full demand. But, again, the price texture, features, and everything suits well for small to medium.

But, for larger organizations, it's more expensive than the other platforms. But, usually, licensing is a bit expensive.

I definitely recommend Okta. It has all the features you can utilize to protect any organization's digital entities. Considering a lot of other factors, like cost and the overall features the company wants to use. If you want to use Identity Governance, Identity Access Management, or Privileged Access Management, that's a different story. It's also a different story if you're using other products for different needs.

Overall, I would rate the solution an eight out of ten. 

It's mostly used for customer-facing applications (Customer Identity Management). API management and self-service flows are the most utilized capabilities. It offers a lot of customization in terms of branding, email notifications, and creating a good end-user experience.

For remote access, we have solutions proposed, like Okta Identity Engine (OIE). It has more capabilities than the classic engines. The certificate-based system is one thing, and third-party tools like Intune and Jamf for iOS devices. There is a trust relationship between these device management tools, and that contributes to control over the end-user devices.

Okta has introduced the Universal Directory. It has custom attribute capability and user permissions to read/write on their profiles or hide them. Profile sources and identity profile sourcing are two different components that I haven't seen in other products. 

Okta can import many attributes into the Okta profile and send attributes from the engines. Multiple sources of truths and profile inheritance are done in granular ways. This plays a major role in ABACs going forward.

Okta's MFA features are good. Okta is looking forward with more on the push or less, relying on the Okta Verify factors. But it also has extensive capabilities for Ubiquiti. It's adopting a layer-by-layer upgrade in developing the policies, like MFAs. 

Okta has more when it comes to the policy level. It has distinctive features where you can do a mix and combination to have users access applications for various business cases. That's something unique and a selling feature.

For security protocols we use most security protocols, such as OIDC and SAML.

Okta has a limitation with directory integrations. If you have multiple Active Directory integrations, the user distinguished name (DN) and the manager DN don't get imported properly into the Okta user profile. It has a property of Get AD user's property, but that has limitations when writing an expression language to import changes or updates to user DNs or manager DNs from AD, especially if you have AD master users.

Also, Okta doesn't have a partial push. It pushes down the full profile schema for lifecycle management or provisioning. Even if only one attribute gets updated, even though it is unmapped, it can override other values in the downstream application by nullifying the query. That's the biggest flaw in my experience.

The product releases a lot of brand-new features within the quarterly releases. There's a feature roadmap for Okta CIM, and most of it is coming in with a lot of users or the customer side.  

It's definitely the leading Identity Access Management cloud platform. I have experience with Okta for almost six to eight years now. 

I've been an Okta-certified consultant since last year. I got an opportunity to work on the workforce as well as the customer side. 

I have experience with more than eight Okta tenants parallelly due to various business cases across my career. Ultimately, this product itself is a pioneer in Identity Access Management.

It's pretty much stable most of the time, but I have come across a lot more outages recently within Okta. 

 But, Okta is definitely a very good product.

Scalability works very well. I've worked so far with Okta. It's like the heartbeat of that company. If Okta goes down, people are unable to authenticate anywhere. They can't get into applications. So there's a lot of dependency on Okta within the businesses and environments that I've seen so far. It's very critical.

The customer service and support are awesome. They have a CSM assigned for each organization, and they are pretty much responsive to any events that occur. Or if there are any escalations or incidents that impact the business, they're pretty much around in a timely fashion to support the organization. 

We have the flexibility with our CSMs to reach them in any manner, email or phone, and they're available most of the time. Very good.

Positive

We have long relationships with other vendors for things like Identity Governance and Privileged Access Management. But one thing I've noticed is that Okta has been expanding into wider ranges. However, there are limits and restrictions to the existing features, which are not fully developed yet. I think they've added a lot of tech in the last couple of years.

It's always smooth and straightforward to set up, but we can definitely have a bit of complex solutions.

I'm not a hundred percent sure about the return of interest because it is very much dependent on the size of the organization.

I came from smaller organizations working, like, midscale to, like, large scale. So overall, like, the security breach, like, there are, like, two to three security reasons that have happened, but nothing has been, like, damage so far for the organization. 

So, investing more in Identity access management is a critical investment for any operation as applications are moving to like cloud and SaaS-based. So there is, like, a dire need to protect the digital identities of enterprise tech employees as well as their customers. 

There are a lot of features you can automate. Okta Workflows is a key feature that has a separate pricing than adaptive MFA or SSO. It's a combination, but Okta has features and capabilities to reduce the IT burden. Within my experience, it's been helpful so far with a lot of overhead work that comes with onboarding, offboarding.

The pricing model for the Customer Identity product is based on Monthly Unique Users (MUI).

The pricing itself is a bit more expensive than the other products in the market so far. Since I know the product is in full demand. But, again, the price texture, features, and everything suits well for small to medium, for sure. 

But, for larger organizations, it's more expensive than the other platforms. But, usually, licensing is a bit expensive.

I definitely recommend Okta.

Every organization needs workforce productivity as well as customer security. The need is definitely there for any enterprise or organization to protect their identity. Customer security also plays the utmost role in protecting customer data.

Overall, I would rate the solution an eight out of ten.