Although I am a fan of Okta Platform overall, there are areas where it could improve security outcomes and reduce admin friction. My top improvement areas include the system log and analytics upgrade, which are great for point troubleshooting, but trending and root cause analysis across large tenants still require exporting to SIEM. Verbose queries and long-range retention costs can add up. Additionally, while certificate rotations are better than most, the process is still manual for busy portfolios, especially concerning multi-SP SAML certificate rotations and app metadata drift.

Two more buckets of potential improvements for Okta Platform involve user experience and security. There is the issue of push fatigue and prompt sprawl, where users receive multiple prompts across different apps and sessions.

I arrived at the rating of eight because the core controls are strong and reliable, but a few operational UX and UI gaps prevent it from being rated higher. The reasons for not giving it a nine or ten include ongoing issues concerning safety and change safety, the complexity of group rules and mappings, and the lack of robustness in policy management. Additionally, there remains a need for more manual involvement than necessary, especially for large portfolios and dual certificate rotation, along with proactive SP data metadata validation.

View full review »

While I see very few areas for improvement in Okta Platform, I do note its high cost, which can be particularly challenging for smaller organizations looking to utilize advanced features like Okta Workflows. Additionally, there are reporting limitations, as some users find Okta Platform's built-in reports less detailed compared to competitors. Furthermore, frequent multi-factor authentication prompts can cause MFA fatigue, disrupting user experience. Lastly, there is limited on-premise support, which, while robust in the cloud, is often expensive to manage for legacy on-premise applications, making these features candidates for enhancement.

View full review »

Okta Platform is already improving in many ways because whatever the current hot topic is, such as AI, Okta Platform is also bringing it up. I believe they are already one step ahead for every industry standard, so I do not think improvable things will do because they are already in the pipeline.

One feature I can mention is that there should be an optional registration option for multiple MFA factors. If a user has already migrated to one type of multifactor authentication and wants to register for another multifactor option, there is currently no option unless it is required. If an industry standard requires a new MFA, we want to give users the option for other multifactor authentication, but currently, this is a mandatory feature only. Some cases mean users do not want to register for new things, so whenever they want to feel comfortable, they should be able to do it. This feature is really restricting because it is mandatory. I want to have it as optional and more flexible for registering multiple MFA options.

View full review »

I would definitely see improvements in the governance module of Okta Platform. The way we do certification of accesses, certification campaigns, and access requests could be improved. A better way for users to actually request an instance in Okta Platform, for example, an app, without having to use a third-party integration for ServiceNow or Jira Service Management, would be valuable. Having something built in to Okta Platform would be beneficial.

From the features perspective, functionality-wise, I would see recent features included in Okta Platform. Our company works on a hub-and-spoke model, and Okta Platform did introduce a way to have more of a federated level. What they call claim sharing, and we really would appreciate a bit more improvement on that functionality, since that functionality helps us to have a single identity on a hub and pass that identity to the other spokes and have seamless login between all of them. Claim sharing helps with that, but the function is still not the best, especially related to authentication policies. There are still some issues, especially when we have some mismatch between the authentication policies on different spokes. I definitely would appreciate some more improvements. Additionally, I would appreciate a bit more improvements on the logging features of Okta Platform, which still are not the best.

View full review »

It has been two years for me with Okta Platform, so I still cannot judge if they need improvement in specific parts. So far, it is covering what my requirements are. Perhaps in the future, if I encounter limitations, I can provide feedback. For now, I have no concerns about this.

I can say one more thing. I am in Saudi Arabia, and Okta Platform is hosted somewhere in Germany on the AWS platform. Every country has their own compliance requirements. Saudi Arabia requires any application, every software, everything to be hosted inside the kingdom. This is our country's compliance requirement. Okta Platform is not hosted in the Saudi region. In fact, it is not even in the Middle East; it is somewhere in Germany. If it were moved to every country with their own data center, it would cover all of our compliance related issues, and every country could align with that. Saudi Arabia especially needs every application, every software, every tool to be inside the kingdom, where Okta Platform is somewhere outside. If they move to the Saudi region or somewhere in the Middle East, it would be really helpful for us.

View full review »

The one thing which can be improved in Okta Platform would be the certifications which they provide. It is crucial for people to get recognized in the industry. Also, some of their documents have outdated images or screenshots, leading to confusion. Keeping the knowledge base updated quarterly is advisable.

