Okta Platform Reviews

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.

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.

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.

Negative

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.

Okta Platform has primarily acted as an identity provider across my organizations. The key component is that even though people have HR systems nowadays, they do not have all the sorts of automations which we require on a daily basis for what we need for the users. For example, in my previous organization, there was no lifecycle automation management. In that order, we used Okta Platform Workflows in automating the CRUD operations, such as creating user accounts, updating whenever a user gets promoted or demoted, and deletion once the user has been leaving from the company. These were the major use cases where we handled identities across the organization and provided access through the SSO or OIDC access through Okta Platform Workflow portal.

We have approached many clients. They were using some native Oracle-based IAM systems, which was too hard for them to maintain and manage for the users. When the client approached my organization, the major request for them was that it should be highly reliable and have a promising uptime value.

It also was for a project requirement. Basically, my organization is heavily relying on Microsoft, but we exactly took Okta Platform for a client requirement. We got a US-based client, and it was a very big project for us, and their all native system was running on Okta Platform. In order to have that sort of running, and they did not have a test tenant. That was where we moved forward and thought to bring up the tenant in Okta Platform and try our sandbox environment, spinning up all the resources and checking how exactly it goes. That was the point where we adapted to Okta Platform and understood the scope and how exactly it has been working.

One thing which makes Okta Platform different from everything is the feasibility of the integration it provides. It almost has all sorts of integrations required for SSO. Okta Platform does not give any cloud platform an upper hand or bias. It has all sorts of integration available. Plus, it is user-friendly and the UI is very promising for the people who work on automations, especially in the workflows. It works in a card-based system, essentially low-code, no-code.

Okta Platform allows troubleshooting of any sort of blocker from the platform and implementing the requirement. The documentation on Okta Platform is extensive and less confusing compared to other identity providers.

Okta Platform is highly reliable and does not have any sort of downtime. Okta Platform also offers customer-managed support for each account. Okta Platform has regular client meetups to educate us on new launches or features such as FIDO.

Okta Platform has a wide variety of API requirements. For example, not all native SSO applications have SCIM requirements, but Okta APIs can help automate even where SCIM is not present. Okta Platform also integrates with AI practices for automation.

Okta Platform provides scalability options with minimal latency. Okta Platform is very scalable, allowing user addition without immediate payment during the current cycle. These scalability attributes cater to larger organizations as well as small businesses.

Okta Platform Application Network is very helpful for identifying integration possibilities. All details that a developer needs would be available in one place.

Okta Platform facilitates SSO capabilities without cloud platform bias and has a user-friendly, card-based automation system. Okta offers focused and efficient customer support, which is highly appreciated.

Whenever we have any sort of technical issues or configuration issues, they have a solution. Customer support is very responsive and effective.

The one thing which can be improved in Okta Platform would be the certifications which they provide. It is crucial for people to get recognized in the industry. Also, some of their documents have outdated images or screenshots, leading to confusion. Keeping the knowledge base updated quarterly is advisable.

In my environment, I have not specifically used some concepts like device management and Okta Platform's OAuth in the CISM platform. I would like to have further implementation progress on them.

I have been working with Okta Platform for almost three plus years.

There were not any downtimes whenever I worked with Okta Platform, but there was a scenario where applications were not visible inside the dashboard. It was fixed within 45 minutes to an hour. Users did have access to the applications in the directories, but they were not visible at the endpoint during this time.

Scalability in Okta Platform is notable for its minimal latency. For my organization, which had only been licensed for Okta Platform up to 50 identities, scaling up was not an issue even when our HR team onboarded more people. This feature makes Okta Platform applicable for larger organizations or small startups.

Whenever there is a need to add users, it is possible, and during the next cycle of payment, we only need to pay them up. This is an immense advantage over platforms such as Google Workspace, which require licenses at most instances.

All the people, especially those who work in Okta Platform, are highly educated. The customer support team has resolutions for the issues or does not make us wait too long. They efficiently access their vast knowledge base and return quickly with solutions. For Okta Platform, the customer service is seamless, and I am very satisfied with their assistance compared to other channels such as Microsoft's, which usually takes longer to resolve issues.

Whenever we create a ticket, Okta Platform usually sorts everything via Zoom calls. Positive experiences every time have led to my satisfaction with their customer support services.

Active Directory is always comfortable in working with Entra because it is a Microsoft product. When starting a company new to technology, Okta Platform is beneficial. Microsoft is a go-to for organizations with legacy identities utilizing Microsoft tools. For Jamf-reliant and MacBook major users, Okta Platform is optimal.

We also use Okta Platform under a client requirement. Since all native systems were on Okta, a test tenant was not available, and hence, understanding the benefits of working on Okta was necessary.

