Okta Platform Reviews

I started using Okta Platform when I led a team to build software and we encountered security issues. We were looking for the best SSO software platform that we could integrate into the system, and during my research, I came across Okta Platform. I have used it for the current system I am building, and I am currently using it to help with the SSO integration flow and MFA.

I use AWS to access Okta Platform.

Okta Platform provides centralized identity, which is one of the major benefits. For example, I use AWS, but if I want to access Okta Platform, my login details for AWS are not needed. Using it for building systems for customers allows companies to access their systems seamlessly through the same procedure, which makes the workflow easy for them. One of the things that helped us was implementing role-based access. One of the systems I built and led the team to develop was a super admin dashboard that extends through a complete chain. We were able to use Okta Platform to manage roles, and this is one of the key areas where Okta Platform has helped me significantly.

Okta Platform helps me secure access to cloud infrastructure, APIs, and containerized workloads. I have not integrated with AI before, but in terms of app redirects and the systems involved, when a user tries to access their application, there is a redirect to Okta Platform, and then Okta Platform verifies the user. That is how my workflow functions. My first application was supported by this architecture, and studying Okta Platform helped me develop that architecture because my previous architecture was not effective. I learned to have users access the application and then get verified by Okta Platform, which provides the token for them to gain access to the system. I believe this uses SAML, and it really works well for us to accomplish all of that.

I have not tried using Okta Platform to protect non-human identities in my environment, such as service accounts, machine-to-machine access, or AI agents, and I have not explored that area.

In the current system I am working on, which is one of the biggest and most complex projects I have completed, Okta Platform helps me address industry and regulatory requirements. The way the system is structured with user data, funds, and role-based assessments, my greatest satisfaction is that I can use Okta Platform to seamlessly manage all of this. Going forward, if I can use Okta Platform in AI and explore AI integrations, I believe I will be very satisfied.

I appreciate the authentication flow of Okta Platform because it is seamless and provides insight into how to easily automate the workflow for authentication and MFA so that it is easy to use within systems where one password or one user detail can be used to access various platforms. The workflow with Okta Platform is something I value.

Okta Platform provides centralized identity, which is a significant benefit. For instance, I use AWS, but if I want to access Okta Platform, my login details for AWS are not required. Using it for building systems for customers allows companies to access their systems seamlessly through the same procedure, which makes the workflow easy for them. Role-based access is one of the things that Okta Platform helped us implement. One of the systems I built and led the team to develop had a super admin dashboard that extends through a complete chain. We were able to use Okta Platform to manage roles, and this is one of the key areas where Okta Platform has helped me.

Before I can answer the question about specific improvements I would like to see in Okta Platform, I also have a question: how well does Okta Platform integrate with SIEMs? I have used Sentinel very well with Okta Platform, but I have not tried other systems. Based on the projects I work on, the demands change, and I do not have a specific company that I work with. If I am not using Sentinel and I want to use another SIEM, how well does Okta Platform integrate into it?

When I started, there were some UI challenges. The UI could be improved to make it better because I had to watch many tutorials to become familiar with their UI flow and integrations. Once I became familiar with the UI, it was good. Many beginners may not pick it up easily. I have experience with other systems before coming to Okta Platform, so it was easier for me. If someone is a beginner with Okta Platform, the UI should be simplified, and the language used should make it easier for them to understand the concepts and what they are trying to do. I believe this would really help.

I have been working with Okta Platform since September of last year.

We monitor the system, and based on our implementation, we have had several challenges where our systems stopped working. We monitor it through various platforms with our DevOps team. If any issues arise, we are able to catch them before they cause complications, so we do not have any issues there.

Currently, we are using Okta Platform at a moderate level, and we are considering scaling it depending on the user data we collect and the number of users coming into the system. However, we have not reached that point yet, so I cannot provide much comment about its scalability at this time. I believe that with the help of AWS and other platforms, we should be able to scale it seamlessly.

I have not interacted with the technical support or customer service of Okta Platform. I hardly go to customer service because of the community available for me to access other information.

