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)
Secure access to cloud accounts has streamlined authentication and supports flexible MFA recovery
What is our primary use case?
I have been using Okta Workforce Identity for single sign-on purposes to identify and authenticate my identity and access resources at AWS. Whenever I want to connect to Amazon Web Services, I provide a particular CLI Okta command, which opens a window where I am redirected to Okta Workforce Identity's single sign-on page. I authenticate myself through mobile, and once that authentication is completed, I am able to access a particular account according to the role that I have configured in the CLI command.
What is most valuable?
The best features that Okta Workforce Identity offers are single sign-on, multi-factor authentication, and privileged access management. It has reduced the time required for authentication and provided a secured way of accessing the Amazon web console.
What needs improvement?
The user interface could be enhanced to allow direct number selection for multi-factor authentication instead of typing out information.
For how long have I used the solution?
I have been using Okta Workforce Identity for two years.
Which solution did I use previously and why did I switch?
I used Ping, but I find Okta to be more reliable with a great user interface.
What was our ROI?
Time saved is a great example of return on investment. It has saved approximately 50 to 80 percent of our time.
What's my experience with pricing, setup cost, and licensing?
The pricing and licensing setup is typical, and since it follows a per-user, per-month subscription model, it is helpful.
What other advice do I have?
One of my team members lost his phone and was unable to do a direct Okta Workforce Identity login. At that time, email multi-factor authentication was useful and helped him to get logged into Okta Workforce Identity and authenticate himself. I do not see any areas for improvement as Okta Workforce Identity is at its best level currently. Okta Workforce Identity is reliable, and its user experience and user interface are great. I would recommend Okta Workforce Identity to others. My overall experience using Okta Workforce Identity has been excellent. I have given this review a rating of ten out of ten.
Which deployment model are you using for this solution?
Private Cloud
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)
Has improved secure access to all applications through a single login point
What is our primary use case?
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.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
I have been working with Okta Customer Identity for more than three years.
What do I think about the stability of the solution?
I rate Okta Customer Identity a 10 out of 10 for stability; it is the best.
What do I think about the scalability of the solution?
The scalability part of Okta Customer Identity is fine, there is no blocker and we can upgrade whenever we need.
How are customer service and support?
Okta Customer Identity's technical support is fine; they help to fix tickets within the timeline and their support is very good.
How would you rate customer service and support?
How was the initial setup?
The initial setup process for Okta Customer Identity is simple.
Which other solutions did I evaluate?
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.
What other advice do I have?
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.
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?