Okta Platform Reviews

Okta provides island access management solutions, which means that anyone who needs an IIM solution can get it through Okta. For example, if you have 30-40 applications and users that need to log in to all of them, Okta can integrate all of the applications into a single point of access where users can log in once and use the same session for all of their applications. Okta also provides multi-factor authentication and other security policies to protect your users and applications.

We have multiple SSO protocols that we use for our different data centers. This is just one example of how we use Okta workforce identity to address our hybrid workforce needs. Apart from SSO, we also have Active Directory integrations that allow us to integrate with customer active directories and use active directory passwords for application sign-in and runtime authentication. This is called daily header authentication. This allows us to provide a centralized identity management platform for our users, regardless of where they are located or what applications they need to access. We can automate the process of adding users to Okta if they are activated in Active Directory, or if they are added to the database of applications or Active Directory in the last couple of days.

Currently, it has two-factor authentication. In addition to biometrics, it should offer three-factor authentication. Also, the training is too costly. Okta could reduce the training cost to make it easier.

I have been using Okta Workforce Identity as a service provider for four years.

I rate the solution’s stability a ten out of ten.

The solution’s scalability is huge. It has 99.9% service availability. We cater this solution to enterprises. I rate the solution’s scalability a ten out of ten.

The initial setup is easy. Once you understand the steps, it's straightforward. There are three steps: enrolling users, removing tenants, and updating field metadata from outside the application and SaaS integration. Deployment depends on the number of occasions, testing, and the users. If you have 30,000 users, you will need two months. I rate the initial setup a ten out of ten.

The solution is suitable for everyone, but it is locked up for a total number of years. Overall, I rate the solution a ten out of ten.

We use the product for a variety of applications to establish the basic functionality of single sign-on for the company. We are looking for more use cases for our users. We are a marketing company. We have a high turnover rate. The processes are key to us. We are exploring how we can take advantage of Okta to help us streamline processes.

We used to have around 12 systems that had unique logins. There were too many central repositories. Now, we can log in using a single presenter.

The end user's ease of use is the most valuable feature.

We faced a bit of an issue integrating the product with some applications. The integration process takes a bit longer than we would want it to.

I have been using the solution for around three years.

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

I rate the tool’s scalability a ten out of ten.

The initial setup was complex. It was not Okta’s issue. We are a holding company with over 30 Active Directory. There were complexities on our side. The product is deployed on the cloud.

It’s a long-term game. We don't expect to see a return on investment very soon.

The solution is really expensive. We are struggling a bit.

People considering the product must not only think about whether the tool will solve their immediate problem. They must think of all the things they want in the future before deploying the tool. Overall, I rate the product a 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 work for a review website for enterprise IT. We publish reviews for other people to read, either publicly or anonymously. We also work directly with Okta Platform, and they are interested in user feedback regarding what people like and what people dislike about their product. I am actively using Okta Platform.

Okta Platform team told us about a feature called Universal Directory. I have tried using it.

Okta Platform performs well regarding stability, lagging, crashing, and downtime.

Okta Platform can be scaled across different applications, platforms, and even for dashboard missions. It performs well regarding scalability.

I have not tried using any alternatives to Okta Platform or similar solutions.

Okta Platform pricing and deployment are easy.

One person can handle the deployment for a new client. Deploying Okta Platform does not require any maintenance on my end.

I do not have any partnerships with Okta Platform; I am just a customer. I will refer Okta Platform if scenarios arise. If anyone asks for a suggestion, I will definitely suggest Okta Platform. I would give Okta Platform a rating of nine out of ten because no software deserves a perfect score, but Okta Platform comes very close.

I am just an end user of the product, so I don't know how the product is used in remote force management in our company. I use the product to help me log on to our company's security systems.

When I was traveling, I could get my OTPs through the tool's app, through my cell phone number or via an SMS,which makes it a flexible product. The tool is helpful even in areas involving emails. It is possible to use the product in another country and add an extra layer of security to it, proving that it can be a really secure platform.

I use the tool at a low level, so it does what I need it to do for me.

The product does not offer enough integration capabilities. I want the tool to provide more integration capabilities in the future.

I have been using Okta Workforce Identity for two years.

Stability-wise, I rate the solution a ten out of ten.

It is an easily scalable solution. When it comes to the scalability features, the product has many options for people in different countries, offices, and remote locations.

I believe that there are around 1,500 users of the tool in my company.

I did contact the product's support team when my password got locked out. I could even reset the whole password from Okta easily through the tool's internal app. The support team was good.

The product's initial setup phase is straightforward.

The solution is deployed on the cloud since it is used at a company-wide level in South Africa.

