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.
Okta Identity Platform [Private Offer Only]
Carahsoft Technology Corp.External reviews
37 reviews
from
External reviews are not included in the AWS star rating for the product.
Centralized access has improved workforce security and streamlines employee lifecycle management
What is our primary use case?
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
I have been using Okta Platform for approximately five years to manage identity and access across our global workforce.
What was our ROI?
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.
What other advice do I have?
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.
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 through single sign-on and adaptive authentication for onboarding and application integration
What is our primary use case?
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.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
I have been working with Okta Customer Identity for six years.
What do I think about the stability of the solution?
There are no doubts regarding the stability of Okta Customer Identity. It is scalable and we can directly make use of this tool.
What do I think about the scalability of the solution?
The solution is scalable.
How was the initial setup?
The setup for Okta Customer Identity is straightforward.
What's my experience with pricing, setup cost, and licensing?
The price of Okta Customer Identity is acceptable.
What other advice do I have?
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.
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?
Neutral
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?
Amazon Web Services (AWS)
Authentication process improves security with quick and intuitive user interface
What is our primary use case?
I don't have many details about Okta Workforce Identity. I use the tool just to sign in to different applications that we have. We basically set up Okta Workforce Identity in our mobile phone. We do the scanning part and then enter our official email address and acknowledge that. They will send a code to the mobile phone. Once that code is authenticated, we are good enough to use that tool going forward. That's the initial setup we do on Okta Workforce Identity.
Okta Workforce Identity is really useful because all internal users that we have in our transfer server have now moved to it. In the progress, it's a suite, as it's a part of MOVEit Automation as well as MOVEit Transfer. On the MOVEit Transfer, all internal users in our company have moved to Okta Workforce Identity single sign-on option. The benefit was addressing issues where people were using incorrect passwords. When they continuously put incorrect passwords, their IP would get locked and their account would get locked. Additionally, there were very few users who kept passwords in secret tools or KeePass tools. Most of them were putting the passwords either in mobile phones or in OneNote or text documents where the data could get breached easily. To deal with all these issues, Okta Workforce Identity is a perfect tool where internal applications can be signed in using your authentication tool itself. It functions as two-factor authentication.
I am using Okta Workforce Identity for login purposes only.
What is most valuable?
The best feature is the speed and execution of Okta Workforce Identity. The moment you click on single sign-on, you immediately get the notification on your mobile phone, then you do the authentication and within a second you get authenticated. The entire customer experience is very good. The user interface is pretty simple, straightforward, and really good.
Multi-factor authentication in Okta Workforce Identity is very useful so people who do not have access or are trying to access using just a user ID and password will be completely blocked because of this two-factor authentication. You will get the code, and as your device is authorized in the system, only that device can be used for the authentication purpose. A third person trying to access or hack your data will not be able to do that anymore. Additionally, you don't have to remember your passwords going forward. Previously, every 60 days or 90 days, passwords kept changing. With the two-factor authentication or single sign-on option in Okta Workforce Identity, you don't have to remember it anymore or write down passwords in plain text. If something goes wrong, we have the IAM team which can unlock your account immediately if you have issues.
What needs improvement?
Currently, in Okta Workforce Identity we get the two-digit authentication code. Instead of getting the two-digit authentication code, if we had an option to do fingerprint verification, that would be beneficial. We have already secured that only the device where we have installed Okta Workforce Identity can do the authentication. However, if that phone or device gets stolen, somebody else can log into the system using that code. If there was a fingerprint option, then only the person who has already added their fingerprint on their mobile phone could access it. This would provide double protection.
For how long have I used the solution?
I started using Okta Workforce Identity four months ago in our company.
Which solution did I use previously and why did I switch?
I didn't have any single sign-on technologies before Okta Workforce Identity. I started with AWS and then adapted Okta Workforce Identity.
How was the initial setup?
The initial setup of Okta Workforce Identity is straightforward. We haven't encountered any issues because if we had, we might have gotten emails from the security or the IAM team who handled the installation. Nothing went wrong. It was pretty smooth.
What was our ROI?
I have seen ROI from Okta Workforce Identity. It was a great implementation. Initially, we had multiple places where we had to store links in browsers to access different applications. We don't have to do that any longer now. We have our dashboard to log in via Okta Workforce Identity. Once logged in, it shows our company's portal where we see different applications. When you click on an application, you automatically get signed into that particular website.
What other advice do I have?
Most of our internal applications are getting migrated to Okta Workforce Identity. We started initially with AWS, then we added Confluence. We also migrated the internal rewards point feature. The entire migration is being done in a phase-wise manner. Currently, 15 applications have been migrated with only a few remaining that we use daily.
I haven't used the Lifecycle Management feature in Okta Workforce Identity. The decision to go with Okta Workforce Identity might have been due to the best customer experience and favorable long-term license deals.
I would recommend Okta Workforce Identity because it's a security standard. Two-factor authentication is always better than using user ID and password. The entire world is now dealing with data and we have to secure it as much as possible. For file transfer, we are using encryption and decryption. Similarly, for accessing internal applications or internal websites, I would recommend using Okta Workforce Identity or any related tool which can provide two-factor authentication as it's a standard nowadays.
I rate Okta Workforce Identity 9 out of 10.
Effective Management of Authentication with Notable Improvements Needed in Governance
What is our primary use case?
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.
What is most valuable?
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.
What needs improvement?
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.
For how long have I used the solution?
[Full sentence answer to 'For how long have I used the solution?' from the text.]
How are customer service and support?
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.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
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.
How was the initial setup?
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.
What other advice do I have?
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.
Empowering seamless access with single sign-on integration and robust authentication
What is our primary use case?
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.
What is most valuable?
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.
What needs improvement?
I believe that if we integrate the workflows section into the main Okta Workforce Identity dashboard, it can be very useful.
For how long have I used the solution?
We have been using Okta Workforce Identity for about 4 to 5 years now.
What was my experience with deployment of the solution?
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.
What do I think about the stability of the solution?
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.
How are customer service and support?
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.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
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.
How was the initial setup?
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.
What was our ROI?
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.
Which other solutions did I evaluate?
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.
What other advice do I have?
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).
Offers an extensive range of ready-to-use connectors and robust documentation and training resources
What is our primary use case?
We are currently using Okta Customer Identity as a managed service platform. We are building a platform where our customers can subscribe to different products of Okta Customer Identity, such as Access Manager, Entity Manager, and Okta Privileged Access. Our customers purchase subscriptions and create a PO number, which we use to perform technical implementations.
What is most valuable?
Okta Customer Identity is a SaaS-based application, making it easy to configure compared to competitors. It offers around eight thousand five hundred out-of-the-box connectors, providing an edge over other tools. It eliminates the need for configuring connectors using REST APIs as they are readily available. The Entity Manager is integrated with SSO, and Okta Customer Identity offers a wide range of protocols for federated single sign-on and token exchange. Okta Customer Identity also provides excellent documentation and training resources.
What needs improvement?
In Okta Identity Governance and Okta Privileged Access, some features are still being developed. Integration with Active Directory servers, Cisco routers, and switches is not currently available. Additionally, integration with platforms like DB2 and Oracle or SaaS-based databases is still in progress. These features need further development for full functionality.
How are customer service and support?
The support from Okta Customer Identity is excellent, and I would rate it eight out of ten.
How would you rate customer service and support?
Positive
How was the initial setup?
Okta Customer Identity is known for its easy configuration and deployment.
What's my experience with pricing, setup cost, and licensing?
Okta Customer Identity is considered cheaper compared to other tools in the market, such as IBM and CyberArk products. Further details on costs would require consultation with our sales team.
Which other solutions did I evaluate?
I compared Okta Customer Identity with solutions like IBM Security Access Manager and CyberArk. While CyberArk is a fully functional tool with all features, Okta Customer Identity is more affordable and offers comparable functionality.
What other advice do I have?
I rate Okta Customer Identity as nine out of ten. The Privileged Access Manager part is still in development but is expected to be in line with competitors like CyberArk or BeyondTrust soon.
Focus on seamless integration and advanced security management enhances application usage and threat detection across multiple countries
What is our primary use case?
We are an advertising company with around 400 employees in four different countries: Peru, Chile, Mexico, and Brazil. We have implemented Okta Customer Identity to enforce security in our applications and ensure all users access them securely. We use Okta Customer Identity for various applications like Office 365 and several other applications essential to our business.
What is most valuable?
Okta Customer Identity focuses on providing top-notch identity management solutions. One of its most valuable features is its easy integration with various applications through its extensive application directory, offering hundreds or thousands of applications ready to configure. This integration is significantly easier compared to Microsoft Entra ID, where we encountered numerous issues. We particularly value its real-time reporting capabilities. For example, we detected cyberattacks from countries like Russia and Asia and were able to block those IP addresses and configure our system for more security. These advanced security features and reporting capabilities make it easy to manage.
What needs improvement?
Okta Customer Identity is continuously improving its solution. Since we started using it in 2019, we have observed numerous enhancements to increase security.
For how long have I used the solution?
We have been using Okta Customer Identity for more than five years in our company.
How are customer service and support?
We had an issue a couple of years ago that was swiftly resolved by the support team, showing their efficiency. They also offer a comprehensive knowledge base on their website, which is very helpful for addressing any issues or queries.
How would you rate customer service and support?
Neutral
Which solution did I use previously and why did I switch?
We evaluated Microsoft Entra ID but chose Okta Customer Identity because it is easier to integrate with various applications. Microsoft Entra ID presented many challenges and it was more difficult to manage integration processes.
How was the initial setup?
The initial setup of Okta Customer Identity is straightforward due to its well-architected solution. It is intuitive and user-friendly for administrators to manage.
What's my experience with pricing, setup cost, and licensing?
Okta Customer Identity is expensive compared to other solutions, but we believe the investment is justified given the rising cybersecurity threats. Despite the cost, it's cheaper than the potential financial loss from a security breach.
Which other solutions did I evaluate?
We evaluated Microsoft Entra ID.
What other advice do I have?
Overall, I would rate Okta Customer Identity a ten. Okta Customer Identity is solely focused on identity management, which makes them excel in this area.
Provides robust identity and access management with seamless integration across hybrid setups
What is our primary use case?
We use Okta for identity and access management for our internal services, cloud services or applications (SaaS). We have a hybrid setup since we have a global workforce, so we unify our IAM services.
What is most valuable?
The most useful features of Okta for my organization are identity and access management, single sign-on, and the flexibility for hybrid setups.
Okta enables multi-factor authentication, which enhances security, especially for SaaS applications. The integration capabilities of Okta are very flexible, with multiple protocols that can be integrated, especially for single sign-on. Any API can also be added, making it mature in terms of integrating with other identity providers, particularly Active Directory or Azure Entra ID.
What needs improvement?
Okta should have at least a local presense for countries that align with or comply with GDPR or data sovereignty, so there are no compliance or audit questions. There are integration issues with Office 365; such as groups not updating correctly in Okta. Okta should work on resolving them.
For how long have I used the solution?
I have been in the organization for one year, and it has been more than three years now that Okta has been used.
What do I think about the stability of the solution?
As long as you have Internet connection, there are no issues with the stability.
What do I think about the scalability of the solution?
Okta is scalable and reliable, with no downtime or service disruption encountered over the years.
How are customer service and support?
My team contacts Okta support for increased integration requirements. They are very supportive; they just open a ticket, and they support us very professionally.
How would you rate customer service and support?
Positive
How was the initial setup?
The setup process is pretty straight-forward, having experience with different single sign-on (SSO) and identity access management, I can manage the setup process with ease. Okta provides clear guidelines and documentations as well.
What's my experience with pricing, setup cost, and licensing?
Pricing for Okta is reasonably not that much, however, I don't have access to the commercial aspect.
What other advice do I have?
showing 11 - 20