I have not used any other solution of the same kind prior to working with Okta Platform.

For my first time, the deployment process of Okta Platform had challenges because I was a beginner and I did not put many configurations in checks. It really did not have anything to do with Okta Platform, but rather how I configured my back-end resources.

Someone helped me with the integration during the deployment of Okta Platform. I did not do it myself.

Personally, for the companies I have worked for, I cannot provide information regarding ROI with Okta Platform, but personally, it is good for me. My return on investment would be the fact that it makes my work easier and gives me a lot of room to integrate. It provides good architecture to prevent excessive loss of money and capital moving from one system to another. For me, who builds systems, the return on investment is that it cuts costs for me and makes it easier. For the company, the benefit is that I can use Okta Platform for them to manage their expenses.

The only service that I used before choosing Okta Platform was a spam protection system that helps with some security. That was the only other solution I considered.

Okta Platform helps me secure access to cloud infrastructure, APIs, and containerized workloads. I have not integrated with AI before, but in terms of app redirects and the systems involved, when a user tries to access their application, there is a redirect to Okta Platform, and then Okta Platform verifies the user. That is how my workflow functions. My first application was supported by this architecture, and studying Okta Platform helped me develop that architecture because my previous architecture was not effective. I learned to have users access the application and then get verified by Okta Platform, which provides the token for them to gain access to the system. I believe this uses SAML, and it really works well for us to accomplish all of that.

I would advise other organizations considering Okta Platform to prioritize security. The world of technology has evolved, and AI has advanced the work developers do. One belief I hold as an engineer is that security will not change; AI can never take that away from us. Therefore, if you are building anything, you should consider security and use the right tools to make your work easier. I recommend Okta Platform for SSO and role-based access control (RBAC) features.

Because I have not been using Okta Platform for a long time, I give it a seven on a scale of one to ten as a product solution, but this rating may change as I explore its features further. I give it a seven because I have not tried scaling systems yet, and there are many features and opportunities in Okta Platform that I am yet to explore. Based on my limited experience, I am giving it a seven, but as I explore more, I believe I could give it a ten out of ten.

Our main use case for Okta Customer Identity is that all of our in-house applications are under Okta. A user or customer has to log in to Okta Customer Identity and then they can access the application. It serves as our main SSO application which we are using.

The main features of Okta Customer Identity that I find most valuable are its security and easy accessibility.

We are using the self-service feature in Okta Customer Identity for almost one year now. Previously, it was not configured, but now we are using it.

We find Okta Adaptive Authentication useful as whatever feature we feel should be implemented and beneficial for users, we have implemented it. We use multi-factor authentication and it is 100% implemented. Multi-factor authentication is also useful for the security part for us.

The report functionality is another important part of Okta Customer Identity; we might need to check logs and other things. The report part is very much useful. I am 100% satisfied with the customizable options in Okta reporting features. This is a very good feature, and it is 100% implemented, so I do not want any changes because it is working as expected.

Stability and the UI/UX of Okta Customer Identity are fine as they are; I do not see any need for improvement in those areas.

From the user perspective, everything is good and no change is needed. I do not think any biometrical features for authentication or limitations from Okta Customer Identity on request systems can be added at this moment.

Some users face challenges after upgrades. Whenever we upgrade Okta Customer Identity, there is no challenge or blocker from Okta Customer Identity. However, I have seen cases where there might be issues with InTune or JumpCloud due to sync delays from their end; Okta Customer Identity was fine at that moment.

After Okta Customer Identity made an upgrade process, we had some challenges with the integration of Okta Customer Identity and Jamf. The only issue with Okta Customer Identity is after the upgrade process; we have some issues with the integration between Okta Customer Identity and Jamf. The only point for improvement is the upgrade process.

I have been working with Okta Customer Identity for more than three years.

I rate Okta Customer Identity a 10 out of 10 for stability; it is the best.

The scalability part of Okta Customer Identity is fine, there is no blocker and we can upgrade whenever we need.

