Okta Platform Reviews

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.

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.

The user interface could be enhanced to allow direct number selection for multi-factor authentication instead of typing out information.

I have been using Okta Workforce Identity for two years.

I used Ping, but I find Okta to be more reliable with a great user interface.

Time saved is a great example of return on investment. It has saved approximately 50 to 80 percent of our time.

The pricing and licensing setup is typical, and since it follows a per-user, per-month subscription model, it is helpful.

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.

We are providing identity access management to the customers with Okta Customer Identity, and then application integration, user onboarding, and related functions.

I'm a senior consultant using Okta Customer Identity.

We are the implementers of Okta Customer Identity as users.

The most valuable feature of Okta Customer Identity is the application interface with SSO. Integration with SSO helps us make use of the credentials. Once we log in, we get the opportunity to explore many applications within the organization with the same login, with no need to log in again.

Adaptive authentication in Okta Customer Identity is a flexible feature that is very secure and user-friendly. The authentication is more complex for man-in-the-middle attacks while remaining useful for end users.

Okta Customer Identity's API gives a clear view of how user onboarding takes place, so we can easily configure with Postman. We can onboard and off-board users, which is very flexible through the APIs.

Regarding multi-factor authentication, it helps reduce unauthorized access in our organization. We are using passwordless authentication with Okta FastPass on mobile devices. Users can get authenticated with two-factor authentication, first entering the password, then directly using the second factor authentication with Okta FastPass.

It is complex when adding it for the first time to users of Okta Customer Identity. For end-users and new users, it can be complex to use.

Okta Customer Identity analytics and reporting tools do not help much to improve customer engagement strategies.

Training should be provided to novice users. There are multiple online learning resources in the Okta documentation part, which users can access free of charge.

I have been working with Okta Customer Identity for six years.

There are no doubts regarding the stability of Okta Customer Identity. It is scalable and we can directly make use of this tool.

The solution is scalable.

The setup for Okta Customer Identity is straightforward.

The price of Okta Customer Identity is acceptable.

For those planning to use Okta Customer Identity, MSA and SSO are among the best features that can be recommended for users. We also have direct integration with Active Directory. There are many features that will be helpful for organizations to easily integrate applications and manage user onboarding and off-boarding.

The solution is deployed on the cloud and I did not purchase it through AWS Marketplace. I usually buy for the entire organization.

I rate Okta Customer Identity 10 out of 10.

The main differences between Okta Platform and Cisco for the IAM solution are that Okta Platform does not have an exclusive product that is tagged federal, and it depends on the person who is deciding it. The way I made Okta Platform comparable with Duo Federal is by attaching it to CAC, which is used by the military.

In my opinion, Okta Platform's best features include federation, which is very important, especially when you work with different systems. SAML plays an important role, and then there is the OAuth feature of Okta Platform and the OpenID. Those three—SAML, OAuth, and OpenID—are crucial. The scope, which is essentially the permission that you give to a token, and then the token that is being used by the application or by your user to authenticate themselves, is also important.

Automated lifecycle management positively impacts onboarding and offboarding processes for Okta Platform in terms of efficiency. When you integrate with Workday, ServiceNow, ITSM, and HR, those integrations make the onboarding process quite smooth. Whether the application involves a new employee, a joiner, or a leaver, those integrations handle all of those scenarios.

Some areas for improvement with Okta Platform, especially concerning AI and the federal aspect, are acknowledged as areas that Okta Platform needs to work on to offer features comparable to those provided by Duo.

In terms of Okta Platform's stability or scalability, I would grade its stability at around seven. Okta Platform is quite stable compared with Oracle. It is scalable compared with Oracle as well, but that is where the effort will come in. When you are doing basic things, it is straightforward, but if you are going to be doing workflows, other things, or recon and trust, then there is effort involved, and that is where it gets convoluted.

On a scale of one to ten, I would rate Okta Platform's support or customer service as around seven. With Duo, I was not directly involved because there is a group that handles it. I am a contractor, so my account does not have the privilege to open a ticket. I document it and pass it to a group, which is most likely the help desk. They are the ones who create the ticket and interface with Duo. If there is a need for collaboration, that is where I come in, and they introduce me to Duo, saying that they want me to collaborate on this particular design.

Positive

My experience with deploying Okta Platform shows that it is not that difficult to deploy, but the integration is challenging. The integration, the tweaking, the configuration, and the tailoring require significant effort.

Compared to Cisco, deploying Okta Platform is a little bit harder. Cisco Duo is quite straightforward.

Regarding costs, I think Okta Platform is more expensive compared to Cisco, but it is less expensive when compared with Oracle.

