Okta Platform Reviews

An example of how I use Okta Platform in my day-to-day work includes the integration of new applications, reviewing security-related matters, or making decisions on how to secure identity. I also perform automation with the help of AI to improve identity management. We are using Okta Platform with AI.

The best feature Okta Platform offers is availability; it has high availability, which is very hard to find, and I have been working with Okta Platform for more than six years.

Availability stands out for me because the identity platform is core; if people cannot sign in, they cannot work, so it has to be available at any point in time. In six years, I have never seen it going down.

Okta Platform has positively impacted my organization by doing a lot of cleanup, simplifying operations, improving visibility, governance, and security across the board.

I would say that sourcing every user via different sources into Okta Platform gives a single pane of view of the organization, where you can track login activity and see who is active and who is inactive. Cleanup of those inactives improves both security and cost.

The only improvement point I would suggest for Okta Platform is that it needs to redesign the feature request system because there are many important features that are not taken into consideration.

I do not want to go into specific details, but you can visit Okta Ideas and see many ideas that have been shared. Many of them are prioritized, but the fact that a user wants it or that a metric exists does not help. Okta Platform needs to redesign or repurpose the entire concept of how it wants to handle feature requests.

I have been using Okta Platform for more than six years.

Okta Platform's customer support is good. I would rate the customer support a 10 because it is consistent.

I rate Okta Platform a 10. The reason for my rating is its reliability, availability, and simplicity. I advise others looking into using Okta Platform to evaluate it; if you are not going to use it, at least evaluate it alongside your current platform to see the difference, as a lot of things can be done through Okta Platform, with availability and reliability being the most important factors.

We are an advertising company with around 400 employees in four different countries: Peru, Chile, Mexico, and Brazil. We have implemented Okta Customer Identity to enforce security in our applications and ensure all users access them securely. We use Okta Customer Identity for various applications like Office 365 and several other applications essential to our business.

Okta Customer Identity focuses on providing top-notch identity management solutions. One of its most valuable features is its easy integration with various applications through its extensive application directory, offering hundreds or thousands of applications ready to configure. This integration is significantly easier compared to Microsoft Entra ID, where we encountered numerous issues. We particularly value its real-time reporting capabilities. For example, we detected cyberattacks from countries like Russia and Asia and were able to block those IP addresses and configure our system for more security. These advanced security features and reporting capabilities make it easy to manage.

Okta Customer Identity is continuously improving its solution. Since we started using it in 2019, we have observed numerous enhancements to increase security.

We have been using Okta Customer Identity for more than five years in our company.

We had an issue a couple of years ago that was swiftly resolved by the support team, showing their efficiency. They also offer a comprehensive knowledge base on their website, which is very helpful for addressing any issues or queries.

Neutral

We evaluated Microsoft Entra ID but chose Okta Customer Identity because it is easier to integrate with various applications. Microsoft Entra ID presented many challenges and it was more difficult to manage integration processes.

The initial setup of Okta Customer Identity is straightforward due to its well-architected solution. It is intuitive and user-friendly for administrators to manage.

Okta Customer Identity is expensive compared to other solutions, but we believe the investment is justified given the rising cybersecurity threats. Despite the cost, it's cheaper than the potential financial loss from a security breach.

We evaluated Microsoft Entra ID.

Overall, I would rate Okta Customer Identity a ten. Okta Customer Identity is solely focused on identity management, which makes them excel in this area.

Private Cloud

Other

My main use cases with the Okta Workforce Identity include preparing my certification and doing integrations such as org-to-org integration or Active Directory, and it is mostly about integration.

As an individual user, I appreciate that I can create my own lab with Okta Workforce Identity. They provide instances for me to create almost ten instances to test.

Some of the best features with Okta Workforce Identity are configuring the SSO through Okta to Okta. For me, it was the certification and the integration I worked on because it was my pathway to prepare my certifications, along with the directory and network security, the IP zone and related components.

We use the Single Sign-On feature with the Okta Workforce Identity, and I configure it through the platform, especially for Okta-to-Okta. From one instance, I could switch to another using the SSO, as Okta to Okta allows the SSO feature.

The impact of SSO on my IT overhead and user experience has been significant because it reduced authentication fatigue, password sharing, and password reusing. For administration, it is integrated, and it is great for IT support. For the end user, it is beneficial as they do not have to remember a password or keep the password on a post-it for different applications; they just authenticate once to access several services and service providers.

Areas for improvement with Okta Workforce Identity would be in the governance place; for me, it is light. Okta is mostly focused on execution and runtime, which means maintaining authentication and ensuring people connect with the appropriate session. However, it could improve in the governance part, particularly regarding better role management and workflow, as I feel it is tedious on Okta. I think Okta could enhance the governance area of identity.

