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.

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 have implemented a number of applications as far as accessing them through their IDPs. And they're an identity provider; they also provide some alternative active directory slash l dash services. And I have purchased those for getting user data onto other systems.

It's very straightforward. The automation that they have and the way that they let you assign applications to groups or to users and do things dynamically, it is very straightforward other than just that there's a lot of nuance because of the breadth of applications out there that they can work with. It's more a matter of knowing how to work with the security mechanisms in place, such as SAML or OAuth, these may require specific expertise.

As far as our security team is concerned, the ease of implementing multifactor authentication is definitely the biggest value for our organization. Additionally, the single sign-on services provided by Okta allow users to log in to their Okta account and access a variety of other applications. That's why we implemented Connect to leverage this feature more efficiently across MacOS.

There are areas for improvement. One thing that seems odd to me is the lack of a built-in way to export all user data. They have a solution available on GitHub that they basically endorse, and it's developed internally, but for some reason, it's not integrated into their product. So, that's a peculiar aspect.

Instead, the support says they don't offer it but provide an alternative solution that we have to manage separately. So, it's a situation where they don't want to include it in their product, but they offer assistance outside of it? It's unclear what kind of support you would need for it. It just works.

Another area of improvement is scalability.

I have been working with Okta for two and a half years.

Okta is pretty stable. Occasionally, we encounter notifications indicating some issues, but that has happened only once or twice in the two years I've been using it.

There have been situations where our own users were temporarily affected by disruptions in the cloud, but those incidents lasted only for a couple of hours. Taking into account a 99.9% uptime SOA.

I would rate its scalability seven out of ten. There are definitely challenges we encounter, not related to the number of users but rather in terms of implementing various applications. Each application we work with can be completely different, resulting in highly variable implementation processes.

It ultimately depends on the specific use cases you have and the tools you utilize. It's important to find the best solution tailored to your needs.

We have around 500 users utilizing Okta Customer Identity.

The initial setup is fairly easy. I would estimate it to be at least an eight in terms of ease of setup.

The actual setup and configuration can be done in half a day or less. However, the main challenge lies in communicating with users and getting them to adopt and use it, rather than the technical setup itself.

It's more about informing everyone about the new requirement, that instead of logging in to each application separately, they can now log in to the Identity Provider (IDP) and utilize its Single Sign-On (SSO) capabilities to simplify the login process for all applications.

Okta's pricing is right where it needs to be and right in the middle of the market. You can pay them extra for services for assistance in implementing certain applications. You can hire one of their engineers to work with you and ensure successful implementation.

And that's something worth considering because they have expertise in their product and can get the job done more efficiently. It's worth paying for their services to ensure the solution is implemented successfully rather than struggling internally and failing to get it done.

Overall, I would rate Okta a nine out of ten because there is always room for improvement. However, it is best in class as far as doing the things it does. And it's something that I've implemented with multiple businesses.

And it's really well-regarded. Yes. There are alternatives out there. Like, they all do somewhat different in each thing, whereas Okta seems to really be trying to cover all the bases as far as providing solutions that integrate with people's OSBAP, people's active directory, companies that wanna get serverless, touching on, the zero test network security that they're really kind of playing in the center of that zone.

We use the solution for application security.

The solution is an open platform. It integrates with multiple applications simultaneously.

The solution's pricing needs improvement.

It is a very scalable solution.

The solution's pricing model could be better for SMBs.

I rate the solution an eight out of ten.