Okta Customer Identity's technical support is fine; they help to fix tickets within the timeline and their support is very good.

Neutral

The initial setup process for Okta Customer Identity is simple.

I do not think there are other competitors to Okta Customer Identity in the market. In my previous company, we tried to switch from Okta Customer Identity to some other SSO authentication method, but we did not find anything relevant. We kept going with Okta Customer Identity.

We discontinued the license for Barista and have moved to Workato Genie. We implemented Workato Genie around six months ago. It is required for the sales team, and they purchased some licenses for the sales and marketing team in the US. We have configured that for IT as well. There can be multiple Genies according to the requirement. If you ask something for the Genie, there is a global Genie and it can redirect that task to the relevant Genie for sales, IT, HR, and other things.

We are not using Google except G Suite. We have some licenses for ChatGPT, but that is not for IT requirements. We are still using AWS, Okta Customer Identity, and Jamf; these are our main core business applications.

The main benefits Okta Customer Identity provides to users include single point of login for all applications and single authentication, which saves time and reduces frustration. If something is not working, users just open a ticket with the Okta team instead of reaching out to other application owners or POCs.

I give Okta Customer Identity a rating of 10 out of 10.

In my current job, we do rely a lot on Okta Platform but we are not using some more advanced features from them; we have some basic subscription with Okta Platform regarding the single sign-on product they offer.

In both my previous job and in this one, we are using it as our main identity provider for our employees to log in into as many apps as possible with it, just to keep things as secure as possible and provide a good employee experience. Instead of our employees having to remember a lot of passwords and credentials, they rely on one single Okta Platform account to access as many systems as possible.

We are not relying on Okta Platform to secure access to cloud infrastructure, APIs, centralized workloads, or AI/GenAI services in our architecture at this time. I know there are ways to leverage Okta Platform for securing APIs and servers, but we mostly rely on Okta Platform for human access.

We do have some service accounts that we rely on, but I wouldn't say we are using more advanced features from Okta Platform. We do use those service accounts to integrate with other platforms, but I understand that the question was mostly about more advanced features from Okta Platform.

Both in my current job and the previous one, we were in Fintech companies in the financial space. One of the reasons to go with Okta Platform is because they are a well-reputed company, providing some attestations such as SOC 2. We try to go with a reliable, reputable company that other companies in the same space tend to choose, so it's a no-brainer to go with Okta Platform.

Okta Platform is the gold standard when it comes to identity providers and the single sign-on experience. I haven't tested similar solutions or any of the competitors, but I'm happy that both companies I worked for decided to go with Okta Platform, which is the gold standard. Most documentation out there provided by other platforms that integrate with Okta Platform usually has an Okta Platform sample; they document how to integrate with Okta Platform, and they may not do the same for integrating with other platforms. Their documentation is pretty good, and there are some communities built around Okta Platform as well. I participate on the Mac Admins Slack, which is a large IT community with a few channels dedicated to Okta Platform products or services, and there is also an Okta Admins community with Okta Platform employees engaged. I appreciate that they build a community around their product, and I can reach out to them on these other channels instead of having to open a ticket with them.

They have good documentation and there are subject matter experts engaging in these communities, including some Okta Platform employees. Their user interface is pretty good.

Okta Platform certainly speeds up the onboarding and offboarding process for employees. When we onboard them, in most cases we only need to grant them their Okta Platform credentials and they will be all set with their accesses. It's also easy to add new apps; if someone joins the company and they have all the apps they need, but then someone requests access to some other app, it's easy to grant them access to that app without jumping through hoops. Similarly, when it comes to offboarding, we know that deactivating their Okta Platform account is removing the keys to everything they have access to. In my current company, we don't have the lifecycle management product by Okta Platform, which automates the provisioning of users across platforms, but I used that at my previous job and it was a time-saving feature.

I have my own wish list of things that I would like Okta Platform to have. They released some features related to device access, such as Okta Device Access, which is an add-on that requires payment. I would expect Okta Platform to include more features over time in their less expensive subscriptions. I wish Okta Workflows could be included in a better way; we currently only have five workflows available, which doesn't provide much value. More workflows available in a paid subscription would be beneficial.

