Okta Platform Reviews

The main differences between Okta Platform and Cisco for the IAM solution are that Okta Platform does not have an exclusive product that is tagged federal, and it depends on the person who is deciding it. The way I made Okta Platform comparable with Duo Federal is by attaching it to CAC, which is used by the military.

In my opinion, Okta Platform's best features include federation, which is very important, especially when you work with different systems. SAML plays an important role, and then there is the OAuth feature of Okta Platform and the OpenID. Those three—SAML, OAuth, and OpenID—are crucial. The scope, which is essentially the permission that you give to a token, and then the token that is being used by the application or by your user to authenticate themselves, is also important.

Automated lifecycle management positively impacts onboarding and offboarding processes for Okta Platform in terms of efficiency. When you integrate with Workday, ServiceNow, ITSM, and HR, those integrations make the onboarding process quite smooth. Whether the application involves a new employee, a joiner, or a leaver, those integrations handle all of those scenarios.

Some areas for improvement with Okta Platform, especially concerning AI and the federal aspect, are acknowledged as areas that Okta Platform needs to work on to offer features comparable to those provided by Duo.

In terms of Okta Platform's stability or scalability, I would grade its stability at around seven. Okta Platform is quite stable compared with Oracle. It is scalable compared with Oracle as well, but that is where the effort will come in. When you are doing basic things, it is straightforward, but if you are going to be doing workflows, other things, or recon and trust, then there is effort involved, and that is where it gets convoluted.

On a scale of one to ten, I would rate Okta Platform's support or customer service as around seven. With Duo, I was not directly involved because there is a group that handles it. I am a contractor, so my account does not have the privilege to open a ticket. I document it and pass it to a group, which is most likely the help desk. They are the ones who create the ticket and interface with Duo. If there is a need for collaboration, that is where I come in, and they introduce me to Duo, saying that they want me to collaborate on this particular design.

My experience with deploying Okta Platform shows that it is not that difficult to deploy, but the integration is challenging. The integration, the tweaking, the configuration, and the tailoring require significant effort.

Compared to Cisco, deploying Okta Platform is a little bit harder. Cisco Duo is quite straightforward.

Regarding costs, I think Okta Platform is more expensive compared to Cisco, but it is less expensive when compared with Oracle.

The reason we recently switched to Okta Platform was a decision made while I was not on the project, as I was with the Air Force at the time. The decision was made by a different branch, I think with the Marines, who were using it and then said that Oracle is obsolete. It was presented as a short message: 'We are using Okta Platform and it works well.' They then asked me to investigate and see how we could use Okta Platform integrated with Oracle.

The improvements I already mentioned are based on the fact that IAMs are evolving, and integration with other components is important. My experience with Okta Platform's integrated PAM capabilities involves many steps. There are many steps, and you have to do this, but as long as the document is fine at the start, it is a trial and error process. If it works or not, then you are going to repeat the whole thing and try a different scenario. The project management does not always see the effort behind all of this tweaking Okta Platform to do what they want it to do and meet their business requirements. I would rate this review a seven overall.

Hybrid Cloud

My job title at FNTS is Senior Security Analyst.

I have been using Okta Platform for three years.

My main use case for Okta Platform is multifactor authentication.

For multifactor authentication in my organization, to log into specific sites, we need Okta Platform as a multifactor authentication to get in.

The process has made logging in easier and more secure for me and my team.

The best features Okta Platform offers are easy SSO, strong security, and improved productivity.

Out of easy SSO, strong security, and improved productivity, the single sign-on has had the biggest impact for my team because it protects effectively and signs on without problems.

Okta Platform has positively impacted my organization with easy single sign-on, as we need single sign-on multifactor authentication for various things and Okta Platform is very secure.

I have definitely noticed specific outcomes such as fewer help desk tickets, as it is very straightforward, streamlined, and easy to use.

I think the setup in the beginning can be a bit of a learning curve.

I have been working in my current field for seven years.

Okta Platform is stable.

Okta Platform's scalability is good.

The customer support is good.

I would rate the customer support on a scale of 1 to 10 as a nine.

Positive

We previously used Duo and switched because we thought Okta Platform had better features.

I think the setup cost was pretty good, but the pricing is moderate.

I am not sure about Okta Integration Network's capability to enable faster deployments, as I have not used it in that capacity and I have not deployed it.