[Full sentence answer to 'For how long have I used the solution?' from the text.]

I have not personally experimented with technical support from Okta Workforce Identity, but I see there is a good community and many resources available. I have not tested Saviynt's support either, but I know there is direct contact with Saviynt support.

I cannot rate the support for Okta Workforce Identity directly because I have not experimented with it; however, I notice good communication within the community, but it would not be fair to rate them without personal experience.

Positive

I have tested different solutions before Okta Workforce Identity, including Saviynt and SailPoint, and decided to go deeper into Okta because it allows me to create my own lab. I worked on a homemade solution for about three to four years back, spending five years on that project.

My experience with the initial setup of Okta Workforce Identity is that it is straightforward and not huge. The initial setup is simple and, considering it is a SaaS solution, it is easier. I have tested the connector, which is available for on-site solutions for Active Directory, and there is still a lot of infrastructure relying on Active Directory.

Regarding experience with pricing for Okta Workforce Identity, I do not have the pricing on IGA solutions or IAM solutions, but from my study two years back for a project, I found it is not that huge.

The main differences I notice between SailPoint and Okta Workforce Identity for the IAM solution suggest that they are in different categories. SailPoint is mostly for the admin part, while Okta is excellent on the runtime section, focusing on secure authentication and SSO. SailPoint is used for configuring identity with the right entitlement while Okta is about ensuring secure connections and efficient user authentication.

I would rate Okta Workforce Identity seven out of ten.

Public Cloud

Other

One of the majorly used use cases for Okta Workforce Identity is the assignment of different SaaS applications, which are cloud-based, and using them with single sign-on. Users don't have to remember the password for each and every online cloud-based application. They just need to sign in with one email and password. This is one of the major benefits of using Okta Workforce Identity.

One of the best features of Okta Workforce Identity is its integration with different SaaS applications, which makes it a better product than the competitors.

The multi-factor authentication feature in Okta Workforce Identity is very good. It has its own verification app as well. It is very good in authentication, and we can use hardware keys, software keys, or any authenticator, majorly known authenticator app, for multi-factor authentication.

The provisioning and deprovisioning features of Okta Workforce Identity are very good. We can automate them as well, and we can provision users, groups, applications, and provision tools based on specific groups as well. The product is very good in that as well.

I believe that if we integrate the workflows section into the main Okta Workforce Identity dashboard, it can be very useful.

We have been using Okta Workforce Identity for about 4 to 5 years now.

In terms of the initial setup and deployment, I find it to be very easy. We have to set it up for the first time, and it has a very straightforward implementation. We have the pictorial and video guides on the Okta Workforce Identity websites on how to deploy it, how to set up employees, how to provision them, how to create groups, and how to set up devices. Each and everything is documented, and it's pretty much straightforward to use.

Okta Workforce Identity is a stable product. We had an issue with the Okta Workforce Identity dashboard once in 2023 when we had an outage, but it recovered in a few minutes.

We have never felt the need to contact the Okta Workforce Identity support team. It has been up and running. We had an issue with the Okta Workforce Identity dashboard once in 2023 when we had an outage, but it recovered in a few minutes.

Positive

We weren't using any single sign-on application or solution before choosing Okta Workforce Identity. This was our first product that we implemented in our company.

In terms of the initial setup and deployment, I find it to be very easy. We have to set it up for the first time, and it has a very straightforward implementation. We have the pictorial and video guides on the Okta Workforce Identity websites on how to deploy it, how to set up employees, how to provision them, how to create groups, and how to set up devices. Each and everything is documented, and it's pretty much straightforward to use.

I don't have the exact quotation or the exact pricing details for Okta Workforce Identity, but everything comes at a cost. However, when it gives you scalability and reliability, then I don't think the pricing matters.

I believe we have a lot of features in Okta Workforce Identity and I don't think we should be having more features in it as it's currently packed with a lot of features.

I believe we have a lot of features in Okta Workforce Identity and I don't think we should be having more features in it as it's currently packed with a lot of features. On a scale of one to ten, I would rate Okta Workforce Identity a nine out of ten (9.9).

Public Cloud

Other

We are currently using Okta Customer Identity as a managed service platform. We are building a platform where our customers can subscribe to different products of Okta Customer Identity, such as Access Manager, Entity Manager, and Okta Privileged Access. Our customers purchase subscriptions and create a PO number, which we use to perform technical implementations.

