Okta Platform

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.

Based on customer requirements for Okta Platform, I have worked on multiple engagements. Passkeys are related to inline hooks. Currently, whatever the client requires, we ensure that Okta can fit into the environment where the client is looking to implement it. The client environment and Okta should come together and complete the client's requirement. This includes MFA-related configurations, SMS-related features, third-party SMS providers, MFAs for only particular users, or network zones restrictions.

Okta Platform has peculiarities that can adopt a client environment easily compared to other single sign-on tools. It is very user-friendly and admin-friendly with everything available through a plug-and-play approach. Most other products, such as OneLogin , are tricky to understand and require more implementation work. With Okta Platform, you just need to take the plugin and use it with your current environment. Okta Platform also has more workflows automations available, which are unique features. Okta Platform is always coming up with new features such as OPAM and governance.

Okta Platform has the capability to protect non-human identities. Okta Platform has a Universal Directory that can pull accounts from different sources and store them securely. With different connectors and service accounts, you can connect to a PAM tool and ensure that passwords are rotated frequently, such as every hour or every 24 hours.

Okta Platform's reliability and availability are top-notch. Okta Platform is a SaaS-based tool with in-house disaster recovery. It does not have any downtime. If you see frequent downtimes or inaccessible tools with other products, you cannot go with those products. With Okta Platform, you have zero downtime and a proper environment to handle everything, which is why every customer is moving to it for reliability.

Okta Platform is already improving in many ways because whatever the current hot topic is, such as AI, Okta Platform is also bringing it up. I believe they are already one step ahead for every industry standard, so I do not think improvable things will do because they are already in the pipeline.

One feature I can mention is that there should be an optional registration option for multiple MFA factors. If a user has already migrated to one type of multifactor authentication and wants to register for another multifactor option, there is currently no option unless it is required. If an industry standard requires a new MFA, we want to give users the option for other multifactor authentication, but currently, this is a mandatory feature only. Some cases mean users do not want to register for new things, so whenever they want to feel comfortable, they should be able to do it. This feature is really restricting because it is mandatory. I want to have it as optional and more flexible for registering multiple MFA options.

I have used Okta Platform for about 7.5 years.

We do communicate with the technical support of Okta Platform, and they have exceptional knowledge of what they are doing. They have three types of supporting models such as gold, diamond, and premium plus. They are reachable and have a toll-free number that you can call anytime for assistance. They also have a networking team with very good support. Every type of issue has a proper team to support it, so you do not need to go to multiple teams. When you write the description, it will specify whether the issue is related to MFA and which MFA support to reach out to, or if it is related to developers and which developer support to contact. Earlier, you would go to the support team and they would segregate it and raise the case in the backend with the developers.

I rate the technical support of Okta Platform as nine out of ten. The one percent adjustment is due to time zone differences. Although you have 24/7 support for all time zones, there will be some gap from one time zone to another time zone.

The usual setup process for Okta Platform starts with onboarding applications if a company has a number of applications to enable single sign-on. Second, if a company wants a new set of policies and automations, such as revoking access within a specific timeframe, you can use connectors in workflows to create this functionality. You can create connectors that disable an account when a user is no longer accessing an application, serving as governance or a license saver.

Installation for Okta Platform is very easy and uses a plug-and-play approach that will take hardly three to four hours. However, the pre-installation steps require testing based on those requirements. If you have a large number of applications to use, you need to take more extra precautions. Installation-wise, it is simple with just a download and install of agents or configuration of workflows, which is a matter of time that could be one day or something. However, it is based on the situation at the client's side. You need to understand the client's requirements and properly relate them to Okta Platform, which will differ from client to client. I cannot tell that this is very much easy to implement because some clients have environments with dependencies.

Initial challenges for Okta Platform are based on the client environment. Customers will expect more customizations for CIAM-related things. Okta Platform has two things in CIAM : Workforce and CIAM . In Customer Identity Access Management , there are some gaps because applications may be capable but it is hard to move the piece of Okta Platform due to applications. For example, an application may need Passkeys because customers now want Passkeys as an advanced feature. If the application is using some older versions of custom widgets or sign-in widgets and you want to implement this new feature, that will take some tricky and hard challenges.

Okta Platform uses advanced AES cryptography to transfer access in depth. For APIs, it is also now using access tokens instead of regular APIs that you can just create and use. The texture in Okta Platform is completely different, and you can use a bearer token instead of an API token, which will control the permissions and attributes to use those APIs. Whenever a user wants to access some API, they first need to call and do machine-to-machine communication before proceeding with changes. Within the time the token session ends, you cannot access it next time, making it more secure than the earlier API approach. In the past, you could create an API token and copy and paste it somewhere to use, but now it is more advanced.

Okta Platform is on the cloud and not on-premises. Okta Platform has the capability to handle both internally facing and customer-facing solutions. Okta Platform now also has the OAuth feature, which is an advanced technology for handling customers. Whatever industries you look at, such as hospitalities, insurance, or marketing, many industries are using Okta Platform because it has the capability to adopt and give the solution that the client exactly needed.

Okta Platform has more adaptability. If you have any number of problems, it has the adaptability to solve them. Okta Platform has that capacity. Now with new features, you have governance, Universal Directory, PAM, MFA, and automations all in one place. If you are having older applications that do not support SAML, you have an access gateway connector. Whatever problem you have, there is a solution with Okta Platform, and it has that capability to resolve those issues. Okta Platform can fit in approximately 99% of any environment. I would rate this review an overall 9.5 out of 10.