The reason we recently switched to Okta Platform was a decision made while I was not on the project, as I was with the Air Force at the time. The decision was made by a different branch, I think with the Marines, who were using it and then said that Oracle is obsolete. It was presented as a short message: 'We are using Okta Platform and it works well.' They then asked me to investigate and see how we could use Okta Platform integrated with Oracle.

The improvements I already mentioned are based on the fact that IAMs are evolving, and integration with other components is important. My experience with Okta Platform's integrated PAM capabilities involves many steps. There are many steps, and you have to do this, but as long as the document is fine at the start, it is a trial and error process. If it works or not, then you are going to repeat the whole thing and try a different scenario. The project management does not always see the effort behind all of this tweaking Okta Platform to do what they want it to do and meet their business requirements. I would rate this review a seven overall.

My job title at FNTS is Senior Security Analyst.

I have been using Okta Platform for three years.

My main use case for Okta Platform is multifactor authentication.

For multifactor authentication in my organization, to log into specific sites, we need Okta Platform as a multifactor authentication to get in.

The process has made logging in easier and more secure for me and my team.

The best features Okta Platform offers are easy SSO, strong security, and improved productivity.

Out of easy SSO, strong security, and improved productivity, the single sign-on has had the biggest impact for my team because it protects effectively and signs on without problems.

Okta Platform has positively impacted my organization with easy single sign-on, as we need single sign-on multifactor authentication for various things and Okta Platform is very secure.

I have definitely noticed specific outcomes such as fewer help desk tickets, as it is very straightforward, streamlined, and easy to use.

I think the setup in the beginning can be a bit of a learning curve.

I have been working in my current field for seven years.

Okta Platform is stable.

Okta Platform's scalability is good.

The customer support is good.

I would rate the customer support on a scale of 1 to 10 as a nine.

Positive

We previously used Duo and switched because we thought Okta Platform had better features.

I think the setup cost was pretty good, but the pricing is moderate.

I am not sure about Okta Integration Network's capability to enable faster deployments, as I have not used it in that capacity and I have not deployed it.

I would assess the role of Universal Directory as a single source of truth for user identities in my organization as it works effectively.

I cannot describe the impact of automated lifecycle management on onboarding and offboarding processes in terms of efficiency.

I have not had any experience with Okta Platform's integrated Privileged Access Management, PAM capabilities, so I cannot compare them to using separate tools.

I have seen a return on investment, as there have been fewer employees needed for multifactor technical responses, and the number of people to assist with tickets has gone down since Okta Platform is a really easy system to use.

I think the setup cost was pretty good, but the pricing is moderate.

Before choosing Okta Platform, we evaluated other options, including Microsoft.

I would advise others looking into using Okta Platform to look very carefully at the pricing and move forward.

My company does not have a business relationship with this vendor other than being a customer.

I find this interview satisfactory and do not think anything needs to change for the future.

I would rate this review an overall eight out of ten.

Okta Platform is my primary tool for implementing Single Sign-On and Multi-factor Authentication. I use Okta Platform primarily for securing employee access, along with leveraging it for lifecycle management to automate user onboarding and offboarding.

The Single Sign-On and Multi-factor Authentication features are the best that Okta Platform offers. These features make my work easier and more secure by automating joiner, mover, and leaver processes, so when a new employee is added to our HR system, their account is automatically created in Slack, Zoom, and the applications we use, increasing productivity without wasting time.

The sharing of secure access via user groups allows us to instantly provision access to shared tools for our remote project teams, ensuring they have exactly what they need when they join a call or project. Okta Platform has positively impacted our organization by dramatically improving our security posture, enforcing Multi-factor Authentication across all applications, and increasing productivity by allowing employees to access all their tools with one set of credentials.

Okta Platform could be improved by offering more out-of-the-box templates for advanced workflows and making the administration console faster when searching through a very large group of users.

I have been using Okta Platform for approximately five years to manage identity and access across our global workforce.

We have seen a 60% reduction in password reset help desk tickets and a significant decrease in the time it takes to onboard new employees from when they join.

I advise others looking into using Okta Platform to start with a clear group strategy before beginning; if the requirement for groups and naming conventions is organized from day one, setting up security policies and automated provisioning will be much easier. I would rate this product 9 out of 10.

My main use cases with the Okta Workforce Identity include preparing my certification and doing integrations such as org-to-org integration or Active Directory, and it is mostly about integration.

As an individual user, I appreciate that I can create my own lab with Okta Workforce Identity. They provide instances for me to create almost ten instances to test.

