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)
Easy, Secure SSO and Authentication Management with Okta
What do you like best about the product?
What I like most about Okta is how easy it makes managing authentication and SSO across multiple applications. It provides a reliable and secure way for teams to access different tools without juggling multiple logins. The integrations with many popular SaaS applications are straightforward to set up, and the admin console makes user and access management fairly simple. It also helps improve security with features like MFA while keeping the login experience smooth for users.
What do you dislike about the product?
One area that could be improved is the admin UI, which can sometimes feel a bit complex when managing many applications or policies. It may take some time for new administrators to get familiar with where certain settings are located. Additionally, troubleshooting authentication or SSO configuration issues can occasionally require digging through multiple logs or settings. Improving the debugging experience and simplifying some workflows would make the platform even better.
What problems is the product solving and how is that benefiting you?
Okta helps us centralize authentication and access management across multiple applications. Instead of managing separate credentials for different tools, users can securely access everything through SSO. This reduces password fatigue for users and improves overall security with features like MFA and centralized policies. It also makes user provisioning and access control much easier for admins, saving time when onboarding or offboarding team members.
Easy SSO and Strong MFA That Save Time
What do you like best about the product?
I like it’s multi factor authentication which helps the systems from unwanted or unsafe access. I also like its SSO which is very easy and convenient. It also saves a lot of time using it. I do hybrid work so it supports remote work office culture as well.
What do you dislike about the product?
The configuration and setting up it is complex and difficult in small companies due to which employees can face delayed login issues which leads to workflow problems
What problems is the product solving and how is that benefiting you?
Saves times by having SSO feature and working on confidentiality data can be safe and secure . Can manage multiple applications in same time which doesn’t cause us irritation and frustration
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)
Strong SSO and Robust MFA for a More Secure Environment
What do you like best about the product?
Strong SSO capabilities and robust MFA help secure the environment.
What do you dislike about the product?
The high costs have affected our organization’s use of OKTA. In addition, the initial configuration is quite complex and takes significant effort to set up properly.
What problems is the product solving and how is that benefiting you?
It has helped in reduciing the password reset tickets for the L2 engineers.Also it is more secure and safe. The adaptiveness has helped us a alot.
Secure, Easy Access Across PC and Mobile with Okta
What do you like best about the product?
Okta help us to keep our account more secure and easy to access when needed. I can connect my okta account both in PC and mobile very easily.
What do you dislike about the product?
Setting up SSO and MFA for the first time can be very tricky, and the same interface needs to be verified multiple times. Also, sometimes an authentication failure pops up without clearly telling us what the main issue is.
What problems is the product solving and how is that benefiting you?
We need to manage dozens of apps which have separate username and passwords and in such cases due to SSO login we can easily access the different platform very easily.