With AI permeating every service, I would like to have some kind of AI chatbot available on Okta Platform interface to ask questions about Okta Platform and how to integrate things. I relied on Google's AI chatbot to ask similar questions, but I would feel more confident asking them to an Okta Platform AI bot. I think someone mentioned there may be something coming from Okta Platform related to this.

I have been working with Okta Platform for about five or six years.

I haven't had any crashes, downtimes, or performance issues with Okta Platform; it has been very reliable for us.

I would think Okta Platform is easy to scale; we are a small company, but we're growing and adding new employees regularly. I haven't faced any significant scalability issues yet, but I believe Okta Platform can be scaled easily.

I have opened some tickets with Okta Platform customer support, but I often prefer to dive into documentation or reach out to relevant communities instead to find answers quickly. We do have access to their support, but I find it sometimes slower than engaging with knowledgeable people in those communities.

On a scale of 1 to 10, I would rate Okta Platform's technical support around an eight or nine. I've only opened a few tickets, and I have had a good experience receiving answers.

I didn't use any different product previously and didn't evaluate other solutions available in the market. We relied on Google for some single sign-on features but I haven't implemented Google's SAML solution in a broad way.

In my previous job, I was kind of in charge of deploying Okta Platform to the entire company. I took a three-day training from Okta Platform, which helped transition me from being a non-believer to a believer in Okta Platform. Deployment was quite a challenge, but taking that training made a difference. In my current job, they already had a contract in place with Okta Platform, but the deployment was easier because we were primarily using the single sign-on feature and adaptive MFA; it was a simpler deployment overall.

We went directly with Okta Platform and didn't go through partners or any marketplace for purchasing it.

I would think there are measurable improvements on our security and operational costs just by relying on Okta Platform. We're a small startup, and we aren't measuring these things closely, but I would think there are improvements due to our use of Okta Platform.

I don't have specific data points to share regarding ROI, as I am not much into hard data. Maybe I could get some numbers from colleagues or my manager eventually, but right now I don't have an answer for this.

Regarding my experience with the pricing aspect, I am not much into the pricing side of things, but I think Okta Platform is not an expensive company for the service they provide. We don't have Okta Workflows or Lifecycle Management due to cost, but the value we get from Okta Platform makes it a non-expensive expense for us.

I didn't use any different product previously and didn't evaluate other solutions available in the market.

I have my own wish list of things that I would like Okta Platform to have.

They have good documentation and there are subject matter experts engaging in these communities, including some Okta Platform employees. Their user interface is pretty good.

I haven't had any crashes, downtimes, or performance issues with Okta Platform; it has been very reliable for us.

Both in my current job and the previous one, we were in Fintech companies in the financial space. One of the reasons to go with Okta Platform is because they are a well-reputed company, providing some attestations such as SOC 2.

On a scale of 1 to 10, I would rate Okta Platform's technical support around an eight or nine. I've only opened a few tickets, and I have had a good experience receiving answers.

Regarding my experience with the pricing aspect, I am not much into the pricing side of things, but I think Okta Platform is not an expensive company for the service they provide. We don't have Okta Workflows or Lifecycle Management due to cost, but the value we get from Okta Platform makes it a non-expensive expense for us.

I would rate this review a 10 out of 10.

The main use cases for Okta Platform are authorization and authentication. From the SSO, I can understand if the person logging in is authorized to redirect to the correct URL. The second use case involves JWT token generation, which includes all the information about the user, such as SSO Gmail and other information about the permissions that person has. When I get that JWT from the code, I can access more user information and authenticate for other services using 3LO.

I haven't handled 2LO, which refers to service-to-service authentication. Okta Platform provides protection for non-human identities in our environment through 2LO, enabling services to call databases or APIs without human involvement, which allows M2M access. For instance, if an MCP gateway needs to access tools without human interaction, Okta Platform offers this option.