Okta Customer Identity is a SaaS-based application, making it easy to configure compared to competitors. It offers around eight thousand five hundred out-of-the-box connectors, providing an edge over other tools. It eliminates the need for configuring connectors using REST APIs as they are readily available. The Entity Manager is integrated with SSO, and Okta Customer Identity offers a wide range of protocols for federated single sign-on and token exchange. Okta Customer Identity also provides excellent documentation and training resources.

In Okta Identity Governance and Okta Privileged Access, some features are still being developed. Integration with Active Directory servers, Cisco routers, and switches is not currently available. Additionally, integration with platforms like DB2 and Oracle or SaaS-based databases is still in progress. These features need further development for full functionality.

The support from Okta Customer Identity is excellent, and I would rate it eight out of ten.

Positive

Okta Customer Identity is known for its easy configuration and deployment.

Okta Customer Identity is considered cheaper compared to other tools in the market, such as IBM and CyberArk products. Further details on costs would require consultation with our sales team.

I compared Okta Customer Identity with solutions like IBM Security Access Manager and CyberArk. While CyberArk is a fully functional tool with all features, Okta Customer Identity is more affordable and offers comparable functionality.

I rate Okta Customer Identity as nine out of ten. The Privileged Access Manager part is still in development but is expected to be in line with competitors like CyberArk or BeyondTrust soon.

Public Cloud

Other

It is for Single Sign-on and Multi-Factor Authentication.

It is very easy to log in to all my various corporate accounts through Okta Platform. This helps me because I do not need to have any password. I just simply log into Okta Platform which has a single sign-on capability.

This helps us whenever our employees, our new employees come into the company. On first login, when they come into the company, they have access to all our corporate accounts already once they have their corporate account. They can log into their various productivity and corporate applications. This helps ease the burden from our IT support team to have to onboard someone manually. When someone leaves the company, having an IT team have to remove their access one by one is a very difficult process. Okta Platform Lifecycle Management helps us offboard those employees who have left the company more easily.

It would be great if there were a way to save even my social media passwords and other passwords through Okta Platform and single sign-on through Okta Platform in the future. I do not think they have this capability just yet.

I have been using this for six years.

There were some alternatives like JumpCloud and Ping Identity that we were evaluating. However, since we are a partner, we prefer Okta Platform. There is a bias towards Okta Platform.

I would say the setup difficulty was in the middle, depending on circumstances. For us, it was quite simple because we had everything in place. We just needed to integrate the Single Sign-on and the directory with our Google Workspace or our current IDP. It was pretty straightforward and took a couple of days.

Regarding pricing, as mentioned, we are a partner, so we do get a special big discount as a partner versus other customers.

There were some alternatives like JumpCloud and Ping Identity that we were evaluating.

Okta Platform is a great product and one of the best. We are a partner and have been using it for six years. We have four engineers on our team. We do not use the PAM and do not need it. I would rate this product nine out of ten.

Public Cloud

Other

I work for one of Norway's largest employers with 50,000 employees. This is Norway's largest retail chain and we use it for 30,000 workers in retail, 15,000 in warehousing, and 5,000 in the corporate environment. For all of these, onboarding is automated to the HR and we have an old CA, which is now called the Broadcom Identity Management Solution for provisioning into Okta Workforce Identity. In this solution, we take those 50,000 identities and we've now built a B2B portal so that vendors, producers of the stuff that is sold in these retail chains, can log on and do things like plan their shipments, have the accounting done, et cetera, et cetera. So there are about maybe 20,000 people, a total of 70,000 people in this identity space. Last but not least, is the PAM solution. So we have maybe 300 IT staff on shore and we have maybe 600 offshore. I haven't done the latest count, but around 1000 IT workers authenticate through Okta Workforce Identity but are then given access to the PAM solution because the PAM solution protects both our cloud environment and our on-prem environment. We use the cloud to get into the on-prem.

First of all, the solution is very simple. It's actually made for smaller companies. So working with it, I wouldn't say that anyone could do it, but everything can be expressed as groups and rules. 

The drawback of this solution is that in our shops, many staff members sometimes have to be borrowed from one shop to another and the solution does not really support having multiple roles. The user experience we would like to have when a person works in shop A which pays their salary is that they should have access to pretty much everything. Maybe you have somebody who is a manager in that shop A, he should be able to order new wear, he should be able to change the pricing, he should be able to empty the cash registry, and ship it to the bank. But when for instance, in COVID, people had to fill in for people in shops where a lot of people were sick, then they had to actually use user accounts of people that work in shop B. If you were employed in shop A, you could not work in shop B without borrowing somebody else's user ID and password. Which is really bad. We haven't been able to work around that and Okta Workforce Identity does not have a solution for it.