I am not able to recall the price structure of Okta Platform. It all would be looking into the financial end, so I am not very familiar with it. I do not know the current rate of purchasing, but it is always based on per seat. Okta has a straightforward purchase system compared to Microsoft's separate licenses for cloud.

If a particular organization is too old or with a legacy system, they would continue favoring Microsoft due to familiarity. Okta Platform serves new startups or ventures seeking technological change well. Engage with CSM providers to have an Okta Platform walkthrough.

When only needing application management, Okta Platform suffices, but if requiring identity, device, and email automation handling, assess needs before adoption.

I would rate Okta Platform as an eight.

I did not work on any health industry projects, but I worked with a food industry known as Flashfood. It is one of the global chains in the US and Canada. They opted for Okta Platform.

The one thing is I am a big fan of where people keep things very minimal in the UI. When I go for other solutions, apart from Google, I keep the Google Workspace identity aside because Google is also one of my favorites whenever I am working with identities.

For all the non-service accounts, the realms inside Okta Platform allow for stringent policy implementation, such as IP or geographical restrictions, ensuring uncompromised service accounts. My overall rating for this review is eight out of ten.

I use Okta Platform majorly for SAML. I use it for users and groups. I also use it as my IDP. I use it for identity and access management. From SAML to SSO, I use it for all of those cases. I use OpenID Connect and OAuth for all of those cases.

One of the best benefits of Okta Platform is the workflow. The project I worked on at that time introduced me to a workflow like this. It is simple and easy to use. I also appreciate the way it is integrated with app integration for almost every major app. This makes it easier for me to work with it. I also appreciate the way I can create rules for groups.

We use Okta Platform for API, especially for API permissions. We use it extensively for API permissions. On Okta Platform, you can create API scopes. Because we also have our own in-built app, we use Okta Platform to give access to specific permissions for specific users.

We use Okta Platform particularly with a transportation company. Since we are a tech company that provides tech services, we use it majorly for tech services. If we need to work with other sectors, Okta Platform is our go-to solution.

I use Okta Platform for both cloud and on-premises environments because we have on-premises infrastructure. I install Okta agent in the on-premises and then I can easily synchronize the users into Okta Platform. I use it for both on-premises and cloud.

The cloud provider I use for Okta Platform extensively is AWS because we have users in AWS that we need to synchronize with Okta Platform. I create the users in Okta Platform and then they already have access in their AWS Identity Center. Entra gave me quite some trouble, so we moved to AWS since we are also using AWS.

The main benefits that Okta Platform brings are significant. The app integration is amazing because I can easily integrate with almost every app that the organization or enterprise uses. The way I can create users with SAML allows me to create users on Okta Platform and then use it to log in on other apps. I see Okta Platform as my security guard when it comes to identity for other apps. I do not prefer to create users and groups on other apps. I prefer to do that in Okta Platform. There is a particular feature I have read about but have not worked with, which is the Okta agent for non-human identities. When I read about it, I thought it was a nice feature.

There have been major improvements. One of the features I appreciate using is Just-in-Time access. You must have approval for why you want to do what you want to do. This is very important. Okta Platform has improved our security significantly. It has reduced how people or users in the organization can just have access to different resources. You need the right person to have the right access to the right resource. Using Okta Platform to implement this has been beneficial for us.

Okta Platform's user interface and user experience need improvement. Sometimes I need to go through the process again. It needs to be more user-friendly. You must know Okta Platform very well. I still go back and read the documentation again and again. Another significant issue is that there are not many resources available for people to go through.

A major factor for me is that in Africa, we are not really Okta-based. There needs to be more publicity on this, especially in Nigeria, because there are many users here. There is not much publicity. When we are talking to a company and say we want to help them manage their identity, and we say Okta Platform, they will ask if we mean something else. Most people know Microsoft Entra, AWS, and AWS IAM. Most organizations do not really know Okta Platform here. I tried to schedule a meeting with Okta staff, but the meeting did not go through. I tried to book it on the calendar so many times but it did not work because I was in a different region. We can go to 10 companies and probably just one would have heard of Okta Platform before, and they have not even used it.

If possible, I would suggest implementing PIM, which is Privileged Identity Management. This is a major factor where Entra is strong. Privileged Identity Management is an amazing aspect. If I want to do PIM and PAM, I need to add Entra and CyberArk to work together with Okta Platform. This requires too many integrations. If Okta Platform could have all of these features together, it would be much easier for me and would be amazing to have within Okta Platform.