One example of how Okta Platform helps secure access to cloud infrastructure is through the AWS service called Bedrock Agent Core, where I can directly integrate with Okta Platform. AWS provides an option for this integration, allowing us to connect our API after authentication.

The best features of Okta Platform are fast authentication and smooth integration with AD groups. AD groups control the permissions people have in our enterprise through our in-house software called CIAM. This integration with Okta Platform is very smooth, the authentication is fast and reliable, and I can retrieve the JWT token, 3LO, and 2LO.

The benefit of using Okta Platform is that for authentication-related things, I don't have to consider build versus buy since this product is reliable for the majority of our applications, significantly reducing our time to develop authentication-related features.

I have seen an improvement in our cloud-based workloads since implementing Okta Platform, which provides faster connections than traditional applications. Previously, I used Redis cached and session-based systems, but through Okta Platform, I work with JWTs for a faster experience.

To improve Okta Platform, I think they should enhance the 2LO service-to-service aspect by integrating more features on the MCP side, allowing for authentication of containers running on the gateway. Instead of just client ID and secret, they could add a Vault-like storage for keys in integrated AWS services to smoothen the process.

The deployment experience with Okta Platform is generally smooth. They provide Okta Preview for non-production deployments, and I suggest they implement a green and blue rollback mechanism in production to avoid any delays for application teams during real deployments.

As a developer, I have been using Okta Platform for around four months. As an employee doing SSO and all, it has been more than a year, so it is around one year as an employee and four to five months as a developer.

Okta Platform is stable, as I haven't faced any authentication issues in the year I have been using it. It works smoothly even with hundreds of applications and hasn't encountered production issues.

The customer service and technical support for Okta Platform at the enterprise level are good, as I primarily rely on consultants who manage these interactions effectively.

Before choosing Okta Platform, I evaluated other solutions like AWS Cognito. The main advantages of Okta Platform are its JWT option, which is passwordless, and its good integration with Vault and Terraform, while Cognito lacks such features, leading to slower session-based processes.

From the start in our application, I have been using Okta Platform and still maintain some session-based systems in the cache layer.

I was not involved in the initial setup of Okta Platform. After the setup was completed, I have been using it for over a year, so I cannot comment on any challenges faced during the initial setup.

I employed consultants from other organizations to assist with the deployment of Okta Platform, which has been effective.

Financially, I cannot provide specific data points for the return on investment with Okta Platform. However, technically, managing these aspects myself would incur server costs for generating JWT tokens and reliability improvements through the OAuth mechanism provided by Okta Platform reduce my technical load.

My company purchases Okta Platform through direct Okta, not through the AWS Marketplace. It is the Okta Platform Enterprise SaaS offering.

My advice for companies considering Okta Platform is to make it more platform-agnostic. While Cognito is limited to AWS, Okta Platform's flexibility allows us to avoid being restricted to a single cloud provider. I would rate this review as a 9 out of 10.

My use case for Okta Platform is that we mostly use it for SSO for the applications we have integrated with Okta. We primarily use SSO for user authentication, and user management is not particularly involved, but we are importing users from Active Directory to Okta.

I assess the role of Universal Directory as a single source of truth for our user identities by stating that there is an application called Workday, and from Workday to SailPoint, Okta Platform will be the target system for SailPoint. When a user joins the organization, aggregation runs from HRMS to SailPoint, which is responsible for creating the birthright application, with AD being one of those. Once the user is created in AD, import jobs will run based on the mapping we did with AD and Okta Platform, and the user will be created in Okta Platform.

The best features of Okta Platform include the import feature, which allows for new employees joining the organization to have their AD account created, and when this import runs from AD to Okta Platform, this employee will be created in Okta Platform. This feature represents automation between Okta Platform and AD.

Apart from these features, I appreciate that there are password policies and authentication policies or network zones we can configure in Okta Platform. If we want to restrict the users from logging in from specific network zones or blacklisted ones, we can configure those.