In my environment, I have not specifically used some concepts like device management and Okta Platform's OAuth in the CISM platform. I would like to have further implementation progress on them.

View full review »

While there are many good things about Okta Platform, I would like to see improvements, especially in the IGA capabilities, which are limited compared to more dedicated IGA tools. I believe adding this would give them a real benefit. Additionally, it is not designed as a privileged access management solution, referred to as PAM. As I come from a Microsoft background, I see that Microsoft has both IGA and PAM capabilities, which Okta Platform lacks. Another area for improvement is pricing; it becomes complex and expensive when you add features. I would like to see licensing transparency, possibly some cost control notifications. Lastly, better policy visualization would be nice to have, showing how the policies configured can be represented more visually.

View full review »

I would say Okta Platform needs to improve on pricing because now Entra ID is providing this kind of capability built-in with P1. People are moving towards those solutions because it is more integrated, provides single sign-on as well, and can do device trust and certificates. If Okta Platform needs to stay in the market, they should consider bringing down their pricing to maintain or regain business, as there is no comparison now with Entra ID.

I think pricing, setup cost, and licensing for Okta Platform are on the higher side. They need to reduce the pricing if they wish to survive and remain competitive.

View full review »

For Okta Platform to improve, I would suggest enhancing debugging for SAML, as we have faced issues using OIDC or SAML without any user-side tools to identify what is happening. This has become a significant challenge, particularly with SAML logins in the context of AWS usage. If the debugging process is made easier, it would greatly improve our experience. I also find the initial policy setup complex, as it can be a nightmare given its intricacy. Although I do not handle it personally from start to finish, I recall those complicated days vividly.

View full review »

Okta Platform does what it promises that it does. It is certainly all cloud-based as a SaaS solution. For enterprises which really prefer to have their own identity within their own perimeter, Okta Platform might not be the solution they might look for. Of course, there are ways you can get your dedicated tenant, especially for governments and federal agencies and all of those things. I have not tried those use cases. I think Okta Platform is the best of the class and appears consistently at the top of the Gartner report and other research.

Based on the use cases I had, I was fairly happy with it. The PAM capabilities and attribute-based access controls, ABAC, represent a new paradigm. How practical that is for enterprises to deploy largely depends upon the use cases. There is always room for improvement, and it is not just for Okta Platform but typically for every single customer identity provider. There are a lot of other things the biometric and FIDO and all of those which can certainly be improved. However, that is more of a technological constraint rather than the vendor itself.

View full review »

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.

View full review »

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.

View full review »

Okta Platform is quite mature, but I would like to see more integration. While they have a vast range of integrations out of the box available, if their PAM and IGA capabilities were more mature, then Okta Platform could be the single solution for everything, covering access management, privilege access management, and governance of identity. This would mean one would not need to take multiple products for specific identity needs in each area.

View full review »

I have my own wish list of things that I would like Okta Platform to have. They released some features related to device access, such as Okta Device Access, which is an add-on that requires payment. I would expect Okta Platform to include more features over time in their less expensive subscriptions. I wish Okta Workflows could be included in a better way; we currently only have five workflows available, which doesn't provide much value. More workflows available in a paid subscription would be beneficial.

With AI permeating every service, I would like to have some kind of AI chatbot available on Okta Platform interface to ask questions about Okta Platform and how to integrate things. I relied on Google's AI chatbot to ask similar questions, but I would feel more confident asking them to an Okta Platform AI bot. I think someone mentioned there may be something coming from Okta Platform related to this.

View full review »

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.

View full review »

Okta Platform's pricing model can be expensive for smaller organizations, affecting user feature accessibility. Initial setup and configuration require careful planning and experience from administrators. Cloud-based infrastructure may lead to access issues during downtime or service disruptions. Support response time could be improved, especially for non-premium customers.

Pricing could be more competitive compared to alternatives like Ping Identity, OneLogin, and Microsoft Azure AD. More responsive customer service, enhancements in setup configuration, and support could improve the platform. Prioritizing customer issues in support tickets based on urgency level might enhance response time, helping businesses manage crises more efficiently.

View full review »

To improve Okta Platform, I think they should enhance the 2LO service-to-service aspect by integrating more features on the MCP side, allowing for authentication of containers running on the gateway. Instead of just client ID and secret, they could add a Vault-like storage for keys in integrated AWS services to smoothen the process.