The pricing aspect is also a concern. I wanted to have a meeting with Okta staff to discuss licensing again for Okta Platform, but it did not go through because it was not forthcoming. If the pricing process could be improved, that would help. I cannot easily see the full pricing on the site or make a seamless call with staff. Sometimes I have to create routes and use a different email like a work email to create an account again. This is quite complicated. The pricing process should be as seamless as possible. We appreciate your services and want to use them.

Regarding pros on Okta Platform, the app integration is seamless and very good. The cons compared to Entra and AWS are that Privileged Identity Management is not available. Most people want to do PIM on Entra. For AWS, policies are much better. I use AWS more for policies than Okta Platform. I did not know Okta Platform even had policies, but they are not as diverse or as flexible as AWS. When it comes to PAM with CyberArk where you can rotate keys, I have not really used that on Okta Platform.

I have been using Okta Platform for close to four years now, about four years.

Okta Platform is stable.

Okta Platform is scalable. I find it scalable.

We use S3 and Identity Center with Okta Platform. We use Identity Center because we have some apps on it. The users that we create on Okta Platform are the users that can have access into those apps in Identity Center. S3 is what we use. Lambda is not used as much, but S3 is used.

Regarding service support and customer support, it would be preferable if it were easier to get in contact with them. I have only spoken to one Okta Platform representative, and the last person I was supposed to talk to did not follow through. Sometimes I wonder if it is because we are from Nigeria. Nevertheless, it should be easier to contact them, whether through email or an AI agent that we can talk to so we can know basically what is needed. There should be ways we can easily contact them. I am certain that all the information gathered will be given to the right persons and they should work on it.

What I did was an integration with AWS. I created the metadata and I told Okta Platform to provide me the metadata. I input it in AWS so that Okta Platform is the IDP of AWS. This is how we work with AWS and Okta Platform.

Based on my work with Okta Platform, the advice I would give to other organizations is that Okta Platform is excellent when it comes to app integration. If you want to do app integrations, you cannot go wrong with Okta Platform. The way they create users, the way they create groups, the type of rules you can add to groups, the permissions, and Just-in-Time access are all excellent. When it comes to identity and access management, Okta Platform is in my top two solutions. It is one of my go-to choices. If you want to do anything with identity and access management, Okta Platform is your go-to solution.

I give Okta Platform an overall rating of eight out of ten.

My main use case for Okta Platform is single sign-on for other applications, and sometimes I also use it for devices with MDMs, and also for workflow, especially for onboarding and offboarding different users.

I use Okta Platform for single sign-on across multiple applications where I integrate multiple applications for single sign-on, and I also integrate an HRM solution for onboarding and offboarding purposes.

Single sign-on is one of the best features Okta Platform offers. Workflows are also good, and device trust is another top feature.

Okta Platform has positively impacted my organization by improving our processes significantly. It eliminates the need for different passwords for various applications compared to single sign-on, which reduces the headache of IT work when offboarding and onboarding users across multiple groups and applications. It is always helpful, and it reduces a lot of work for us.

Implementing Okta has reduced a lot of IT work. I would say it saves hours and hours of work when it comes to single sign-on and the same for user onboarding, offboarding, and group settings.

I would say Okta Platform needs to improve on pricing because now Entra ID is providing this kind of capability built-in with P1. People are moving towards those solutions because it is more integrated, provides single sign-on as well, and can do device trust and certificates. If Okta Platform needs to stay in the market, they should consider bringing down their pricing to maintain or regain business, as there is no comparison now with Entra ID.

I think pricing, setup cost, and licensing for Okta Platform are on the higher side. They need to reduce the pricing if they wish to survive and remain competitive.

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

Okta Platform is stable, scalable, and reliable.

The customer support for Okta Platform is good.

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

I have seen a return on investment with Okta Platform. Implementing this solution saves time and money. By saving engineering time, I am effectively saving money as well, so it saves a lot of hours of manual work.

I did evaluate other options before choosing Okta Platform.

I think the rest of Okta Platform is good. I would say it is more good than Entra, so it is good overall.

I think Okta Platform uses AI for governance and is still working on it. They will reach out in due course. However, as far as single sign-on and such functionalities go, AI is not needed there. If your workflow is good, then everything should be fine.

I find its accuracy and reliability of output to be around eighty to ninety percent.

Okta Platform helps secure access to cloud infrastructure, APIs, containerized workloads, and AI GenAI services in my architecture through API-based and token-based integration with single sign-on for these applications. It is always helpful.

Okta Platform does not protect non-human identities in my environment, such as service accounts or machine-to-machine access, because I use RDP. It provides capabilities there, but not for service accounts or similar.

Okta Platform helps address specific industry or regulatory requirements in healthcare, financial services, or the public sector, and I would say everything is nominal.

I have noticed measurable security and operational improvements in my cloud-based workloads since implementing Okta Platform. It provides secure single sign-on and everything.