I would assess the role of Universal Directory as a single source of truth for user identities in my organization as it works effectively.

I cannot describe the impact of automated lifecycle management on onboarding and offboarding processes in terms of efficiency.

I have not had any experience with Okta Platform's integrated Privileged Access Management, PAM capabilities, so I cannot compare them to using separate tools.

I have seen a return on investment, as there have been fewer employees needed for multifactor technical responses, and the number of people to assist with tickets has gone down since Okta Platform is a really easy system to use.

I think the setup cost was pretty good, but the pricing is moderate.

Before choosing Okta Platform, we evaluated other options, including Microsoft.

I would advise others looking into using Okta Platform to look very carefully at the pricing and move forward.

My company does not have a business relationship with this vendor other than being a customer.

I find this interview satisfactory and do not think anything needs to change for the future.

I would rate this review an overall eight out of ten.

Private Cloud

Amazon Web Services (AWS)

Okta Platform is my primary tool for implementing Single Sign-On and Multi-factor Authentication. I use Okta Platform primarily for securing employee access, along with leveraging it for lifecycle management to automate user onboarding and offboarding.

The Single Sign-On and Multi-factor Authentication features are the best that Okta Platform offers. These features make my work easier and more secure by automating joiner, mover, and leaver processes, so when a new employee is added to our HR system, their account is automatically created in Slack, Zoom, and the applications we use, increasing productivity without wasting time.

The sharing of secure access via user groups allows us to instantly provision access to shared tools for our remote project teams, ensuring they have exactly what they need when they join a call or project. Okta Platform has positively impacted our organization by dramatically improving our security posture, enforcing Multi-factor Authentication across all applications, and increasing productivity by allowing employees to access all their tools with one set of credentials.

Okta Platform could be improved by offering more out-of-the-box templates for advanced workflows and making the administration console faster when searching through a very large group of users.

I have been using Okta Platform for approximately five years to manage identity and access across our global workforce.

We have seen a 60% reduction in password reset help desk tickets and a significant decrease in the time it takes to onboard new employees from when they join.

I advise others looking into using Okta Platform to start with a clear group strategy before beginning; if the requirement for groups and naming conventions is organized from day one, setting up security policies and automated provisioning will be much easier. I would rate this product 9 out of 10.

Public Cloud

Amazon Web Services (AWS)

My use cases for Okta Platform involve having a single place for authentication, as my company requires it for all of our applications that we use with our organization, which includes SAML and SSO. It's a critical piece for authentication, and the token generally lasts about eight hours based on our company's configuration, allowing us to sign in once a day and eliminating the need to enter credentials multiple times for different applications. Okta Platform authentication is essential because it minimizes the hassle of signing into multiple applications while maintaining security. Essentially, all my critical apps are secured with Okta Platform, which also provides features like second-factor authentication through cell phone verification or facial recognition. Overall, it's very functional and an integral part of our business processes.

Regarding how Okta Platform helps secure access to cloud infrastructure, APIs, containerized workloads, or AI services in our architecture, I can't provide an authoritative answer on how security is hardened since I wasn't involved in that aspect. However, I know that it provides security. My company has been using it for four years without plans to change because it remains secure, even as we increase our internal applications and expose some to clients.

The workloads secured by Okta Platform are hosted across multiple cloud providers, including AWS, Azure, and some GCP, so it encompasses all of those.

For AWS, we have integrated EC2 instances with Okta Platform, and I'm not sure about other services or buckets related to the things you mentioned, such as Amazon Voice.

I see the benefits of Okta Platform immediately upon deployment, as it saves time. Dealing with multiple authentications without a federated system is time-consuming, requiring different passwords for different applications, which is a hassle. As soon as Okta Platform was implemented, there was an immediate improvement in the ease and speed of secure authentication.

Personally, I have noticed measurable security and operational improvements since implementing Okta Platform, primarily due to the ease of access it provides in a more secure manner while saving time.

What I dislike about Okta Platform is that sometimes there has been some downtime. It doesn't happen often, but ironically, it did occur on a day I knew this call was coming, leading to a brief period when Okta Platform authentication didn't work. We had to rely on third-party IT support to resolve it. When this happens, it stops us from accessing what we need until the issue is fixed.

