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 previous company did purchase Okta Platform through the AWS Marketplace. When I was in Smarsh, they bought it from the AWS Marketplace and were using the Single Sign-On option with multi-factor authentication to ensure that whenever we tried to log into a system such as Bosch or Concur, the login happened via Okta Platform. Smarsh was primarily using Okta Platform via the AWS Marketplace, whereas  in my current organization is not using Okta Platform from AWS services. We have purchased it directly from the vendor.

In our case, the main use cases for Okta Platform include a Central Identity Provider where multiple SaaS tools are utilized along with many internal apps we have. We configured a Single Sign-On option for everything, eliminating the need for users to remember different logins and information. This was something we configured in Smarsh, where a single login ensured that we were able to log in via Okta Platform only instead of doing individual logins for each screen. Every SSO login used one username and password for the SSO login, followed by an authentication layer. Based on the three-factor authentication combining username, password, and authentication, we were able to perform proper sign-in. This serves primarily for our multiple SaaS tools we have in our organization, as well as certain internal apps we are using.

In our architecture, Okta Platform helps secure access to cloud infrastructure, APIs, and containerized workloads. We have not integrated GenAI in Okta Platform right now, but we have integrated it for our AWS services, which has resulted in positive outcomes. After implementing proper user authentication, we can segregate user access effectively and also trace any malicious or bad actors in the company. Previously, we relied on common credentials for specific tasks, which resulted in downtime. Because of this, we introduced Okta Platform. We were using manual sign-ins with usernames, but when SSO was introduced, it made our lives easier.

We are a FinTech company, and Okta Platform helps us address compliance and regulatory requirements effectively. There are numerous statutory regulations we have to follow, especially when dealing with finance customers such as larger banks, who have specific requirements to fulfill. Okta Platform has significantly aided us in this area as we can track each user, monitoring what they do and even obtaining their geolocation. For banking and finance purposes, it has proven to be very beneficial. Although I am not involved in healthcare or any other domain, I work solely in FinTech.

The best features of Okta Platform include Single Sign-On, which we have utilized. Beyond that, multi-factor authentication has been beneficial. User Lifecycle Management is also a key feature where everything is managed via Okta Platform itself, allowing us multiple ways to set policies and automate provisioning. We can onboard both customers and employees to our internal organization through this.

Based on my use case, I was more involved in the team that managed Okta Platform for other teams. One problem we previously faced was multiple users coming to us with different forgot password issues, as we had an administrator sign-on for the forgot password situation. Before Okta Platform, all our logins were fragmented, leading to a lot of manual toil. After implementing Okta Platform with centralized authentication and policy enforcement on top of the existing sign-in approach, our workflow has become much easier. The best part is that manual toil has almost vanished.

Since implementing Okta Platform, we have noticed measurable security and operational improvements in our cloud-based workloads. The best part is it is very easy to integrate as it has a huge app catalog which streamlines the integration process. I have never encountered issues with failed sign-ins due to external factors. As for our security posture, with MFA enabled, we have significantly reduced the common credential problems we previously faced. Because of all this, we ensure our security positioning meets all compliance standards, and whatever protocols are necessary are followed. Overall, from a security standpoint, it provides a better approach. With its extensive app catalog, integration is seamless; you just purchase it from the vendor and incorporate it into your system.

For Okta Platform to improve, I would suggest enhancing debugging for SAML, as we have faced issues using OIDC or SAML without any user-side tools to identify what is happening. This has become a significant challenge, particularly with SAML logins in the context of AWS usage. If the debugging process is made easier, it would greatly improve our experience. I also find the initial policy setup complex, as it can be a nightmare given its intricacy. Although I do not handle it personally from start to finish, I recall those complicated days vividly.

Okta Platform usage has been around four years in Smarsh and one and a half years at my current organization, totaling approximately five years.

I have not experienced any downtimes or crashes. The only issue arises during SAML errors, which are tough to debug, but overall, I have not seen any downtime. When I check Okta Platform uptime, it seems to be above two nines.

Throughout my experience, I have never noticed any downtime. Reliability is paramount, especially since I work as a Site Reliability Engineer, so both reliability and availability factors are critical. Okta Platform scales efficiently, and I have consistently observed its performance as quite fast, but my experience is only with the cloud solution.

I have not utilized customer service and technical support much. My experience shows that it should be satisfactory. We received helpful responses and resolutions for the few questions we directed to them.

Before choosing Okta Platform, we evaluated Azure where we use Microsoft Intune to register our devices. This alternative is also relatively cheaper for us since it is bundled with Microsoft services and has provided better ROI, but we still use Okta Platform for its effectiveness. We have a partnership with Microsoft in our organization, and they also sell out product in their marketplace. Okta Platform's sign-in features are especially good, offering proper pop-ups when signing in and providing easier access compared to Azure currently.

Before choosing Okta Platform, we mostly used manual logins for everything at my previous service company. When I joined Smarsh, they utilized Okta Platform logins exclusively. We even used shared credentials because we were more of a startup. As the company grew, we adopted Okta Platform based on an architecture suggestion, and this was integrated into our system smoothly without issues. In my current organization, we are using Microsoft login instead of Azure, but both solutions function similarly. However, I find Okta Platform preferable for Mac users.

My experience with the deployment of Okta Platform indicates it is very easy to integrate; however, the configuration of policies is quite complex. We had to troubleshoot SAML assertion issues during quite a bit of integration, which was painful. The token expiration and refresh process also require careful handling as we faced numerous token expiration notifications through Slack.

The initial setup process can feel overwhelming since while integrating Okta Platform is easy with the existing catalog, the complexity arises during policy configuration, which requires extensive research and adjustments. This is something that often feels problematic. Aside from that, the cloud solution integrates relatively smoothly; most challenges arise from policy settings.

We did not use an integrator, reseller, or consultant for the integration process. Our internal team performed most integrations with minimal external assistance, relying primarily on the documentation provided after purchasing the solution. The documentation is straightforward and manageable, and we only needed to contact the support team a couple of times with questions. Overall, it was not a major issue.

If I want to quantify the return on investment with Okta Platform, I have certain metrics. It has reduced our login-related support tickets significantly, providing us with better visibility and reducing manual toil, which has almost been eliminated. Previously, we conducted numerous audits, but now the admin UI provides all necessary details about what, where, and how events occurred. Employee onboarding used to be a major pain point, but the automation Okta Platform provides for creating user accounts across various apps or SaaS tools has made our life much easier. Audit processes have also become simpler, especially in finance where compliance is critical. This is something most people experience with Okta Platform; it undoubtedly has a positive impact.

Okta Platform is expensive. At scale, Okta Platform is costly. There is no question about that. However, I feel it offers quality. While it is not entirely justified, it is somewhere between 70-80% justified in terms of pricing.

Okta Platform is a good solution to discuss. When advising other companies considering Okta Platform, I recommend analyzing the cost first, as it is a critical metric. For organizations with a large user base, it is essential to explore and understand potential expenses associated with Okta Platform. The pricing can be quite high for large-scale usage, so expenses should be considered carefully before committing to Okta Platform. Services are generally good, and no product is flawless, so there will be notable strengths and weaknesses to consider, such as token and SAML troubleshooting issues. With our company's tuned MFA, we have alleviated many issues, but without it, problems can arise for several employees. Okta Platform is not deployed on-premise; everything is on the cloud. I would rate this review as an 8 out of 10.