Okta Platform Reviews

My primary use case is to have a single sign-on and to have identity access management. I'm the team management manager and we are customers of Okta. 

Having a single sign-on to all our applications.

With the device applications, when you are checking the logs, you can't hide the device and that's a feature that's missing. I'd like to see MDM source added. 

I have used this solution for a year. 

The solution is good on scalability and stability. 

The company has very good tehnical support and they respond quickly. 

The initial setup wasn't so easy but it wasn't too complex either. We had assistance from Okta for the installation. Implementation didn't take long, maybe two or three days but we had some issues with some applications, and we had to postpone our deployment for about two months because of that. There's no maintenance required. We have about 300 users dealing with the solution in the company and it's used daily. We have no plans to increase usage for now.

I think the approximate cost for the license is somewhere between $20,000-$21,000 a year and that includes everything. 

I think this is a good solution, I would recommend it. 

I would rate this solution an eight out of 10. 

SSO and MFA: To extend Identity Authentication on the existing IAM identity and account operations to the multiple domains for administrative and help desk personnel. Improve consistency of the identity management processes across the organization and improve compliance with governance mandates.

The access management with Okta revolves around the establishment of a single authentication store (reducing the number of accounts), which will allow the migration of existing applications to federations, or a common identity store. It will also establish a suite of centralized authentication services that can be used for future applications and systems platforms.