I have to mention some occasional downtime with Okta Platform. It doesn't occur very often, but when it happens, it's crucial because you can feel stuck without it.

I have been working with Okta Platform for just over four years.

Regarding stability, there hasn't been much to note aside from some occasional downtime, but I appreciate the different options provided by Okta Platform for verification. You can manually enter a password, use push notifications, or facial recognition, which can be more convenient depending on the context, whether mobile or at a desk.

I believe Okta Platform has been scalable. My company has integrated all major applications, and it has supported our growth without issues.

I've contacted internal company IT support a few times while learning the intricacies of Okta Platform, but I've never reached out to Okta Platform's direct customer support.

Positive

My organization hasn't tried any alternatives to Okta Platform, and I personally haven't had the need to seek them out. Some people look for alternatives such as password managers, but those are not the same. Implementing a solution such as Okta Platform isn't straightforward without a team behind it, so once it was working here, there wasn't a felt need to explore other options. I'm unsure of what the previous system was, but I believe they considered Cisco Duo at one point without ultimately proceeding.

The initial deployment of Okta Platform was easy and without any significant bumps, as far as I know.

The deployment of Okta Platform involves a lot of collaboration across the security team, working with the CISO to ensure adherence to standards such as SOC and FINRA. Though technically it's not a one-person job, my company wouldn't implement it that way either, as there is always a team behind it.

I probably don't think of anything else, as Okta Platform does what it intends to do. Given my experience in the field, I recognize that these tools work well, but they're only as effective as their configuration and security hardening. My company has done an excellent job with Okta Platform, and I feel it's a quality product because it effectively integrates single sign-on and SAML authentication.

I'm not entirely sure if our organization uses Okta Platform to protect non-human identities, such as service accounts or AI agents, as we've rolled out chatbots and are developing them. I can't confidently answer that question.

Okta Platform does help address specific industry or regulatory requirements, such as those in healthcare and financial services, for both our organization as an outsourced IT service provider and internally when accessing platforms.

On my end, there are updates from time to time for apps on mobile devices or operating systems that need to be addressed, but company policies manage updates for company-owned workstations, so it's not too burdensome.

I'm not aware of any formal partnerships with Okta Platform in my department, so I can't speak to that.

I would rate this review an 8 overall.

I don't have many details about Okta Workforce Identity. I use the tool just to sign in to different applications that we have. We basically set up Okta Workforce Identity in our mobile phone. We do the scanning part and then enter our official email address and acknowledge that. They will send a code to the mobile phone. Once that code is authenticated, we are good enough to use that tool going forward. That's the initial setup we do on Okta Workforce Identity.

Okta Workforce Identity is really useful because all internal users that we have in our transfer server have now moved to it. In the progress, it's a suite, as it's a part of MOVEit Automation as well as MOVEit Transfer. On the MOVEit Transfer, all internal users in our company have moved to Okta Workforce Identity single sign-on option. The benefit was addressing issues where people were using incorrect passwords. When they continuously put incorrect passwords, their IP would get locked and their account would get locked. Additionally, there were very few users who kept passwords in secret tools or KeePass tools. Most of them were putting the passwords either in mobile phones or in OneNote or text documents where the data could get breached easily. To deal with all these issues, Okta Workforce Identity is a perfect tool where internal applications can be signed in using your authentication tool itself. It functions as two-factor authentication.

I am using Okta Workforce Identity for login purposes only.

The best feature is the speed and execution of Okta Workforce Identity. The moment you click on single sign-on, you immediately get the notification on your mobile phone, then you do the authentication and within a second you get authenticated. The entire customer experience is very good. The user interface is pretty simple, straightforward, and really good.

Multi-factor authentication in Okta Workforce Identity is very useful so people who do not have access or are trying to access using just a user ID and password will be completely blocked because of this two-factor authentication. You will get the code, and as your device is authorized in the system, only that device can be used for the authentication purpose. A third person trying to access or hack your data will not be able to do that anymore. Additionally, you don't have to remember your passwords going forward. Previously, every 60 days or 90 days, passwords kept changing. With the two-factor authentication or single sign-on option in Okta Workforce Identity, you don't have to remember it anymore or write down passwords in plain text. If something goes wrong, we have the IAM team which can unlock your account immediately if you have issues.

