Okta Platform Reviews

Most of what I appreciate about Okta Platform are the no-code features that I have found excellent, as you have a very low requirement to code. Even if a new teammate comes in and tries to get familiar with it, after some basic training, they will be able to perform some minimal tasks that are repeated processes for us. It is quite easy to learn from my perspective if you have basic IAM knowledge. If you understand the concept, a new person can come in and get up to speed very quickly. You don't have to do very extensive training as you might have to do for some other tools to handle advanced tasks. With five to six months of experience, we can put a person on policy creations.

For me, learning to use Okta Platform was quite easy because I have been in this space for around seven-plus years. I had previous knowledge of ForgeRock and SailPoint, so it was easy for me to transition to Okta Platform because I had knowledge of the concepts.

The major problem we face with Okta Platform is pricing because most of our clientele move away from Okta Platform because of the pricing. If someone is looking for on-premises solutions, they usually don't choose Okta Platform.

They predominantly try to go for Ping rather than Okta Platform because Ping provides a very wide variety of concepts and tools and details their tool on a very specific level, particularly their on-premises tools. Anyone who invests has to pay a higher price, and if with the same kind of structure they can get some other enterprise-grade tool that caters to all those things, they will definitely choose Ping rather than Okta Platform.

I have approximately three to four years of experience working with Okta Platform, from the time I started working and even before that.

The only issue I faced was once at the start. I have worked with around 50,000 users. Right now, the recent client has more than that, but on average, around 50,000 in a typical scenario. I have never seen drops in Okta Platform systems.

I have contacted technical support or customer support multiple times, but not through standard channels. We are a technical partner with Okta Platform, so we have a channel open all the time. I have been in contact with them for different types of RFPs, and even right now, I am still in communication with Okta Platform support.

I think the quality and speed of support for Okta Platform are among the best. The way they respond and the quickness in terms of when you raise an issue through technical channels such as creating a support ticket, they respond back within the SLA they have provided, which might depend on the kind of service the client has signed an MOU for. It can either be 24 hours or 48 hours based on severity. They do respond within that time, whichever they have agreed on.

I give them a score of eight because I have seen them respond in detail, and you usually don't have to follow up on that. Sometimes, with those kinds of detailed scenarios, there might be misinterpretation at the level where you misunderstand something in the question, and that follow-up can be tricky.

For me, the initial deployment of Okta Platform was already completed for most of the clients because you get built-in support from Okta Platform, so that is majorly the case. For the current client, the tool itself is not decided, so I have not worked on an Okta Platform deployment.

I am majorly on the development and implementation side. For Okta Platform, I have not seen much maintenance happening. There was only once I faced an issue, and that was at the start of my career, but I have never faced that kind of issue in Okta Platform since.

Pricing-wise, Okta Platform is higher compared to the other tools, and my current client actually moved away from Okta Platform because of that reason alone.

Right now, we don't have a tool selected on our client's side, and we are mostly targeting Ping because that caters to all their requirements, and the costing is lower than Okta Platform.

I think the score I give to Okta Platform overall will completely depend on the use cases each client has because it might vary. From my personal opinion, I would rate it around eight because I think there are many things Okta Platform has that are best in terms of IAM solutions. However, there are still many things that other platforms are doing that are missing in Okta Platform. From my perspective, Okta Platform is currently trying to move towards IGA as well, but there are still some areas for improvement. 

My customers approach me to integrate with Okta Platform. I have configured multiple AWS accounts to Okta Platform.

My usual use case for Okta Platform is to onboard AWS accounts into Okta Platform and add the users AD groups into Okta Platform and add those AD groups to integrate with the AWS account, which is my job.

I find the most useful feature of Okta Platform is that it allows the preconfiguration of multiple applications, eliminating the need for customized application onboarding, which is very helpful for me to configure multiple applications such as AWS, Azure, Zoom, Salesforce, and more than 1000 applications in Okta Platform dashboard.

Okta Platform has had a lot of positive impacts on my organization. For example, it is very difficult to disable user access in multiple places, but once we implement Okta Platform, we just need to disable it at the AD level, and the rest gets taken care of by Okta Platform.

A couple of things need to be improved at Okta Platform level. In AWS, we are using tag-based policies to enforce the RABC, but when trying to configure tags in Okta Platform level, we are not able to configure them.