The deployment experience with Okta Platform is generally smooth. They provide Okta Preview for non-production deployments, and I suggest they implement a green and blue rollback mechanism in production to avoid any delays for application teams during real deployments.

View full review »

In Okta Platform, I do not see much room for improvement because currently, they are managing automations and the new workflow, which helps with automation. Previously, this was not available in Okta Platform, but it was introduced recently.

The automation aspect can be improved.

View full review »

I have worked on Okta Platform's IGA features, and they were not great or up to the mark. While they were trying to get new features, it was not working as expected at that time when it was in beta. There are some features, especially on the customization side, that cannot be customized, and there are a few things that would be nice to customize as well.

I would like Okta Platform to protect non-human identities in the environment, such as service accounts.

In terms of industry or regulatory requirements, it depends on the person implementing Okta Platform. All necessary protocols need to be followed, but I don't think Okta Platform has set any templates to ensure these protocols are being followed. It would be a nice-to-have feature where they could set some templates and provide guidance on what can be implemented.

View full review »

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

View full review »

The major problem we face with Okta Platform is pricing because most of our clientele move away from Okta Platform because of the pricing. If someone is looking for on-premises solutions, they usually don't choose Okta Platform.

They predominantly try to go for Ping rather than Okta Platform because Ping provides a very wide variety of concepts and tools and details their tool on a very specific level, particularly their on-premises tools. Anyone who invests has to pay a higher price, and if with the same kind of structure they can get some other enterprise-grade tool that caters to all those things, they will definitely choose Ping rather than Okta Platform.

View full review »

Okta Platform does not recognize when I have already verified myself once on my HubSpot login across multiple tabs. I have to verify myself for every single tab. If there were a way to recognize that I already verified myself on that URL or domain and just give me access to the rest of the tabs instead of having to click one by one, that would be an improvement.

View full review »

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.

View full review »

Okta Platform could be improved or enhanced by adding more integration options for third-party applications.

View full review »

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.

View full review »

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

View full review »

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.

View full review »

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.

View full review »

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.

View full review »

I do not see any bugs or improvements needed in Okta Platform because it functions perfectly, and I have not faced any issues with Okta Platform in my career.

View full review »

Okta Platform can be improved by enhancing the mobile application because sometimes it has issues. Specifically, sometimes the OTP is not received for the mobile application.

View full review »

I have not encountered any negative points for this product.

For log monitoring, after a certain period of time, logs are deleted, such as after three months, and you have to configure it using a separate or external SIEM connector, such as Splunk or Cortex XSOAR, because after 90 days, the logs will be deleted, so we have to take an export manually or add one external log monitoring solution.

If the organization is big, I can say Okta Platform is affordable; however, for small-scale industries, I would not recommend it, but for medium and enterprise organizations, it is good.

View full review »

The only improvement point I would suggest for Okta Platform is that it needs to redesign the feature request system because there are many important features that are not taken into consideration.

I do not want to go into specific details, but you can visit Okta Ideas and see many ideas that have been shared. Many of them are prioritized, but the fact that a user wants it or that a metric exists does not help. Okta Platform needs to redesign or repurpose the entire concept of how it wants to handle feature requests.

View full review »

Okta Customer Identity is continuously improving its solution. Since we started using it in 2019, we have observed numerous enhancements to increase security.

View full review »

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

View full review »

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. View full review »

It would be great if there were a way to save even my social media passwords and other passwords through Okta Platform and single sign-on through Okta Platform in the future. I do not think they have this capability just yet.

View full review »

The drawback of this solution is that in our shops, many staff members sometimes have to be borrowed from one shop to another and the solution does not really support having multiple roles. The user experience we would like to have when a person works in shop A which pays their salary is that they should have access to pretty much everything. Maybe you have somebody who is a manager in that shop A, he should be able to order new wear, he should be able to change the pricing, he should be able to empty the cash registry, and ship it to the bank. But when for instance, in COVID, people had to fill in for people in shops where a lot of people were sick, then they had to actually use user accounts of people that work in shop B. If you were employed in shop A, you could not work in shop B without borrowing somebody else's user ID and password. Which is really bad. We haven't been able to work around that and Okta Workforce Identity does not have a solution for it.