• Enabled MFA to access federated applications as well as increased user satisfaction through improved provisioning times and more reliable processes. 
• Reduced costs associated with paying for AD accounts for customers who use corporate applications (currently 4000+ customer IDs exist within the AD forest – these require a license at a substantial cost to the organization). 
• Increased productivity through centralization of IAM Authentication - Authorization operations to a single tool (ISIM), and better operational resiliency with distributed administration (Common tasks can now be handled by a more diverse set of individuals across the organization.

SSO and MFA for improved end-user experience, and protection against password spray attacks, account password self-service. Extend Identity Authentication and authorization management operations. Extend the existing IAM identity and account operations to divisional administrative and help desk personnel. This improves the consistency of the identity management processes across the organization. Obfuscating the AD account infrastructure from the application infrastructure to reduce risk and vulnerabilities associated with tying externally facing applications to corporate accounts.

• Passwordless authentication. 
• Integration with the user provisioning infrastructure to track all entitlement changes; simplify the modeling of the role and access definitions at every stage of the user life cycle.  
• Automation of the entire entitlement and role review process, in alignment with business needs and requirements as stated by business leaders and managers. 
• Oversight in the form of dashboards reconciling and centralizing information for immediate insight into the status of access reviews and certification processes.

3 years.

They work really well.

I did not have another access management solution in place prior to implementing.

It was straightforward for access management with SSO and MFA. It was complex to implement password synchronization between AD domains.

We implemented directly with the solutions provider.

We evaluated IBM Access Manager but decided to go with a cloud-based product.

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.

It is the authenticator for secure logins. We use it to log into companies' applications with a double security level. 

It is to prove that I am an employee authorized to use certain applications.

Our repository of data and our work are all based on Microsoft Teams now since we are a global organization with people spread literally across the globe. Employees have access to these documents all over the world, so the company needs to have a high level of security and privacy to access these documents. Okta is an important tool for controlling this access.

I find it very useful and very easy to use.

They have good push authentications. This is when I get into my company's internet and they ask me for a code that is provided by Okta. I don't need to write the code, I just need to click the "push" button and my mobile phone is asking, "Someone is trying to connect to your account, do you authorize them?" I just click yes, and automatically it recognizes that that login is authenticated. 

In terms of the user interface, it's fine. It's very good. I don't see any improvement needed in the user interface.

It's stable.

The solution can scale. 

My concern is that I live in an emerging country. In my country, there's a lot of stealing of mobile phones, and mobile phones are the authentication device through the Okta application. If someone should steal my mobile phone, which is very common in my country, he or she might have access to my company account. That's my concern. I don't know if there's another way of doing the authentification. Maybe if you can have a dedicated device for using Okta, it might be better, or if there were other options for authentication.

I would like to have a version of this software for personal use, for my personal accounts. 

I've been using the solution for two and a half years now.

The solution can scale. 

I'd rate its ability to expand eight out of ten.

Everyone is using the solution in our company right now. That's roughly 3,000 people. 

I've never directly dealt with technical support.

I'm not sure if any other solution was used previously. When I joined the company in 2020, I start using Okta, and I don't know if they had any previous applications.

The initial setup is intermediate. A security solution is not supposed to be easy to apply. It's supposed to be somewhat bureaucratic. That said, the setup itself leans towards being straightforward. We didn't have any issues with the setup.

I'd rate the ease of implementation at a seven or eight out of ten. 

I'm not sure about maintenance requirements, however, our company has a limited IT team of about three or four people, and therefore it's likely not too maintenance-heavy.

It has been a very stable product. It's reliable. There are no bugs or glitches. It doesn't crash or freeze. 

I'd rate the stability eight out of ten. 

I don't have any visibility on the pricing. It was negotiated by my company. I'm not sure how much they pay.

I'm a customer and end-user.

This solution is a direct competitor to Google Authenticator or Microsoft Authenticator. I use Okta. My company adopted Okta as a security platform.

It updates automatically, and therefore, we always use the latest version of the solution. 

Generally speaking, it is a good tool, and I would recommend it to others. 

I'd rate it eight out of ten overall. My main concern is security should a device get stolen.

We are using Okta Workforce Identity for our clients to be able to plug into the applications without entering the credentials. We are using a single sign-on for our services.

The most valuable feature in Okta Workforce Identity is the single sign-on,  universal directory, and lifecycle management.

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

Okta Workforce Identity is stable.

The scalability of Okta Workforce Identity is good when accessing all our applications.

We have approximately 500 users using this solution in my organization. The IT department is mostly using the solution.

Okta Workforce Identity could improve the support system, they are too slow.

We have not used other solutions.

The initial setup of Okta Workforce Identity was straightforward. The deployment took us approximately one and a half months. This included many different applications and services.

We did the implementation ourselves.

The price of the solution is good.

I would advise others to explore Okta Workforce Identity well before using it. It has a lot of capabilities.

I rate Okta Workforce Identity a nine out of ten.

The provisioning functionality has been the most valuable. This solution has good performance, fast integration and is very responsive. 

This user integration with the Okta integration network could be simplified.

I have used this solution for one year. 

This is a stable solution. 

The customer service and support is fast and effective. 

I did about six months' worth of work on it. It was more towards getting our lab set up, getting the certification done, etc.

It makes it very easy to onboard and offboard accounts. When someone quits, one of the hardest things for an admin to do nowadays is figuring out the 37 accounts that this person had and getting rid of all of them. With Okta, it is not that difficult. You can eliminate a lot of that admin time in one shot, which is important on the security aspect of things. If you miss one or two accounts, they can backdoor you.

Its integration components are most valuable. It integrates with everything in some way. There are some products, such as O365 or AD, with which it completely and 100% integrates. So, you can seamlessly create accounts across the board with some of these products. For some of the products with which it doesn't completely integrate, you can do some kind of interfacing. 

The only aspect in which it can be improved is that the interface could be cleaner. I found this even when I was trying to do my certification exam because the certification is hands-on. You find yourself fumbling around a little bit to find simple things. This happens even when you start to get familiar with the product.

Stability-wise, it is pretty rock solid. Its stability also depends on your access to the internet. We didn't see one instance where we felt that we were going to lose access. It is completely or 100% cloud-based.

We've seen Okta scaled to thousands and thousands of endpoints. You would have a couple hundred thousand before you go, "I wonder if that would work". Even then, you can run different instances based on geography, and they would tie in together. So, its scalability should be one of the least important concerns for a company.

My advice would be to look at the entire spectrum of your web apps as well as your on-prem integrations as you start to plan. If you don't plan it out initially, it gets really hard to fix some of these things at the backend. You should get a good, firm list of all the applications that you would like to integrate with and see which ones integrate seamlessly. From everything that we've read up on, they do a lot in terms of API support. So, for what they don't provide readily or out of the box, they could probably customize an API.

I would rate it a strong eight out of 10. It was the best product that we saw in its space. I didn't do a lot of comparisons on it.