At Okta Platform level, we have not yet configured the machine-to-machine configuration. It is very difficult for me to create the API accounts to enforce. For example, when we generate temporary credentials in AWS, it is challenging to use Okta Platform level because there are no features to create CLI-based temporary credentials.

I would like to improve the tagging on Okta Platform. For every identity, we need to create a tag. Instead of hard coding in AWS, we use tag-based authentication, allowing access based on tags associated with resources.

From my perspective, everything is good on Okta Platform except for the tags that need to be improved.

I have been using Okta Platform for three years.

The stability of Okta Platform is good. We have not faced any major issues or outages in the last couple of months.

Because we are using the cloud for Okta Platform, it is automatically scalable. There is no need to inquire about scalability since it scales as required.

I do not often communicate with the technical support of Okta Platform.

I have never communicated with the technical support of Okta Platform.

Before Okta Platform, we used Entra ID or Azure AD for similar use cases.

The decision to stop using Azure AD and start with Entra ID is not my call, as management decides. From my perspective, technically, Okta Platform is very user-friendly for application onboarding, whereas Entra ID is a bit more challenging for onboarding applications.

I went straight with Okta Platform and did not consider anything else.

I did not evaluate other options besides Okta Platform.

I am not sure about the GenAI aspect, but Okta Platform is very helpful for integrating the identity center and allows us to create multiple individual accounts using the IAM or at the organization level using the identity center.

I am in the healthcare industry, but I am not sure how Okta Platform helps address specific industry or regulatory requirements.

I do not know about the regulatory environments of the healthcare industry regarding Okta Platform because I am not managing health standards or other governance standards.

I have not noticed any measurable security or operational improvements in my cloud-based workloads since implementing Okta Platform, but I find it very helpful to utilize MFA or UBIKeys or other security keys to enforce the login mechanism.

I do not know the pricing details of Okta Platform because I am not the appropriate person to discuss pricing matters. The purchasing department will take care of those.

I would rate this review as an 8.

Public Cloud

Amazon Web Services (AWS)

Okta Platform is essentially the gateway for everything we do. We have the Okta app on our phones and computers, and it is the only way we can access any of our interfaces on a day-to-day basis, including work messaging on Slack or any of our apps. We go through Okta FastPass to gain access. Every 60 days, I have to reset that on my phone by logging out of everything, doing Face ID, and verifying my credentials before I can log back in and keep everything secure. Additionally, we have to update our password every 180 days or so. I basically start my day every morning with Okta identification or verification.

Okta Platform helps to secure access to cloud infrastructure, APIs, containerized workloads, and AI generative AI services. It pairs well with some of the AI tools we use. I even have a verification method for ChatGPT and Glean, which is another AI interface. Okta Platform essentially applies to anything I use on a day-to-day basis. I do not get any pop-ups throughout my day, which indicates that it is securing the interface or network I am using or even just the application.

Okta Platform protects our benefits and payments app through Workday, so it definitely protects my benefits, my pay information, and any type of personally identifiable information such as first name, last name, and Social Security number.

Ease of use is what I value most about Okta Platform. It is not difficult to learn or navigate. Once you have a username and password, you can have your computer memorize it. On my phone, I use Face ID so that I am not having to type in my password every single time, but it does make things very secure. If I ever were to leave my laptop anywhere by accident and not be able to recover it that same day, I would be able to trust that it would block anybody from getting access to anything because that is something you have to log into every day. Ease of use and the ability to trust the product are what I value most.

Okta Platform does not recognize when I have already verified myself once on my HubSpot login across multiple tabs. I have to verify myself for every single tab. If there were a way to recognize that I already verified myself on that URL or domain and just give me access to the rest of the tabs instead of having to click one by one, that would be an improvement.

Okta Platform does not recognize when I have already verified myself once on my HubSpot login across multiple tabs. I have to verify myself for every single tab. If there were a way to recognize that I already verified myself on that URL or domain and just give me access to the rest of the tabs instead of having to click one by one, that would be an improvement.

I have been using Okta Platform for at least five years.

Okta Platform does not lag. The only thing that might happen every once in a while is that I will click Okta FastPass, it will spin, I will click submit, and then nothing will happen. I just have to refresh my tab and then do it again. However, that happens pretty infrequently.

Okta Platform definitely supports our whole company, which is not small at all. It is good to know that it can support both smaller and larger teams.

I have not had to contact Okta's technical support or customer support, which is probably a good thing.

