Identity platform has unified access, automated lifecycle tasks, and strengthened cloud security
What is our primary use case?
I have been using Okta Platform for almost four years. In my current organization, I use Okta Platform as a cloud-based IAM platform for purposes like Single Sign-On, multi-factor authentication, lifecycle management, as well as for universal directories. It provides secure, automated user provisioning and access to applications for employers and customers, and it is also useful for risk authentication and API access management. Okta Platform is an AI-driven technology that detects threat-related models, signaling if anything potentially harmful might occur. Thus, there are various uses for Okta Platform.
Okta Platform protects non-human identities in my environment, including service accounts, machine-to-machine access, and AI agents. Regarding non-human identity protection, the ServiceNow team creates a non-human identity that flows into Okta Platform and generates a generic password for them. It helps manage our service accounts and includes customization features that enable these non-human identities to automatically activate their passwords every 60 days and restrict logins to approved systems only, not from personal or any other devices.
Okta Platform helps to address specific industry and regulatory requirements in my cloud environment, including usage within the banking sector, finance sector, and one of the large logistics sectors. We also have a client in the pharmacy sector where we use Okta Platform as a complete end-to-end product.
For Okta Platform deployment model, I am using AWS. I have integrated and secured AWS services through Okta Platform by utilizing Single Sign-On for application integration and using Terraform for project deployments.
What is most valuable?
The best features of Okta Platform include Single Sign-On, which offers one-click access for thousands of cloud and on-premise applications, and great lifecycle management. It automates user provisioning and de-provisioning, managing the entire identity lifecycle from onboarding to offboarding. Additionally, it provides excellent scalability along with device and administrative tools management, making Single Sign-On and lifecycle management the standout features.
Using Okta Platform, we can utilize almost 7,000 pre-built integrations with popular applications. It provides easy and customizable configuration based on client requirements, allowing for development of user onboarding, offboarding, and updating processes. There are numerous API features, including passwordless authentication and B2B customer identity with a CIAM feature. Okta Platform secures APIs to control access and protect sensitive data, enabling users to reset passwords or unlock accounts without IT intervention. Moreover, it offers standard and custom reports to monitor access, ensuring compliance and visibility into potential security risks.
Okta Platform helps to secure access to cloud infrastructure, APIs, containerized workloads, or AI/GenAI services in my architecture by utilizing two modules: Identity Threat Protection (ITP) and identity governance and automation. ITP analyzes login patterns, device posture, and network data to detect anomalous activity, and it enables universal logout for instant revocation of access tokens across all supported applications if suspicious behavior is detected. The shared signals framework, along with Log Investigator and natural language processing, allows admins to query system logs in plain English for quicker investigations. In terms of identity governance and automation, it analyzes user roles and activity to recommend the least privileged access, optimizing governance policies and generating summaries of user access rights for access certification reviews.
What needs improvement?
While I see very few areas for improvement in Okta Platform, I do note its high cost, which can be particularly challenging for smaller organizations looking to utilize advanced features like Okta Workflows. Additionally, there are reporting limitations, as some users find Okta Platform's built-in reports less detailed compared to competitors. Furthermore, frequent multi-factor authentication prompts can cause MFA fatigue, disrupting user experience. Lastly, there is limited on-premise support, which, while robust in the cloud, is often expensive to manage for legacy on-premise applications, making these features candidates for enhancement.
For how long have I used the solution?
I have been using Okta Platform for almost four years.
What do I think about the stability of the solution?
In terms of stability, I faced some issues in 2022, but for the last three years, there have been no scalability problems. Okta Platform efficiently supports scalability, allowing for extensive individual tenants within a single environment, as well as onboarding and offboarding processes for thousands of applications. Clients can scale their API access requests beyond default limits, which is adaptable according to requirements without impacting performance or deployment.
What do I think about the scalability of the solution?
In terms of stability, I faced some issues in 2022, but for the last three years, there have been no scalability problems. Okta Platform efficiently supports scalability, allowing for extensive individual tenants within a single environment, as well as onboarding and offboarding processes for thousands of applications. Clients can scale their API access requests beyond default limits, which is adaptable according to requirements without impacting performance or deployment.
How are customer service and support?
I would rate Okta Platform's tech support and customer service as an eight out of ten, as their availability can be rare and requires scheduled calls, often taking a significant time to receive solutions. However, the support provided is generally very good.
Which solution did I use previously and why did I switch?
Before adopting Okta Platform, I had used OneLogin and Entra ID for identity and access management, specifically for privileged access.
How was the initial setup?
The deployment experience with Okta Platform varies based on client requirements. For large-scale applications, it took almost two to three months, while small-scale organizations required around six to seven days. I have not faced issues during deployment; it has consistently met our clients' expectations.
What about the implementation team?
For deployment, our AWS DevOps team works on the deployment-related aspects and supports the workloads secured by Okta Platform.
What was our ROI?
Since implementing Okta Platform, I have noticed measurable security and operational improvements in our cloud-based workloads. Initially, we faced complex implementation challenges, but now it supports much faster and easier implementation and deployment in production, thanks to AI utilization. We resolved earlier centralized risks, and credentials are now managed in a very encrypted manner, which has improved performance and security.
What's my experience with pricing, setup cost, and licensing?
I find Okta Platform cost-effective and worthwhile to purchase due to its vendor-neutral nature, supporting thousands of pre-built integrations with third-party applications. It is highly flexible with adaptive MFA, includes user behavior analytics and custom workflows, which many competitors do not offer. Its granular and easily configurable policy engine, along with a strong lifecycle management process, makes it worthy of investment for any organization despite its cost.
Which other solutions did I evaluate?
I evaluated OneLogin and Entra ID before choosing Okta Platform.
What other advice do I have?
My advice for organizations considering Okta Platform is that if cost is not a concern, they should definitely opt for it, as it features excellent user lifecycle management, identity governance, re-certification, user provisioning, and strong Single Sign-On functionalities. I would rate this review as a nine out of ten.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)
Unified access has simplified JML automation but data residency still needs improvement
What is our primary use case?
We started Okta Platform as an SSO solution. We are using it for workflows configuring like JML and all the automation. Okta Platform is being used for the JML purpose like joiner, mover, leaver purposes and all the automations.
We are using ServiceNow, so Okta Platform is integrated with them using the APIs. We have custom applications that we are integrating with using the APIs, and it is supporting very well.
In our environment, we have not enabled Okta Platform for service accounts, and we have bypassed Okta Platform authentication for those things. I am not certain if Okta Platform can support those accounts, but in our environment, we have bypassed those items.
What is most valuable?
The first thing I appreciate about Okta Platform is the security, and then the JML automation process. It is truly amazing and makes life easier for us.
We have multiple applications before using multiple authentication methods, using multiple kinds of Intranet ID and many other things. Now, we have moved to one platform which is Okta Platform. We have a single source of Okta Platform, and not only that. Before we had many processes using ServiceNow for the management services. We have integrated Okta Platform with that to make the process more automated. This makes life easier, making things faster and more secure, with one point of one resource of authentication. It is very user-friendly.
Okta Platform supports integration with the APIs as well for applications which do not have SAML and Zero Auth. Okta Platform can integrate with the APIs.
What needs improvement?
It has been two years for me with Okta Platform, so I still cannot judge if they need improvement in specific parts. So far, it is covering what my requirements are. Perhaps in the future, if I encounter limitations, I can provide feedback. For now, I have no concerns about this.
I can say one more thing. I am in Saudi Arabia, and Okta Platform is hosted somewhere in Germany on the AWS platform. Every country has their own compliance requirements. Saudi Arabia requires any application, every software, everything to be hosted inside the kingdom. This is our country's compliance requirement. Okta Platform is not hosted in the Saudi region. In fact, it is not even in the Middle East; it is somewhere in Germany. If it were moved to every country with their own data center, it would cover all of our compliance related issues, and every country could align with that. Saudi Arabia especially needs every application, every software, every tool to be inside the kingdom, where Okta Platform is somewhere outside. If they move to the Saudi region or somewhere in the Middle East, it would be really helpful for us.
For how long have I used the solution?
What do I think about the stability of the solution?
Since Okta Platform is a SaaS service, we do not have to do anything. We just need a mid-server and that is all. That works for us. We do not have any main challenges with Okta Platform.
What do I think about the scalability of the solution?
I am still in the phase of rolling out Okta Platform completely. I have not done the complete rollout. I cannot assess this now because we are in one of the biggest companies, so we have many things, more than 300 applications, and a lot of other items. We are still in the phase of rolling out Okta Platform everywhere.
How are customer service and support?
I have dealt with some issues and have raised tickets, and they were really helpful. They replied immediately with no delay. Since I am also using professional services, the responses are quicker because of that. They are very good.
For tech support, I can rate them an eight. The only thing I found is that they are working somewhere in the UK, and I am working in a different time zone, so there is a time difference. If I raise a ticket, I will get a reply the next day. That is the only issue because of the time difference. Otherwise, it is an eight.
Which solution did I use previously and why did I switch?
Before, we were using Microsoft and some other kinds of authentication methods. Okta Platform has replaced those things. Almost, I feel both are the same. I did not feel much difference in the security aspect. It is the same for all.
We were on Microsoft and some other third-party authentication, though I do not remember the exact name. Then we moved to Okta Platform. It was not much, but we moved from Microsoft and some other small things to Okta Platform.
How was the initial setup?
Since Okta Platform is a SaaS service, we do not have to do anything. We just need a mid-server and that is all. That works for us. We do not have any main challenges with the initial setup of Okta Platform. We need to properly design the deployment according to our organization's needs, rolling out things accordingly. But otherwise, the deployment of Okta Platform in our environment and the initial setup is straightforward because it is a SaaS service.
What about the implementation team?
We did not buy Okta Platform directly because, in the Saudi region, Okta Platform is not there. They do not have any head office here or any base here. We went through another third-party company. Through them, we are buying Okta Platform.
We do have Okta Platform team with us for managed services and professional services from Okta Platform's side, along with our team. They are handling these things for us from Okta Platform itself.
What was our ROI?
We have calculated the number of seats and users. We have around 4,000 user licenses.
What's my experience with pricing, setup cost, and licensing?
Okta Platform is a bit expensive compared to other solutions. Okta Platform is a bit expensive, and in fact, I am using the managed services from Okta Platform. They too are a bit expensive for us, but we are using them because we are happy to go with this solution. Otherwise, compared to others, they are expensive.
Which other solutions did I evaluate?
We did not buy Okta Platform directly because, in the Saudi region, Okta Platform is not there. They do not have any head office here or any base here. We went through another third-party company. Through them, we are buying Okta Platform.
What other advice do I have?
It is more user-friendly than Microsoft, and Microsoft only has authentication factors. Okta Platform has other kinds of services, such as JML processes and other workflows that we can design. Microsoft does not support those things. Even though Auth0 and other solutions are more flexible, Okta Platform offers more capabilities, so we have moved with Okta Platform.
I can say it is more secure, more user-friendly, and integration with applications is easier. It does not require expert professionals to manage it. Anybody can manage it fairly easily. If you are dedicated to working on Okta Platform, then it is very easy to manage. Integration with applications is very straightforward, and there are a lot of user guides available, which help us work with Okta Platform.
My overall rating for this solution is seven.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Centralized identity has streamlined secure access and authentication but onboarding UI still needs work
What is our primary use case?
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.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
I have been working with Okta Platform since September of last year.
What do I think about the stability of the solution?
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.
What do I think about the scalability of the solution?
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.
How are customer service and support?
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.
How would you rate customer service and support?
Which solution did I use previously and why did I switch?
I have not used any other solution of the same kind prior to working with Okta Platform.
How was the initial setup?
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.
What about the implementation team?
Someone helped me with the integration during the deployment of Okta Platform. I did not do it myself.
What was our ROI?
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.
Which other solutions did I evaluate?
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.
What other advice do I have?
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.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)
Single secure login has simplified daily access and strengthened multi-factor protection
What is our primary use case?
Okta Platform is a cloud-based identity and access management solution, so I mostly use it to provide secure and centralized access to my applications by managing user identities and authentication processes.
I generally use Okta Platform to manage secure access to enterprise applications including cloud and cloud GSP, and to gain access to cloud services or internal systems. I mostly use some features including Single Sign-On (SSO) and multi-factor authentication (MFA). I use them for lifecycle management and integration of various cloud applications.
I generally use Okta Platform because it simplifies my identity management and improves security. I believe it saves us time in terms of development and other areas. When I try to log in and do my work, before using Okta Platform, it used to take considerable time, starting with trying to log in once and then logging in to every application that is in my VDI. It generally tends to take a lot of time, and our thinking capability also differs slightly when we are trying to log in through different applications and attempt to do our fundamental logic work.
What is most valuable?
Okta Platform offers several valuable features. The first one is Single Sign-On, which allows users to log in once and gain access to multiple applications without needing to enter credentials repeatedly. I believe that is one of the best features. The second one is multi-factor authentication (MFA). It adds an extra layer of security by requiring users to verify their identity through multiple methods such as a password and a mobile verification code. I use it mostly to manage secure access to enterprise applications and cloud services. Other features include user lifecycle management and integration with cloud applications.
I myself have relied mostly on multi-factor authentication (MFA) because I tend to log in every day and whenever I am working or take a break, I use this multi-factor authentication to sign in.
Okta Platform simplifies identity management, improves security, and allows employees to access multiple applications through a single secure login. I believe this is a very good feature.
Okta Platform has improved our organization through user authentication with features like Single Sign-On and multi-factor authentication. I believe the features it provides simplify identity management, improve security, and fulfill the need for secure and centralized identity and access management.
What needs improvement?
Okta Platform could improve its administrative interface and make some configuration processes simpler for many users. Okta Platform tends to become more complex with more complex functions. The complexity increases with the complexity of the functions that we receive. It could use better documentation and onboarding experience for new users. Some advanced configurations require deeper technical knowledge. Clearer guides would help organizations implement features faster. While Okta Platform is a strong identity management platform, improvements could be made by simplifying integrations and providing more intuitive configuration options for administrators.
For how long have I used the solution?
I have been using Okta Platform since the beginning of my corporate career, for around one year and two months.
What do I think about the stability of the solution?
Okta Platform is very stable in terms of stability. For enterprise-related identity and access management, Microsoft Entra ID and Ping Identity offer strong SSO, MFA, and governance features, ideal for complex organizations. JumpCloud and OneLogin would suit SMBs with software SSO and device management needs.
What do I think about the scalability of the solution?
Okta Platform is highly scalable because it is at an enterprise level. Microsoft Entra ID, which is Azure AD, grows easily with large organizations and strong cloud infrastructure. Ping Identity is designed for large enterprises and complex environments. SailPoint is an excellent solution for scaling identity and governance. It is very flexible and developer-friendly. Auth0 scales well with applications and customer identity use cases. Keycloak is another option if you want to self-host and manage infrastructure.
How are customer service and support?
Okta Platform has incredible customer support. I have never faced an issue with it to begin with. If we were to face an issue, I think it would be handled really well.
Which solution did I use previously and why did I switch?
I have not used any other different solution before Okta Platform because this is the first company that I have worked for.
Initially, my project used ZITADEL, which is an open-source IAM cloud-native alternative. It emphasizes open standards and passwordless login. It works with SSO, MFA, OIDC, and OAuth support, and integrated dev tooling. It was a developer-friendly tool, but we ended up choosing Okta Platform right before I onboarded to this project.
How was the initial setup?
Okta Platform protects non-human identities such as secure accounts, APIs, and automated applications. It provides secure authentication mechanisms and access policies to ensure that only authorized systems can interact with enterprise resources.
What about the implementation team?
GenAI services can be used with Okta Platform to enhance security monitoring and automate identity management tasks. It can help analyze login patterns, detect anomalies, and assist administrators in responding to potential security threats more quickly.
What was our ROI?
The return on investment comes from reduced time spent on password-related support requests. With Single Sign-On and automated identity management, employees can access applications faster while IT teams spend less time handling authentication issues. I think it is a very good return on investment.
What's my experience with pricing, setup cost, and licensing?
Okta Platform is on the costlier side because it is considered competitive for enterprise identity management solutions. Although it may seem slightly expensive at first, the security features, reliability, and ease of integration provide good value for the investment.
The licensing cost mostly depends on the number of users and the features required. While licensing cost may be higher compared to alternatives, the security capabilities and reliability make it a worthwhile investment. Currently, we have not faced any issue and it was fairly smooth.
Which other solutions did I evaluate?
For enterprise-related identity and access management, Microsoft Entra ID and Ping Identity offer strong SSO, MFA, and governance features, ideal for complex organizations. JumpCloud and OneLogin would suit SMBs with software SSO and device management needs.
Microsoft Entra ID, which is Azure AD, grows easily with large organizations and strong cloud infrastructure. Ping Identity is designed for large enterprises and complex environments. SailPoint is an excellent solution for scaling identity and governance. It is very flexible and developer-friendly. Auth0 scales well with applications and customer identity use cases. Keycloak is another option if you want to self-host and manage infrastructure.
What other advice do I have?
I would highly recommend Okta Platform because it gives you access to Single Sign-On (SSO) and multi-factor authentication. These two features cover most of the market value. Nobody else has both of these features. If we were to look for alternatives other than this, I would not recommend them because even though it is on a costly side, it would eventually balance out with the features that they provide. I would recommend it because as a developer, you would not want to remember multiple passwords, go to different applications, and try to enter your password. Those kinds of things could be avoided, so I would highly recommend this product.
If I were to consider security improvement, after implementing Okta Platform, we observed improved security through multi-factor authentication and centralized identity. This significantly reduced unauthorized access attempts and lowered the number of password-related security incidents.
I give this product a rating of ten out of ten.
Which deployment model are you using for this solution?
Public Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)