Currently, in Okta Workforce Identity we get the two-digit authentication code. Instead of getting the two-digit authentication code, if we had an option to do fingerprint verification, that would be beneficial. We have already secured that only the device where we have installed Okta Workforce Identity can do the authentication. However, if that phone or device gets stolen, somebody else can log into the system using that code. If there was a fingerprint option, then only the person who has already added their fingerprint on their mobile phone could access it. This would provide double protection.

I started using Okta Workforce Identity four months ago in our company.

I didn't have any single sign-on technologies before Okta Workforce Identity. I started with AWS and then adapted Okta Workforce Identity.

The initial setup of Okta Workforce Identity is straightforward. We haven't encountered any issues because if we had, we might have gotten emails from the security or the IAM team who handled the installation. Nothing went wrong. It was pretty smooth.

I have seen ROI from Okta Workforce Identity. It was a great implementation. Initially, we had multiple places where we had to store links in browsers to access different applications. We don't have to do that any longer now. We have our dashboard to log in via Okta Workforce Identity. Once logged in, it shows our company's portal where we see different applications. When you click on an application, you automatically get signed into that particular website.

Most of our internal applications are getting migrated to Okta Workforce Identity. We started initially with AWS, then we added Confluence. We also migrated the internal rewards point feature. The entire migration is being done in a phase-wise manner. Currently, 15 applications have been migrated with only a few remaining that we use daily.

I haven't used the Lifecycle Management feature in Okta Workforce Identity. The decision to go with Okta Workforce Identity might have been due to the best customer experience and favorable long-term license deals.

I would recommend Okta Workforce Identity because it's a security standard. Two-factor authentication is always better than using user ID and password. The entire world is now dealing with data and we have to secure it as much as possible. For file transfer, we are using encryption and decryption. Similarly, for accessing internal applications or internal websites, I would recommend using Okta Workforce Identity or any related tool which can provide two-factor authentication as it's a standard nowadays.

I rate Okta Workforce Identity 9 out of 10.

My main use case for Okta Platform is managing the workforce identity in Identity Engine, which helps the organization maintain the workforce identity in a seamless manner for provisioning and deprovisioning.

For workforce identity management with Okta Platform, I mostly use it for the joiner, mover, and leaver process, and whenever it comes to the application, I am integrating SCIM provisioning to make the users aligned with the applications on the fly.

Regarding my main use case for Okta Platform, for access governance, I maintain all those certifications as well, and for non-human identities, I also manage them in Okta Platform itself.

The best features Okta Platform offers are workforce identity management, access provisioning, and single sign-on.

Okta Platform's single sign-on and access provisioning features have helped my organization by being quite seamless. The user gets onboarded on the fly with Just-In-Time provisioning enabled, which helps propagate the users across the organizational applications.

The behavioral detection and threat detection features of Okta Platform are very good. They provide insights into the behavioral pattern of user access management and inform the administrator of any kind of intruder detections or threat analysis, making it very useful to use Okta Platform for maintaining identities.

Okta Platform has positively impacted my organization by bringing more automations with Okta Workflows, resulting in a drastic change in the manual efforts, as most things are being automated and Okta Platform is very convenient with their workflow management.

The impact on manual efforts with Okta Platform means that for some activities in my day-to-day business that used to take around an hour or two, it is now reduced to seconds, and I am getting things done much faster.

In terms of improvement, Okta Platform can focus more on governance and posture management.

The needed improvements mostly pertain to the ISPM, especially in posture management.

This means that whenever there are changes or a change audit occurs, Okta Platform should provide details on what exactly is happening, who is making the change, what values are changed from past to the current one, providing more insight into the change audit process.

I have been working for around nine years in the current field of IAM domain.

Okta Platform is stable.

The scalability of Okta Platform is quite flexible.

I find Okta Platform scalable, as it can easily handle more users or workloads as my organization grows.

The customer support from Okta Platform is quite fast.

I would rate the customer support a nine out of ten.

I previously used NetIQ, which has a good engine, but the operational and maintenance costs are quite high, which is why I switched.

I have seen a return on investment with fewer employees needed due to workload or user base considerations, making it very cost-effective.

My experience with pricing, setup cost, and licensing for Okta Platform is very convenient. I have a good partnership with Okta Platform for negotiating pricing, and while this will not be disclosed, it is flexible enough.