Negative

I have used Cloudflare in the past. I know it is not really a direct competitor, but that is maybe the only thing else that I would mention.

I did not do the initial deployment, but when I was first brought on, I had to go through the whole setup of everything to tie to my email address and all my information to be a verified user on the account for Okta Platform through HubSpot. It was pretty easy. I had to set it up on my phone, download the app, and scan the QR code. It was pretty simple on both my laptop as well as my phone.

Okta Platform does not protect non-human identities in my environments.

We are providing identity access management to the customers with Okta Customer Identity, and then application integration, user onboarding, and related functions.

I'm a senior consultant using Okta Customer Identity.

We are the implementers of Okta Customer Identity as users.

The most valuable feature of Okta Customer Identity is the application interface with SSO. Integration with SSO helps us make use of the credentials. Once we log in, we get the opportunity to explore many applications within the organization with the same login, with no need to log in again.

Adaptive authentication in Okta Customer Identity is a flexible feature that is very secure and user-friendly. The authentication is more complex for man-in-the-middle attacks while remaining useful for end users.

Okta Customer Identity's API gives a clear view of how user onboarding takes place, so we can easily configure with Postman. We can onboard and off-board users, which is very flexible through the APIs.

Regarding multi-factor authentication, it helps reduce unauthorized access in our organization. We are using passwordless authentication with Okta FastPass on mobile devices. Users can get authenticated with two-factor authentication, first entering the password, then directly using the second factor authentication with Okta FastPass.

It is complex when adding it for the first time to users of Okta Customer Identity. For end-users and new users, it can be complex to use.

Okta Customer Identity analytics and reporting tools do not help much to improve customer engagement strategies.

Training should be provided to novice users. There are multiple online learning resources in the Okta documentation part, which users can access free of charge.

I have been working with Okta Customer Identity for six years.

There are no doubts regarding the stability of Okta Customer Identity. It is scalable and we can directly make use of this tool.

The solution is scalable.

The setup for Okta Customer Identity is straightforward.

The price of Okta Customer Identity is acceptable.

For those planning to use Okta Customer Identity, MSA and SSO are among the best features that can be recommended for users. We also have direct integration with Active Directory. There are many features that will be helpful for organizations to easily integrate applications and manage user onboarding and off-boarding.

The solution is deployed on the cloud and I did not purchase it through AWS Marketplace. I usually buy for the entire organization.

I rate Okta Customer Identity 10 out of 10.

Public Cloud

Microsoft Azure

I usually used Okta Platform for managing user identities and ensuring secure access to our applications.

Okta Platform helped me secure access to cloud infrastructure, APIs, containerized workloads, and AI/GenAI services in my architecture, enhancing our security posture significantly.

Okta Platform protected non-human identities in my environment, such as service accounts and machine-to-machine access.

The features or capabilities of Okta Platform that I have found the most valuable include its single sign-on and multi-factor authentication.

The positive impact and benefits I have seen from using Okta Platform involve enhanced security and streamlined user access.

Specific industry and regulatory requirements that Okta Platform helped me address in my cloud environment were critical for compliance.

Since implementing Okta Platform, I have noticed measurable security and operational improvements in my cloud-based workloads.

Okta Platform could be improved or enhanced by adding more integration options for third-party applications.

I have been working with Okta Platform for a considerable time now, which has provided me with great insights into its functionalities.

Okta Platform's stability and reliability are impressive, which is crucial for our operations.

My experience with the technical support of Okta Platform and their customer service was positive, as they were responsive to my inquiries.

I would rate the technical support from one to ten as an eight, appreciating their effectiveness though there is always room for improvement.

I changed the previous solution and decided to switch from Adaxes to something else because we needed more robust features, and with large companies offering solutions such as Okta Platform, it became inevitable.

I participated in the initial setup of Okta Platform, which allowed me to understand its configuration better.

I found everything straightforward during the initial setup; however, I did encounter some challenges with integration.

I have experienced a notable ROI from Okta Platform, which has justified our investment in it.

I last engaged with Okta Platform around this time of the year.

I was a customer of Okta Platform and found the solution to meet our requirements effectively.

The last time I used Okta Platform was relatively recently, and it still remains quite effective for our needs.

I did not participate in the decision-making process for Okta Platform purchasing, as that was handled by our procurement team.

I would rate this review an eight out of ten.

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.

Positive

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

Other

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 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

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.