Some of the best features with Okta Workforce Identity are configuring the SSO through Okta to Okta. For me, it was the certification and the integration I worked on because it was my pathway to prepare my certifications, along with the directory and network security, the IP zone and related components.

We use the Single Sign-On feature with the Okta Workforce Identity, and I configure it through the platform, especially for Okta-to-Okta. From one instance, I could switch to another using the SSO, as Okta to Okta allows the SSO feature.

The impact of SSO on my IT overhead and user experience has been significant because it reduced authentication fatigue, password sharing, and password reusing. For administration, it is integrated, and it is great for IT support. For the end user, it is beneficial as they do not have to remember a password or keep the password on a post-it for different applications; they just authenticate once to access several services and service providers.

Areas for improvement with Okta Workforce Identity would be in the governance place; for me, it is light. Okta is mostly focused on execution and runtime, which means maintaining authentication and ensuring people connect with the appropriate session. However, it could improve in the governance part, particularly regarding better role management and workflow, as I feel it is tedious on Okta. I think Okta could enhance the governance area of identity.

I have not personally experimented with technical support from Okta Workforce Identity, but I see there is a good community and many resources available. I have not tested Saviynt's support either, but I know there is direct contact with Saviynt support.

I cannot rate the support for Okta Workforce Identity directly because I have not experimented with it; however, I notice good communication within the community, but it would not be fair to rate them without personal experience.

Positive

I have tested different solutions before Okta Workforce Identity, including Saviynt and SailPoint, and decided to go deeper into Okta because it allows me to create my own lab. I worked on a homemade solution for about three to four years back, spending five years on that project.

My experience with the initial setup of Okta Workforce Identity is that it is straightforward and not huge. The initial setup is simple and, considering it is a SaaS solution, it is easier. I have tested the connector, which is available for on-site solutions for Active Directory, and there is still a lot of infrastructure relying on Active Directory.

Regarding experience with pricing for Okta Workforce Identity, I do not have the pricing on IGA solutions or IAM solutions, but from my study two years back for a project, I found it is not that huge.

The main differences I notice between SailPoint and Okta Workforce Identity for the IAM solution suggest that they are in different categories. SailPoint is mostly for the admin part, while Okta is excellent on the runtime section, focusing on secure authentication and SSO. SailPoint is used for configuring identity with the right entitlement while Okta is about ensuring secure connections and efficient user authentication.

I would rate Okta Workforce Identity seven out of ten.

My use cases for Okta Platform involve having a single place for authentication, as my company requires it for all of our applications that we use with our organization, which includes SAML and SSO. It's a critical piece for authentication, and the token generally lasts about eight hours based on our company's configuration, allowing us to sign in once a day and eliminating the need to enter credentials multiple times for different applications. Okta Platform authentication is essential because it minimizes the hassle of signing into multiple applications while maintaining security. Essentially, all my critical apps are secured with Okta Platform, which also provides features like second-factor authentication through cell phone verification or facial recognition. Overall, it's very functional and an integral part of our business processes.

Regarding how Okta Platform helps secure access to cloud infrastructure, APIs, containerized workloads, or AI services in our architecture, I can't provide an authoritative answer on how security is hardened since I wasn't involved in that aspect. However, I know that it provides security. My company has been using it for four years without plans to change because it remains secure, even as we increase our internal applications and expose some to clients.

The workloads secured by Okta Platform are hosted across multiple cloud providers, including AWS, Azure, and some GCP, so it encompasses all of those.

For AWS, we have integrated EC2 instances with Okta Platform, and I'm not sure about other services or buckets related to the things you mentioned, such as Amazon Voice.

I see the benefits of Okta Platform immediately upon deployment, as it saves time. Dealing with multiple authentications without a federated system is time-consuming, requiring different passwords for different applications, which is a hassle. As soon as Okta Platform was implemented, there was an immediate improvement in the ease and speed of secure authentication.

Personally, I have noticed measurable security and operational improvements since implementing Okta Platform, primarily due to the ease of access it provides in a more secure manner while saving time.

What I dislike about Okta Platform is that sometimes there has been some downtime. It doesn't happen often, but ironically, it did occur on a day I knew this call was coming, leading to a brief period when Okta Platform authentication didn't work. We had to rely on third-party IT support to resolve it. When this happens, it stops us from accessing what we need until the issue is fixed.

I have to mention some occasional downtime with Okta Platform. It doesn't occur very often, but when it happens, it's crucial because you can feel stuck without it.

I have been working with Okta Platform for just over four years.