Okta Platform is a good platform and has everything needed with more capabilities. The only concern is pricing, so I recommend comparing it with other platforms because you might already have this capability in Entra. I would rate this product nine out of ten.

Use cases include onboarding SAML applications, onboarding OIDC applications, onboarding third-party vendors for accessing these applications, enabling single sign-on across internal and external applications, enabling multi-factor authentication, and enabling adaptive authentication that triggers based on risk score.

Okta Platform is among the market leaders in this space. They have numerous integrations available out of the box, and some of the functionality beyond access management is also there, such as IGA capabilities and PAM capabilities. Overall, I have had a good experience.

Okta Platform has been in the industry for a while, so they have become quite mature in terms of product. The product is robust and does not have many bugs in it. They offer a range of out-of-the-box connectors, so you can quickly onboard target applications without custom integration. The ease of integration with multiple other applications is a key point I would highlight.

The main benefit is single sign-on. All access management solutions, including Okta Platform, provide single sign-on capability and multi-factor authentication capability. These are the two core functions any organization should implement. Beyond that, they also offer advanced capabilities such as passwordless authentication, so you can integrate your FIDO2 equivalent devices and enable passwordless authentication to your applications. These features are basically why they are quite famous in the market.

Okta Platform secures access to cloud infrastructure, APIs, containerized workloads, and AI and GenAI services in a similar way to how they do SAML and OIDC. Recently, they have rolled out some capabilities in the GenAI or Agentic AI area, where they can secure AI agents and manage the provisioning and deprovisioning of their identity and access parts. Regarding web APIs and everything, they have solutions to secure API accounts, ensuring access is provided only to required users based on access control.

Okta Platform does have PAM capabilities, and there they onboard non-human identities and manage and govern them. They definitely have some of the latest capabilities, such as OpenID and OIDC connections that you can utilize for your cloud workload and manage access to your cloud provider. They also have some fine-grained access available, enabling segregation of duties. These improvements bring operational efficiencies as well.

Okta Platform is quite mature, but I would like to see more integration. While they have a vast range of integrations out of the box available, if their PAM and IGA capabilities were more mature, then Okta Platform could be the single solution for everything, covering access management, privilege access management, and governance of identity. This would mean one would not need to take multiple products for specific identity needs in each area.

I have been using Okta Platform for seven to eight years now.

I find Okta Platform to be stable.

I believe Okta Platform is scalable. You can deploy it for 10,000 identities to 5 million identities. They have good elasticity and resiliency, so I find it quite scalable.

Both the tech support team and customer service team are good.

I have used OneLogin in my past with one of my employers, and we were using OneLogin for single sign-on, MFA, and passwordless journey.

The pros are that both Ping and Okta Platform have been in the market for a while, and they were among the first to provide single sign-on and MFA capabilities. They have become quite mature with multiple capabilities available, which is advantageous. They are enterprise-grade solutions and mature enough for any kind of organization to deploy. On the other hand, with OneLogin, there were some bugs I encountered, and I always needed to work with the product and R&D teams to get them fixed, so the product was not as mature or stable then. The pricing point for OneLogin is appealing, which draws customers in, but in terms of capabilities and features, both Ping and Okta Platform have a slight advantage.

Okta Platform is much easier to deploy.

I am using the SaaS deployment model.

Okta Platform has delivered ROI in two ways. First, it improves the security authentication and authorization processes across the organization, securing applications with single sign-on and MFA. Second, it helps cover compliance requirements, whether following SOCS compliance or any similar compliance. It assists in reducing user friction and the manual work of managing multiple applications independently while improving security.

I would not say Okta Platform is a cost-effective solution. It is an enterprise-grade solution, so it is comparatively on the higher side in terms of cost. It is not as cheap as you may find with other single sign-on products.

The main key feature Okta Platform is currently working on and has launched recently is Agentic AI for securing those Agentic AI identities. That is the one I would highlight as compelling at this moment, given that everyone is talking about Agentic AI.

My advice is to understand your requirements and decide your product based on that. Okta Platform could be good for enterprise customers because it serves multiple use cases and offers various capabilities, similar to Ping. If your requirement is very specific, then conduct an assessment and POC, identify your real use cases and future growth areas, and then make the investment to achieve real ROI.

Most likely, Agentic AI and healthcare are the two key industries. I would say everyone else as well, whether retail, pharmaceutical, or manufacturing. Everyone who wants to utilize single sign-on or multi-factor authentication tends to use either Okta Platform, Ping, or OneLogin, depending on the situation. I have not seen OneLogin in many customer environments. I would rate this solution an eight out of ten.

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.

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.

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.

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.