We are now piloting their identity governance solution. Obviously, it's easy to give somebody access, give them an account, and give them roles, but it's hard to maintain that. For example, if you moved from, say working in a shop to working in a warehouse. But why do you still have all this shop access? The solution has until now not had anything to really support the process of taking away access. But now we are in a better release program of Okta's identity governance solution. Although it's very basic, the solution has started on a journey, but identity governance is something that Okta Workforce Identity really needs to improve.

The ability or the options in the solution for changing the look and feel are not good enough because in our partner portal, essentially what they have is an ugly admin interface. The admin interface is good enough for us technical people because that's all we need. We work with the product and we're able to see the data but when it comes to presenting the service portal, Okta Workforce Identity does not have any capabilities really for making it look pretty. 

To add branding and different graphical user interface elements than Okta basic for essentially delegated admin for the business-to-business portal is horrifying because you're essentially using the tech admin. The only option we had and used, was to take the tech admin console and strip it. so that a vendor that has some goods that are sold in the shops, when they want to add a user on their side, say a driver or a packer on their side who should know how much they've packed in a truck to come to our warehouse, then the user interface that this vendor is using, these functional people will then have to use an extremely basic user interface.

I have been using the solution for three years.

The stability is fantastic and has never been down. I give the stability a ten out of ten.

The solution's cloud environment seems to be highly scalable. We haven't found any bottlenecks there. The only bottlenecks we found are within our own infrastructure.

The customer support guy for Okta in Europe, a relationship manager, used to be a friend of mine when I lived in Sydney, Australia. He worked for Sun Microsystems systems back then. Sun Microsystems was the best product in the IT industry. Now Okta Workforce Identity is the best in the identity industry. The solution is not perfect because it's meant to be high volume, simple functionality, and all the basics first. The point is they're now adding functionality and this is where the EMEA lead, he's been in this industry for 20 years just like me. And he's so good. The team that he has, again, the tech team that they have is fabulous. The tech team is on par with maybe the absolutely best tech team that I've ever experienced with CyberArk, but the Okta guys are brilliant.

Positive

Previous to using Okta Workforce Identity we used Oracle Access Manager and it was horrible. Oracle Access Manager didn't scale, it had a lot of bugs, and it was expensive. Oracle was charging obscene license fees for a product that was rubbish.

The initial setup is very easy. Building a new environment is easy because nobody is better than Okta Workforce Identity when it comes to deployment. I give the setup a ten out of ten for ease.

The implementation was completed in-house by our two engineers.

I give the solution an eight out of ten for return on investment. I would not give the solution a ten because our brand is hurting a little bit by having these non-customizable external interfaces. 

The licensing is per user per month and includes full technical support. I give the pricing a six out of ten. It's not a bad product for a high price like Oracle is. It's a good product for a fair price but It's not cheap.

I give the solution a nine out of ten.

The thing is you can build a deployment in a day. So creating a new environment is done overnight, 24 hours. But if you say, how long does it take for us to build the connection so that CA was able to give us the data we needed to fill the roles in the solution, and then get provisioning up to work with Azure AD, and the main applications, that took us six months. Not because of Okta Workforce Identity but because of all these interfaces. That's always the killer with identity implementations. The interfaces you need to speak with to get your source, your HR data, or partner data. Maybe the best example is the partner portal. That took one year but that was more to get what's the functionality, what's the user experience. Okta Workforce Identity for engineers is a pretty solution. 

There are over 70,000 people using this solution.

We also use Thycotic Secret Server for privileged access management. So for all the tech people that need to say take backup our ERP, warehousing applications or put a new feature in the warehousing applications or upgrade the point of sale system, all those tech people get access to Thycotic Secret Server. I think there are 1000 that are actually employed onshore and offshore by my employer. And another 1000 that are tech people that maintain switches, operating technology kind of equipment. So about 2000 people have Thycotic accounts. But 70,000 have user accounts and user access. With Okta Workforce Identity everything is included with the licensing fee. If you've ever seen an Oracle licensing agreement there are loopholes in there and so you end up paying for additional items above the Access Manager, for example, you also pay for the database that it runs on. With Okta Workforce Identity it's simple. You get what you pay for. No more, no less.

I understand that Okta Workforce Identity has chosen to go for simplicity first. And that complex functionality, which we, being a very large customer... There are not many like us. We have more difficult requirements than most. But to do the simple things so well that we don't have to worry about them means we can focus on the last 10% of requirements. That will always be hard. And that's why I think the solution does 90% of the requirements so well that you need to do every day, so we can focus on the remaining 10%, which may not even be an Okta Workforce Identity problem. It is just a problem that you end up with when you have a very large business with a user portfolio that is everything from server admin from India to a trucking company that needs access to the warehousing doors in another part of the world. Okta Workforce Identity from an access management point of view is a nine out of ten.