We are now piloting their identity governance solution. Obviously, it's easy to give somebody access, give them an account, and give them roles, but it's hard to maintain that. For example, if you moved from, say working in a shop to working in a warehouse. But why do you still have all this shop access? The solution has until now not had anything to really support the process of taking away access. But now we are in a better release program of Okta's identity governance solution. Although it's very basic, the solution has started on a journey, but identity governance is something that Okta Workforce Identity really needs to improve.

The ability or the options in the solution for changing the look and feel are not good enough because in our partner portal, essentially what they have is an ugly admin interface. The admin interface is good enough for us technical people because that's all we need. We work with the product and we're able to see the data but when it comes to presenting the service portal, Okta Workforce Identity does not have any capabilities really for making it look pretty. 

To add branding and different graphical user interface elements than Okta basic for essentially delegated admin for the business-to-business portal is horrifying because you're essentially using the tech admin. The only option we had and used, was to take the tech admin console and strip it. so that a vendor that has some goods that are sold in the shops, when they want to add a user on their side, say a driver or a packer on their side who should know how much they've packed in a truck to come to our warehouse, then the user interface that this vendor is using, these functional people will then have to use an extremely basic user interface.

View full review »

There is a need for Okta to provide an end-to-end solution without needing a separate product like Zscaler for multifactor authentication. Additionally, Okta should enhance its endpoint defensive capabilities, as we currently use BeyondTrust for Elevator Access Management.

View full review »

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.

View full review »

There is room for Okta Customer Identity to improve by increasing the reliability for the server end, creating more directories, and focusing on internal users rather than external or contract-based ones. Additionally, extending idle session times from ten milliseconds to at least forty-five seconds would be beneficial. It is also suggested that patches be applied annually rather than quarterly.

View full review »

There are areas for improvement. One thing that seems odd to me is the lack of a built-in way to export all user data. They have a solution available on GitHub that they basically endorse, and it's developed internally, but for some reason, it's not integrated into their product. So, that's a peculiar aspect.

Instead, the support says they don't offer it but provide an alternative solution that we have to manage separately. So, it's a situation where they don't want to include it in their product, but they offer assistance outside of it? It's unclear what kind of support you would need for it. It just works.

Another area of improvement is scalability.

View full review »

I would appreciate it if Okta Workforce Identity becomes more user-friendly. Its API technology is complicated. Certain applications may pose challenges in terms of integration, especially when they require IDP technologies that aren't easily codable. While I can't provide specific examples, some applications may not integrate with Okta Workforce Identity. 

View full review »

If Okta Workforce Identity has a strong integration with other OEM solutions and can leverage intelligence from those OEMs to enable automatic restricted access for users, it would be highly appreciated. For instance, if it can integrate with DLP and EDR solutions, and if the DLP detects suspicious user activities, it should automatically restrict access to sensitive applications or prompt for multi factor authentication.

View full review »

The product is expensive compared to other tools.

View full review »

The only area of concern in the solution stems from the fact that my company needs some help regarding the setup phase from a partner.

View full review »

Currently, it has two-factor authentication. In addition to biometrics, it should offer three-factor authentication. Also, the training is too costly. Okta could reduce the training cost to make it easier.

View full review »

We faced a bit of an issue integrating the product with some applications. The integration process takes a bit longer than we would want it to.

View full review »

It's not compatible with on-premises installations, unless you host it as a SaaS. We were not able to do that. For example, imagine a scenario where the cloud is not available. Then, Okta will not work for you. That use case will readily fail because it doesn't have an on-premises installation that you can use to authenticate or provide identity and access management. If you have a purely on-premises solution that is not connected to the internet, then this will not work. This is one area that can be improved.

I would also like to see more intelligent analysis of the identity and access management from Okta.

View full review »

We had some implementation issues.

View full review »

I use the tool at a low level, so it does what I need it to do for me.

The product does not offer enough integration capabilities. I want the tool to provide more integration capabilities in the future.

View full review »

An area for potential improvement in Okta lies in the absence of a dedicated feature for backing up the configuration of our tenants. It is challenging to obtain a comprehensive backup. We have to manually document all the configurations. They could provide a built-in tool for creating backups mitigating potential issues or crises.

View full review »