Regarding stability, there hasn't been much to note aside from some occasional downtime, but I appreciate the different options provided by Okta Platform for verification. You can manually enter a password, use push notifications, or facial recognition, which can be more convenient depending on the context, whether mobile or at a desk.

I believe Okta Platform has been scalable. My company has integrated all major applications, and it has supported our growth without issues.

I've contacted internal company IT support a few times while learning the intricacies of Okta Platform, but I've never reached out to Okta Platform's direct customer support.

Positive

My organization hasn't tried any alternatives to Okta Platform, and I personally haven't had the need to seek them out. Some people look for alternatives such as password managers, but those are not the same. Implementing a solution such as Okta Platform isn't straightforward without a team behind it, so once it was working here, there wasn't a felt need to explore other options. I'm unsure of what the previous system was, but I believe they considered Cisco Duo at one point without ultimately proceeding.

The initial deployment of Okta Platform was easy and without any significant bumps, as far as I know.

The deployment of Okta Platform involves a lot of collaboration across the security team, working with the CISO to ensure adherence to standards such as SOC and FINRA. Though technically it's not a one-person job, my company wouldn't implement it that way either, as there is always a team behind it.

I probably don't think of anything else, as Okta Platform does what it intends to do. Given my experience in the field, I recognize that these tools work well, but they're only as effective as their configuration and security hardening. My company has done an excellent job with Okta Platform, and I feel it's a quality product because it effectively integrates single sign-on and SAML authentication.

I'm not entirely sure if our organization uses Okta Platform to protect non-human identities, such as service accounts or AI agents, as we've rolled out chatbots and are developing them. I can't confidently answer that question.

Okta Platform does help address specific industry or regulatory requirements, such as those in healthcare and financial services, for both our organization as an outsourced IT service provider and internally when accessing platforms.

On my end, there are updates from time to time for apps on mobile devices or operating systems that need to be addressed, but company policies manage updates for company-owned workstations, so it's not too burdensome.

I'm not aware of any formal partnerships with Okta Platform in my department, so I can't speak to that.

I would rate this review an 8 overall.

One of the majorly used use cases for Okta Workforce Identity is the assignment of different SaaS applications, which are cloud-based, and using them with single sign-on. Users don't have to remember the password for each and every online cloud-based application. They just need to sign in with one email and password. This is one of the major benefits of using Okta Workforce Identity.

One of the best features of Okta Workforce Identity is its integration with different SaaS applications, which makes it a better product than the competitors.

The multi-factor authentication feature in Okta Workforce Identity is very good. It has its own verification app as well. It is very good in authentication, and we can use hardware keys, software keys, or any authenticator, majorly known authenticator app, for multi-factor authentication.

The provisioning and deprovisioning features of Okta Workforce Identity are very good. We can automate them as well, and we can provision users, groups, applications, and provision tools based on specific groups as well. The product is very good in that as well.

I believe that if we integrate the workflows section into the main Okta Workforce Identity dashboard, it can be very useful.

We have been using Okta Workforce Identity for about 4 to 5 years now.

In terms of the initial setup and deployment, I find it to be very easy. We have to set it up for the first time, and it has a very straightforward implementation. We have the pictorial and video guides on the Okta Workforce Identity websites on how to deploy it, how to set up employees, how to provision them, how to create groups, and how to set up devices. Each and everything is documented, and it's pretty much straightforward to use.

Okta Workforce Identity is a stable product. We had an issue with the Okta Workforce Identity dashboard once in 2023 when we had an outage, but it recovered in a few minutes.

We have never felt the need to contact the Okta Workforce Identity support team. It has been up and running. We had an issue with the Okta Workforce Identity dashboard once in 2023 when we had an outage, but it recovered in a few minutes.

Positive

We weren't using any single sign-on application or solution before choosing Okta Workforce Identity. This was our first product that we implemented in our company.

In terms of the initial setup and deployment, I find it to be very easy. We have to set it up for the first time, and it has a very straightforward implementation. We have the pictorial and video guides on the Okta Workforce Identity websites on how to deploy it, how to set up employees, how to provision them, how to create groups, and how to set up devices. Each and everything is documented, and it's pretty much straightforward to use.

I don't have the exact quotation or the exact pricing details for Okta Workforce Identity, but everything comes at a cost. However, when it gives you scalability and reliability, then I don't think the pricing matters.

I believe we have a lot of features in Okta Workforce Identity and I don't think we should be having more features in it as it's currently packed with a lot of features.

I believe we have a lot of features in Okta Workforce Identity and I don't think we should be having more features in it as it's currently packed with a lot of features. On a scale of one to ten, I would rate Okta Workforce Identity a nine out of ten (9.9).