Private Cloud

Other

The solution is used to eliminate a VPN, provide identity authentication, and single sign-on (SSO). We use Zscaler authentication to manage endpoint logins, endpoint report management, and single sign-on for applications.

The most valuable feature is the identity access authentication.

There is a need for Okta to provide an end-to-end solution without needing a separate product like Zscaler for multifactor authentication. Additionally, Okta should enhance its endpoint defensive capabilities, as we currently use BeyondTrust for Elevator Access Management.

I have been working with Okta Workforce Identity for four years.

The solution is rated as a nine in terms of stability.

Okta is not designed fully for scalability.

Okta provides good support. While we are unable to have it in-house, we can raise a ticket, and they support us well.

Positive

We utilize Okta and Zscaler for multifactor authentication.

The setup process is very user-friendly and has no issues.

Our internal team underwent training materials and configured the implementation successfully.

The pricing is very high, which is an area for improvement.

I recommend Okta Workforce Identity to others, particularly for mid-sized and large enterprises.

I'd rate the solution nine out of ten.

Hybrid Cloud

We use Okta for identity and access management for our internal services, cloud services or applications (SaaS). We have a hybrid setup since we have a global workforce, so we unify our IAM services.

The most useful features of Okta for my organization are identity and access management, single sign-on, and the flexibility for hybrid setups. 

Okta enables multi-factor authentication, which enhances security, especially for SaaS applications. The integration capabilities of Okta are very flexible, with multiple protocols that can be integrated, especially for single sign-on. Any API can also be added, making it mature in terms of integrating with other identity providers, particularly Active Directory or Azure Entra ID.

Okta should have at least a local presense for countries that align with or comply with GDPR or data sovereignty, so there are no compliance or audit questions. There are integration issues with Office 365; such as groups not updating correctly in Okta. Okta should work on resolving them.

I have been in the organization for one year, and it has been more than three years now that Okta has been used.

As long as you have Internet connection, there are no issues with the stability. 

Okta is scalable and reliable, with no downtime or service disruption encountered over the years.

My team contacts Okta support for increased integration requirements. They are very supportive; they just open a ticket, and they support us very professionally.

Positive

The setup process is pretty straight-forward, having experience with different single sign-on (SSO) and identity access management, I can manage the setup process with ease. Okta provides clear guidelines and documentations as well.

Pricing for Okta is reasonably not that much, however,  I don't have access to the commercial aspect.

I recommend evaluating your environment first. If you have a global workforce or you need flexibility and higher visibility on your identity and access management (IAM) and SSO, Okta is a good solution. My total rating for Okta is ten out of ten.

Hybrid Cloud

Other

In Okta Customer Identity, I primarily respond to application handling with around three thousand applications. This includes handling internal applications for permanent employees and third-party applications for contractors. I also work on certification renewal annually and the setup of SSO pages to enhance security.

The most valuable aspect of Okta Customer Identity is the server's reliability, especially for directory and node management. I set up different directories for traffic redirection, ensuring backup when a data center faces issues and maintaining seamless operations.

There is room for Okta Customer Identity to improve by increasing the reliability for the server end, creating more directories, and focusing on internal users rather than external or contract-based ones. Additionally, extending idle session times from ten milliseconds to at least forty-five seconds would be beneficial. It is also suggested that patches be applied annually rather than quarterly.

I have been working with Okta Customer Identity for nine months.

I would rate the stability of Okta Customer Identity as eight. It has allowed us to manage identity signals effectively, though some customers are resistant to certain procedures, making stability slightly challenging.

I rate the scalability of Okta at nine. I have a clear understanding of the architecture and processes involved, which allows for effective scaling to manage user privileges, application logins, and leveraging tools like Splunk for efficient data management.

We have a strong internal support system including application support, data center, and IDM teams. However, direct interaction with Okta's technical support is minimal as we typically manage internally.

Positive

Before using Okta Customer Identity, I did not utilize a different solution for these use cases.

The initial setup of Okta Customer Identity took about five hours and required a team of three.

We needed three people for deployment and now require about four people for maintenance, including rotations among five to six employees.

The pricing for Okta Customer Identity is very economical. It is much cheaper compared to Oracle Access Manager, and the company focuses on internal training to mitigate additional certification costs.

We evaluated Microsoft Azure as another option, but both Okta and Azure are quite similar in functionality.

Overall, I rate Okta Customer Identity as nine. Although there are some areas of improvement, its pricing and scalability make it a preferred choice for managing user identity and applications.