Though I am not sure, I feel that during the implementation phase, my company did seek the help of a consultant and our organization's in-house team.

In terms of benefits offered by the product, I can say that the tool has centralized our company's security and internal policies while ensuring that we stay compliant so that the users stay protected. With the product in place, no phishing attacks or any other types of attacks can cause a problem since it is a secure platform.

Though I don't know about the licensing model of the product, I wouldn't be surprised if Okta offers a per user license subscription model.

The employee onboarding process is okay if you use Okta Workforce Identity.

The SSO feature offered by the product is good, easy to use, and user-friendly. The tool also has a password manager as well.

The tool's MFA part comes as one of the strongest features of the product.

I feel that it is a good platform with a good security layer, especially when you are scaling out your business, and you have to manage a lot of areas.

I ate the tool a ten out of ten.

We use the product to manage access and identify several applications.

The product’s most valuable feature is multifactor authentication. It has an easier integration and configuration management process than Microsoft Entra ID. We can integrate it into different platforms.

An area for potential improvement in Okta lies in the absence of a dedicated feature for backing up the configuration of our tenants. It is challenging to obtain a comprehensive backup. We have to manually document all the configurations. They could provide a built-in tool for creating backups mitigating potential issues or crises.

We have been using Okta Workforce Identity for five years.

The technical support services are good. They respond to the queries immediately.

Positive

Compared with Okta Workforce Identity, Microsoft Entra ID is challenging to use in terms of integration and troubleshooting.

The initial setup is simple. I rate the process an eight out of ten. It takes a few weeks to complete the integration for different projects. It is a reasonable time.

The deployment team includes administrators for the applications, as they are responsible for configuring integrations from their side. The administrator plays a crucial role in integrating the Active Directory. The project may require a collaborative effort of approximately three to five individuals. It requires two engineers for maintenance.

The single sign-on (SSO) capability in Okta has significantly streamlined the user experience. It provides an ease of accessing applications. The subsequent access to other applications within the same browser is automatic, eliminating the need to initiate the multi-factor authentication (MFA) process repeatedly. We can define trusted sources and policies depending on the security requirements.

The centralized approach to managing everything from a central point has streamlined administrative tasks, eliminating the need to navigate through different systems for user and role management. It is one of the best solutions. We find a lot of information on their support website.

The overall reliability is commendable, as the platform strategically replicates its systems across various clouds, minimizing the likelihood of service disruptions. Over the past five years, we have not encountered any problems with the service.

I rate it a nine out of ten.

We use Okta Workforce Identity for single sign-on (SSO).

One of the most beneficial features of the solution is the user provisioning and the de-provisioning feature. With the solution's universal directory, you can have all the user attribute information in one place. You can store it on Okta instead of in multiple places like your AD, applications, or different IdPs. You can get all the user attribute data onto your Okta, and then you can customize it. Okta allows you to modify the user attributes, which is also one of the useful features of Okta Workforce Identity.

Because it's a password-less authentication for personal sign-on, users don't need to use a password for it. That's how Okta comes into the picture, where it identifies the user based on the certificates for authentication. In that way, it also doesn't reveal the user identity to the applications if there is a man-in-the-middle (MITM) attack.

Okta Workforce Identity uses the System for Cross-domain Identity Management (SCIM) protocol for provisioning and de-provisioning. That is also one of the benefits of having your application's functionality on a platform like Okta Workforce Identity. It's easy from an admin point of view because when you de-provision a user on Okta, it will remove all the access from the respective applications without needing anything at the application level.

Because it's a cloud-based platform, installing the agents is the only integration you need to do in your current environment. You can have their agents installed on your Active Directory servers.

The integration is quite easy for other cloud applications. They have their own catalog of all the applications you can search and integrate. Applications like Microsoft Office 365 and Salesforce are already hosted on Okta. It's just a matter of configuring the applications with your company's metadata into your applications.

The solution's user interface needs to be improved and made easy. It has a lot of repetitive things. The solution should have a single pane of interface for admins.

I have been using Okta Workforce Identity for six months.

I rate Okta Workforce Identity an eight out of ten for stability.

Since it's a cloud-based platform, I haven't faced any scalability issues with Okta Workforce Identity. Our clients for Okta Workforce Identity are enterprise businesses.

I rate the solution an eight out of ten for scalability.

The solution's technical support depends on the service level. Okta has certain packages, like gold or silver levels. If you have a silver-level agreement with Okta, you can get the right support at the right time.

Neutral

On a scale from one to ten, where one is difficult and ten is easy, I rate the solution's initial setup an eight out of ten.

Okta Workforce Identity is one of the market's leading and stable identity solutions.

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

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.