Before choosing Okta Platform, I evaluated other options such as SailPoint and Saviyant, but I found Okta Platform to be more convenient, leading me to choose it.

My advice for others looking into using Okta Platform is that if users are more cloud-focused, Okta Platform is very convenient for integration. It is important to consider the infrastructure and applications used within the organization to ensure compatibility with Okta Platform, especially with legacy applications. I would rate this product an overall eight out of ten.

My main use case for Okta Platform is single sign-on.

As a specific example of how I use Okta Platform for email sign-on in my organization, we log in to our browser and then enter our username and password, and then we receive a Google Authenticator code, a six-digit code which we enter, and then we can log in.

Okta Platform offers features that allow you to log in to multiple applications, including GitLab, Looker, Workday, and many more with single sign-on.

Out of those applications, single sign-on is the feature I find most valuable because it saves a significant amount of time for the user. If any new user is onboarded into the company, instead of giving them access to all the applications individually, we add them into the Okta Platform group and that is all that is needed. They can access all the company-based applications within approximately one minute.

Okta Platform has positively impacted our organization as it eliminates the manual intervention work of providing access to new users who join the company to multiple applications. Instead of that process, providing access to Okta Platform allows them to access all our applications. The time saved is approximately two to three hours.

I do not see any bugs or improvements needed in Okta Platform because it functions perfectly, and I have not faced any issues with Okta Platform in my career.

I have been using Okta Platform for seven years.

Okta Platform is stable.

Okta Platform's scalability is good.

I have not faced any issues, so I have never contacted customer support.

I did not previously use a different solution before Okta Platform.

I have not set up Okta Platform in my organization because when I joined, it was already deployed.

There is no specific team mentioned for the implementation.

I have seen a return on investment because only a few people are required to manage Okta Platform, and it saves a significant amount of time for us, approximately four to five hours.

There is no information provided regarding the setup cost.

There is no mention of any alternate solutions being considered.

If you are looking for single sign-on, then Okta Platform is the best option; you can confidently go with it.

Okta Platform could be a little faster. I have given this solution an overall rating of 10 out of 10.

Public Cloud

Google

Okta Platform serves as a single sign-on tool in our daily operations. We use Okta Platform because we have access to numerous applications, and it is impractical to add all websites to a favorites bar or remember all the passwords for these applications, tools, and websites. We have configured Okta Platform for every person, allowing them to connect to the tools and applications through single sign-on.

The best features Okta Platform offers are the ease of use and the ease of access.

The ease of use comes from the very user-friendly interface, which allows us to select the application we need to sign on to easily. The ease of access stands out because it can be accessed through one link only.

Okta Platform has positively impacted our organization because our staff can connect to all tools and applications we use from a single location, which has saved us time.

When we have a new joiner who does not know the links for our tools or applications, they spend time asking other users and may engage in lengthy conversations. Because of that, we advise the new joiner to sign in to Okta Platform, and they will find all the applications and tools they need.

Okta Platform can be improved by enhancing the mobile application because sometimes it has issues. Specifically, sometimes the OTP is not received for the mobile application.

I have used Okta Platform for approximately one and a half years.

My advice to others looking into using Okta Platform is that it saves money and effort and saves time, making it a great solution for your company. I rate this product 9 out of 10.

Hybrid Cloud

Amazon Web Services (AWS)

As an integrator, I work with Okta Platform.

Okta Platform can be used for IAM and IGA; it is a cloud-based solution for Identity and Access Management, as well as Identity Governance and Access.

As an integrator, I find Okta Platform user-friendly with a good number of connectors, making it easy to integrate with applications, and it is easy for SSO implementation and MFA implementation.

Lifecycle Management is configurable in Okta Platform; you can configure the joiners, movers, and leavers process with this product.

Okta Platform is a cloud-based platform, so you do not have to take care of installations as you would with on-premises solutions for SailPoint or Oracle Identity Management, which is a big difference.

Based on requirements, context-aware policies of Adaptive MFA are configurable, which is a plus point, as you can configure it based on certain requirements, such as adaptive authentication based on behavioral patterns and logging in from one place to another.

It is time-saving, which is definitely linked with money; a lesser number of users are required to do the manual work, so it has that impact on money as well.