The solution's user interface needs to be improved and made easy. It has a lot of repetitive things. The solution should have a single pane of interface for admins.

View full review »

The stability could be better.

View full review »

A room for improvement in Okta Workforce Identity is its price. It could be cheaper. The biggest benefit of the solution is that everything works securely without extra steps, so you're saving on your workforce's time and effort because your applications work smoothly and securely, but you'd need to pay some amount of money for that.

Another area that could be improved, though not necessarily regarding Okta Workforce Identity, is the SSO applications because so many of the source applications charge extra money to put the SSO to work, which means you have to buy a more expensive license. Nowadays, SSO is a mainstream functionality and it should be out-of-the-box in those applications because it's so easy to set up.

View full review »

Okta Workforce Identity could improve provisioning it can be made simpler.

They are implementing in one of the newer releases certification, attestation, and some role-mining abilities, but I don't know how far along that's going to be. That's a statement that they said they are going to have in the future.

View full review »

The high cost of the product is an area of concern where improvements are required.

View full review »

I'm not sure what areas need improvement. They are at the top in terms of identity management. I can't find any shortcomings. 

We don't need any additional features as it covers more than our needs. It's a massive tool. 

The solution is very expensive.

View full review »

I've been pleased with its capabilities overall. 

Support could be a bit faster.

View full review »

What I'd like to see improved in Okta Customer Identity is the process of exporting users. Currently, it lacks this feature, and you have to use a third-party tool to export users from the group. Exporting users should be very easy, though I did notice that Okta Customer Identity is being upgraded from time to time, and I've been seeing much improvement in it compared to the previous years.

View full review »

We are facing one issue with Cypress test cases. Whenever I write Cypress test cases, we encounter problems with logging in through Okta. There is no proper documentation on integrating test cases with Okta, and this issue is troubling whenever I try to implement it.

View full review »

We faced some challenges during the Okta Identity Workforce deployment. Integrating with AWS and other cloud services posed some limitations with federated options. For instance, features like automatic user addition from AWS to the tool were missing, requiring manual intervention. The API is limited compared to the manual configuration possible through the UI.

I think Okta Workforce Identity could improve by making its API more robust, ensuring that all UI capabilities are exposed in the API. This is particularly important for integrating with other applications, such as AWS and other cloud providers.

View full review »

Okta has a limitation with directory integrations. If you have multiple Active Directory integrations, the user distinguished name (DN) and the manager DN don't get imported properly into the Okta user profile. It has a property of Get AD user's property, but that has limitations when writing an expression language to import changes or updates to user DNs or manager DNs from AD, especially if you have AD master users.

Also, Okta doesn't have a partial push. It pushes down the full profile schema for lifecycle management or provisioning. Even if only one attribute gets updated, even though it is unmapped, it can override other values in the downstream application by nullifying the query. That's the biggest flaw in my experience.

The product releases a lot of brand-new features within the quarterly releases.

View full review »

Okta has a limitation with directory integrations. If you have multiple Active Directory integrations, the user distinguished name (DN) and the manager DN don't get imported properly into the Okta user profile. It has a property of Get AD user's property, but that has limitations when writing an expression language to import changes or updates to user DNs or manager DNs from AD, especially if you have AD master users.

Also, Okta doesn't have a partial push. It pushes down the full profile schema for lifecycle management or provisioning. Even if only one attribute gets updated, even though it is unmapped, it can override other values in the downstream application by nullifying the query. That's the biggest flaw in my experience.

The product releases a lot of brand-new features within the quarterly releases. There's a feature roadmap for Okta CIM, and most of it is coming in with a lot of users or the customer side.  

View full review »

The product must be provided for free. We cannot substantiate the cost with the features provided by the tool. Microsoft provides similar features for free. I don’t see any extra features in Okta.

View full review »

They should focus on providing top-notch team access management to companies.

View full review »

The error logging could be improved. Okta doesn't provide enough details when you are troubleshooting an issue. It's often difficult to fix it from our end, so we always need additional support from Okta.

View full review »

There is an access request system that is very limited access to the systems available for end-users. The access request should improve in Okta Customer Identity.

View full review »

The solution works well. I can't speak to any areas of improvement. 

In the future, we'd like to see the product implement more security features, like, for example, zero-trust.

View full review »

The cost per user for this solution is really high and could be reduced. 