The context-aware policies of adaptive MFA influence my authentication process because we can enable more MFA based on client requirements. Okta Platform is one of the MFA tools available, alongside others such as RSA, and based on the requirements, we can enable those and apply the policy accordingly.

The positive impact I have seen from using Okta Platform is that it makes it easier for new joiners to get birthright access and have users added based on department or employee type. We implement rules and policies, such as when a user joins the sales department; we can configure the group rule, and the user will automatically be tagged to that specific group. This represents an automated process with Okta Platform, rather than doing it manually.

The automated lifecycle management helps with the efficiency of onboarding and offboarding by ensuring that once a user joins the organization, they come into HRMS. From there, it goes to AD, and the target will be Okta Platform. Birthright access and applications are provisioned based on conditions. For offboarding, if an event is triggered, such as leaver or termination, values will be populated in AD, and once the import runs, Okta Platform will terminate the user, disabling access and removing whatever accesses the user had.

In Okta Platform, I do not see much room for improvement because currently, they are managing automations and the new workflow, which helps with automation. Previously, this was not available in Okta Platform, but it was introduced recently.

The automation aspect can be improved.

I have been using Okta Platform for three and a half years.

The stability of Okta Platform, I would say, is an eight because it is growing day by day. Previously, it had static features without automation, but currently, it is moving towards automation and introduced workflows.

I would consider the scalability of Okta Platform to be a six.

The scalability rating of six is due to factors that come with the tenant and the specific elements around that, which I am not entirely sure about.

My relationship with the vendor is as a customer and partner. When we have issues with Okta Platform, we reach out to their support team, and they take care of the issues we encounter.

We do not go through AWS, GCP, or Azure for Okta Platform; instead, we usually access the Okta Platform support portal to raise our concerns, and the team reaches out to us to resolve those issues, sometimes scheduling meetings as needed.

Positive

Before using Okta Platform, I did not really use any other software, but I did consider Entra ID, which is most probably similar to Okta Platform. However, Okta Platform has a user-friendly interface and is easy to use.

The integration aspects include that the capabilities come with modern protocols, making it easier for integration with various protocols and target systems.

Integration capabilities of Okta Platform enable faster deployment, as they support modern protocols such as IDP and SSO.

I have not used Okta Platform AI, but I need to check on its automated threat response features.

Regarding pricing for Okta Platform, I am not aware of how much it costs because I used to work as a consultant for them, and the licensing details are taken care of by the sales team or others.

The solution requires little maintenance, and I would say it is easier to maintain compared to other IM platforms such as SailPoint, which had huge coding and infrastructure costs.

My advice to others looking to implement Okta Platform is to definitely go for the software instead of Entra ID, as it offers a much easier and user-friendly UI.

Our company is an educational training platform operating as a global online training model. We focus on IT services and training, managing global employees and user accounts while handling the onboarding and offboarding process. We specifically use Okta Platform to manage MFA, SSO, and logins for multiple applications. It is integral to our identity and access management strategy, effectively centralizing our application management. We opted for Okta Platform because we wanted a separate, unique platform solely dedicated to identity management, unlike Microsoft Azure, where additional interconnections like Entra ID and Intune might be required.

Okta Platform offers valuable features such as centralized identity and access management, which allow for a single sign-on process, simplifying user authentication across applications. Its scalable management solutions provide strong multi-factor authentication, integrating easily with various applications using protocols like SAML, OAuth, and OpenID Connect. An intuitive admin interface makes user roles and access policies easy to manage, enhancing overall operational efficiency and security.

Security improvements are notable, with centralized identity control and reduced IT workload through automation. Okta Platform supports onboarding and offboarding employees, improving user experience with fewer logins needed.

Overall security posture with adaptive multi-factor authentication centralizes access control, especially benefiting hybrid and multi-cloud environments. Smooth deployment and scalability eliminate lag, providing seamless and stable operations in managing user accounts and identities.

Okta Platform's pricing model can be expensive for smaller organizations, affecting user feature accessibility. Initial setup and configuration require careful planning and experience from administrators. Cloud-based infrastructure may lead to access issues during downtime or service disruptions. Support response time could be improved, especially for non-premium customers.