I have not encountered any negative points for this product.

For log monitoring, after a certain period of time, logs are deleted, such as after three months, and you have to configure it using a separate or external SIEM connector, such as Splunk or Cortex XSOAR, because after 90 days, the logs will be deleted, so we have to take an export manually or add one external log monitoring solution.

If the organization is big, I can say Okta Platform is affordable; however, for small-scale industries, I would not recommend it, but for medium and enterprise organizations, it is good.

I have been using Okta Platform for approximately one to one and a half years.

Okta Platform is a stable product.

Okta Platform is a scalable product.

I can rate Okta Platform support at approximately eight or nine out of ten.

Positive

I have worked with Oracle Identity Management and SailPoint as other access management tools before.

I have not worked with Universal Directory in my case, and I have not worked on it recently.

Okta Platform is an IGA solution, so in terms of PAM capabilities, it is not working as PAM for storing passwords or secret vaults, such as Delinea or CyberArk; it is a completely different product.

Public Cloud

Other

Okta Platform was originally implemented to provide remote authentication for our hosted applications to authenticate against Active Directory for users accessing them from the internet. Then we started using it for multi-factor authentication for our remote access and VPN remote access. Now we have been looking at it for securing the desktops with multi-factor authentication.

Let me give you a specific example of how we use Okta Platform in our environment. We do not allow access to our internal Active Directory. Our DMZ does not have access to our internal Active Directory. Any external application or hosted application that needs to authenticate users against Active Directory has never been able to do so because we do not allow these hosted applications or our DMZ to have access to our internal Active Directory servers. We block that kind of access for security concerns. Okta Platform is different because the Okta agents are configured to make outbound calls on our internal network, continuously polling for authentication requests. When they receive authentication requests, they then authenticate against our internal Active Directory servers. There is never any inbound traffic from the internet to our internal infrastructure. That was the main point which caused us to select Okta Platform many years ago. It was the only solution that worked this way. This allows authentication for external users without breaching any of our firewall rules, without needing any reverse proxy or any tunnels from the internet to our internal servers.

Okta Platform offers flexibility that was very useful. It allows us to have multi-domain and multi-tenant authentication with entities that we do not control, but still allows us to use a single set of authentication rules and security rules with Okta Platform that is also able to authenticate users from other entities to give them access to our resources, authentication-wise, but still allowing us to select and enforce our own security rules.

Okta Platform's best feature is the ability to authenticate users without needing any inbound connections to our secure internal Active Directory servers on our internal network. That is the main feature which caused us to select Okta Platform and will continue to use Okta Platform.

This feature impacts my daily operations by allowing us to use external applications which we would not have otherwise used because we would not have allowed authentication from the internet unless it was implemented the way Okta Platform implements it. Had we been forced to do so, we would have had to open what are called holes in our firewalls to allow for authentication and that would have dramatically decreased our security posture.

Okta Platform has positively impacted my organization by improving efficiency, security, and user satisfaction by allowing us to use external applications.

Okta Platform can be improved by lowering the price, as the price is very high.

Besides pricing, there are other things I think could be improved with Okta Platform, such as the strength against distributed attacks from the internet. We would like more flexibility and the ability to stop attacks when there is password spraying or brute forcing accounts. There is work that can be done there to improve the features.

I have been using Okta Platform for about ten years or possibly longer.

Okta Platform is stable, but it can have issues with downtime or reliability.

Okta Platform's customer support has been average in my experience. We handle most issues ourselves, so approximately once every few years we have to contact support, and it has been neither good nor bad.

Okta Platform was the first and only solution I used; I did not previously use a different solution.

I have not seen a return on investment as an IT administrator who deals with security, not the financials.

My experience with pricing, setup cost, and licensing for Okta Platform is that it is expensive and complicated. We do not handle purchasing ourselves as we have a purchasing department that takes care of all the paperwork. For us, it is just an upfront cost that is excessive.

I did not evaluate other options before choosing Okta Platform as it was more than ten years ago. However, we did evaluate alternatives, and Okta Platform was the only one that matched our requirements to authenticate without any connectivity to our internal network.

My advice to others looking into using Okta Platform is to not discount the fact that authentication can be made without any connectivity to the internal network, as that was critical for us. I give this product a rating of nine out of ten.

Public Cloud

Other