We have experienced some challenges in integrating this solution with Scope and Cognito. 

View full review »

The initial setup could be easier to do.

View full review »

We've not come across anything missing. It's under continual improvement. It is actually very good. We've not had any problems with Okta. I'd have to think hard to find anything that was badly implemented.

View full review »

Okta Workforce Identity could improve the way passwords are reset and how it interfaces with Microsoft.

Okta Workforce Identity acquired Auth0 and they should have a solution with integration between the two.

View full review »

We experienced some technical glitches that need to be resolved. 

I go into further detail below in the 'stability' section.

View full review »

There are many things that Okta has to improve on. I understand that Okta has a lot of apps, like any other provider, e.g. Microsoft apps, IDP apps, or cloud identity apps.

The problem with Okta is that they create the app and they never update. In this fast-paced industry where versions keep getting updated, Okta is really slow at times.

None of the Okta applications that they create, for example, in my case: I have used the cloud identity of Microsoft apps and now I'm using the off tabs. What I found is none of the single Okta apps that we have worked and did not create an issue. They are not fully mature. So it's that aspect that can be improved, which Okta is investigating. Their application support and not having updates for those applications also need to be improved. These are the things that surprised me and I was not able to understand from Okta.

Okta's customer support should be improved.

Okta should work with certain providers, e.g. the Google cloud, the AWS cloud, the Microsoft cloud, and they should evaluate the integration point because what happens is if your organization has SSO which relies on Okta, all of these three clouds and the Okta app are far from perfect. You are not able to get the right setup based on how your security is trying to define it vs what the application can support. You'll end up using the default interface Okta provides with those apps.

I understand Okta could say that if they shouldn't worry about it because if AWS wanted to support Okta, then AWS should be the one providing us the app and support, but Okta should try to understand the users, do surveys from the different automation using Okta, and use different apps because those apps are very critical. They are far from perfect, so Okta has the worst implementation.

View full review »

There are sometimes issues with the voice authentication methods when users receive calls and they're not able to get the verification codes. That needs to be improved. A troubleshooting dashboard would be helpful in terms of pinpointing issues as opposed to running a search query switch. 

View full review »

The product's connector framework needs improvement. There should be automated aggregation and complete classification processes included in it.

View full review »

The solution’s policies are difficult to understand due to the policy methods. They use authentication. The solution’s workflow is also difficult and not very active. They need to have proper documentation on it. In the next release, I would like to see the workflows being more digestible.

View full review »

My concern is that I live in an emerging country. In my country, there's a lot of stealing of mobile phones, and mobile phones are the authentication device through the Okta application. If someone should steal my mobile phone, which is very common in my country, he or she might have access to my company account. That's my concern. I don't know if there's another way of doing the authentification. Maybe if you can have a dedicated device for using Okta, it might be better, or if there were other options for authentication.

I would like to have a version of this software for personal use, for my personal accounts. 

View full review »

Okta Workforce Identity can improve by having more features in governance.

View full review »

This user integration with the Okta integration network could be simplified.

View full review »

The only aspect in which it can be improved is that the interface could be cleaner. I found this even when I was trying to do my certification exam because the certification is hands-on. You find yourself fumbling around a little bit to find simple things. This happens even when you start to get familiar with the product.

View full review »

I do not see much room for improvement. I have not encountered any issues with the solution, though it may be worth checking this with the technical team involved in its implementation. 

This said, it is scalable for midsize companies and infrastructure but, owing to the regulations we have in place in Egypt, not every enterprise-sized company. This means the solution did not comply with everything in the financial sector, such as with our central bank. As such, one who is working in the financial sector must resort to another solution or, at the least, another one in addition to Okta Workforce Identity. 

The solution should have greater on-premises availability, not just cloud and more package customization in its processing. 

View full review »

It's my personal opinion, but it was a classic UI and now the UI is different. I was used to the old UI and when I moved from the old to new, I found it a bit difficult.

View full review »

Okta can consider to become also a password vaulting manager. We also didn't find an option to setup access to web services that require second factor authentication. Also it's hard to figure out which license is responsible for which features and how are they correlated.

View full review »

The solution needs to improve its own marketing. It's a great solution, however, most people don't know what it does. It should be first in line for onboarding employees. 

The solution should continue to work to improve its interface and make it more user-friendly.

The initial setup can be complex at first.