Pricing could be more competitive compared to alternatives like Ping Identity, OneLogin, and Microsoft Azure AD. More responsive customer service, enhancements in setup configuration, and support could improve the platform. Prioritizing customer issues in support tickets based on urgency level might enhance response time, helping businesses manage crises more efficiently.

We have been using Okta Platform for almost three and a half years.

Okta Platform is absolutely stable, with no experienced lag. This ensures immediate action upon changes applied within Okta Platform, stabilizing operations in managing user accounts, identities, logins, and user profiles. With functionalities running smoothly, it fulfills stability expectations effectively.

Okta Platform's scalability is robust and performs well. It responds quickly and does not delay processes, yielding timely, appropriate results. There is no lag, allowing the platform to function smoothly. It is secure, providing needed scalability without impacting performance.

While the deployment process was smooth, helped by Okta Platform's support team, more immediate assistance post-deployment is required. Currently, the support response time is too long, adversely affecting business during urgent issues or scenarios. A suggestion is improving the customer support experience by introducing a priority system for issues, allowing urgent cases to be addressed swiftly. Adding features in support ticketing to prioritize urgency could enhance effectiveness.

By offering a system to set varying priority levels on support tickets, urgent issues could receive quicker attention, benefiting business continuity and customer satisfaction.

We considered other identity platforms available in the market and ultimately chose Okta Platform for its unique, standalone identity management capabilities.

Oakta Platform's deployment and initial setup were smooth and straightforward. We were guided effectively by Okta Platform's support team on how to configure it to fit our business needs and tenant setup.

Our team implemented the platform internally without utilizing external consultants, integrators, or resellers, except for support guidance from Okta Platform's support team.

We have a basic business standard license for Okta Platform. If we go beyond that, it is a little pricey compared to other models. Alternatives like Ping Identity, OneLogin, and Microsoft Azure AD offer minimal costs.

Comparisons were made with platforms like Microsoft Azure, which require interconnections, unlike Okta Platform's independent design. Our management team ultimately preferred Okta Platform for its unique identity management focus, taking insights from Okta Platform's demo presentations.

Okta Platform's genuine uniqueness in focusing on identity is appreciable, unlike other tools requiring interconnected services. However, the pricing, initial configuration, and support response need improvements for enhanced customer satisfaction. A customer feedback mechanism to prioritize urgent issues might ensure timelier assistance during crises, maintaining business continuity and satisfaction. I would rate this overall experience as an eight out of ten.

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.

I have been using Okta Workforce Identity for single sign-on purposes to identify and authenticate my identity and access resources at AWS. Whenever I want to connect to Amazon Web Services, I provide a particular CLI Okta command, which opens a window where I am redirected to Okta Workforce Identity's single sign-on page. I authenticate myself through mobile, and once that authentication is completed, I am able to access a particular account according to the role that I have configured in the CLI command.

The best features that Okta Workforce Identity offers are single sign-on, multi-factor authentication, and privileged access management. It has reduced the time required for authentication and provided a secured way of accessing the Amazon web console.

The user interface could be enhanced to allow direct number selection for multi-factor authentication instead of typing out information.

I have been using Okta Workforce Identity for two years.

I used Ping, but I find Okta to be more reliable with a great user interface.

Time saved is a great example of return on investment. It has saved approximately 50 to 80 percent of our time.

The pricing and licensing setup is typical, and since it follows a per-user, per-month subscription model, it is helpful.

One of my team members lost his phone and was unable to do a direct Okta Workforce Identity login. At that time, email multi-factor authentication was useful and helped him to get logged into Okta Workforce Identity and authenticate himself. I do not see any areas for improvement as Okta Workforce Identity is at its best level currently. Okta Workforce Identity is reliable, and its user experience and user interface are great. I would recommend Okta Workforce Identity to others. My overall experience using Okta Workforce Identity has been excellent. I have given this review a rating of ten out of ten.