View full review »

All of the governance functionality and privileged account management could be improved.

View full review »

The lifecycle management part can be improved. It should also have identity governance and the ability to choose a specific factor authentication at the application level.

Its licensing and pricing can also be improved.

View full review »

There are some issues with the interface that can be improved.

View full review »

The guest user access could be improved. How do we authenticate people that aren't in our Active Directory?

In the next release, I would like to see passwordless access.

View full review »

It is not very interesting from a marketing perspective. For this, you can use open source solutions to reflect different groups.

View full review »

The pricing could be improved. Right now, it's a bit expensive. They should work to make it more affordable.

In general, the solution isn't really missing any features. It's rather complete. I can't recall anything that would need to be added into future updates.

View full review »

API Securities Solution

View full review »

The integration with third-party tools needs to be improved. Mainly, the open-source APIs for Splunk would be helpful, as that is where they aggregate most of the data. If this process can be streamlined then it will definitely help.

View full review »

They also have single sign-on (SSO). When we bought Okta Workforce Identity a year and a half ago, I was also looking at SSO, but not much documentation was available for SSO. The documentation for SSO should be a little more robust for somebody who is implementing it for the first time. 

View full review »

With the device applications, when you are checking the logs, you can't hide the device and that's a feature that's missing. I'd like to see MDM source added. 

View full review »

It would be pricing, which is a tough one because it goes against Microsoft. A lot of companies say they're a Microsoft partner, and they get all their software for free.

Okta is like a luxury product, and it's not the most affordable one. I would say if they could work on pricing, it would help. Other than that, they've done great strides in developing a product that is really good. The companies that do see the value tend to invest in it.

View full review »

I would like to see the provisioning simplified. When it comes to certain tasks, such as where it is activated on-premises, Azure AD is simpler than Okta.

SSO functionality needs better client support.

View full review »

• Passwordless authentication. 
• Integration with the user provisioning infrastructure to track all entitlement changes; simplify the modeling of the role and access definitions at every stage of the user life cycle.  
• Automation of the entire entitlement and role review process, in alignment with business needs and requirements as stated by business leaders and managers. 
• Oversight in the form of dashboards reconciling and centralizing information for immediate insight into the status of access reviews and certification processes.

View full review »

Command line access

Reporting

View full review »

This solution would be improved by adding more biometrics features. One example is Cyberside Biometrics.

The technical support is good but needs to improve in their response time.

In the next release, I would like to see biometrics, multi-factor authentication, and to rely more on the mobile or something different on CyberSide.

View full review »

The solution lacks an on-premises deployment model so it can't offer a hybrid solution. It would be ideal if clients had options that weren't just cloud-based.

View full review »

Better multi-factor authentication integration and support, it's around v2.0 and will need a 3.0 release for maturity.

View full review »

On the admin side, we can create our own passwords instead of generating one, which is usually difficult to explain to a user. Otherwise, the application is pretty awesome.

View full review »

RESTful Web Service calls and their response seem a bit slow.

View full review »

Maybe the interface could use some work but, for the most part, the tool is pretty cool.

View full review »

We still had to write several internal programs/scripts to complete the user-provisioning process. Okta does not have the ability to provision mailbox accounts for on-premise Exchange or in a hybrid O365 environment. The Group Push function from Okta to AD did not work reliably in our environment.

View full review »

UD attribute mapping, Okta group rules, and dynamic usage could use improvement. More in-depth functionality and features to integrate with RADIUS solutions.

View full review »

The Identity Management part can be improved a bit.

View full review »

I would like to see further integrations with applications and services such as Office 365.

View full review »

• A couple of improvements with the lifecycle management that will help companies that don't have an HRIS system to help manage contractors and contingent workers would be to add ways to disable their accounts once a certain time point is designated.
• Also, an improvement to the reporting capabilities can make running reports easier and more customizable.

View full review »

They could provide collaboration with Microsoft for conditional access and other features. They could work on reducing bugs as well.

View full review »

The solution's pricing needs improvement.

View full review »

In some setup cases, there are issues with attributes not going in properly. We've also had some problems with the firewall causing the data center to slow down.

View full review »

Okta could improve by making their learning materials more user-friendly. They could also enhance the flexibility of their MFA feature, allowing clients to implement preferred MFA methods without restrictions.

View full review »