
Okta Platform
Automated onboarding and RBAC have reduced manual work but costs and local hosting still need improvement
What is our primary use case?
My main use case for Okta Platform is not only for MFA purposes. All our applications are integrated with Okta Platform for SSO. Apart from that, we use automation for the joiner, mover, and leaver process.
Okta Platform handles our joiner, mover, and leaver process in a fully automated way. We have an HR system called SAP SuccessFactors. HR enters their data in SAP SuccessFactors, and Okta Platform picks up those details. Based on the joining date of the users, it creates a user profile in Okta Platform, pushes it to Active Directory, and creates a ServiceNow task for the helpdesk team to prepare a laptop or whatever assets are required. It also sends an email to the joiner's personal email address with his credentials for the company.
Something unique to our organization is that, based on the application assignment, we use RBAC to assign applications to the users, rather than doing everything manually. It is all completely automated using the RBAC system and security group systems.
We use Okta Platform only at the application level. We have not integrated it with containerization in general, but we are using it in Azure for containerization, which is very helpful and more secure. We have a multi-cloud environment, so in one of the clouds, Azure, we use Okta Platform for containerization and everything.
Okta Platform does not protect non-human identities in our environment, since we have eliminated Okta Platform from those accounts. We are not integrating Okta Platform with service accounts.
Our workloads are hosted across multiple clouds. As I mentioned, we have a multi-cloud environment, so all of our clouds are being used, and even on-premises.
How has it helped my organization?
Okta Platform has positively impacted our organization through user assignment to applications based on RBAC policies. As I mentioned, this is a more advanced and better feature, because Okta Platform applies RBAC policies when assigning users based on their groups and roles. This is one of the best features I found, and it helps our company because it is completely automated. Once a user has a role assigned, Okta Platform automatically assigns the groups and the applications.
Okta Platform reduces manual work and saves us time. The automation stops manual work, and it saves a lot of time. The process is very accurate and resolves things through defined tasks, one, two, three, and four. A human can err, but in automation, human error does not occur. All the workflow is perfectly managed. Security-wise, it is more secure because of MFA, and I found Okta Platform more secure compared to other solutions.
I have not noticed any measurable security or operational improvements in our cloud-based workloads since implementing Okta Platform.
What is most valuable?
Automation is one of the best features Okta Platform offers. I especially like its automation work.
The automation feature I find most valuable is that the whole process is very interesting and helps us make things faster. I cannot name anything in particular, because I find the whole Okta Platform automation process completely good.
I would like to add that Okta Platform supports SAML and everything else we need. For SSO or MFA purposes, it is mandatory for us to use SSO for all our integrations, and Okta Platform is more reliable. Security-wise, Okta Platform is more trustable.
What needs improvement?
Okta Platform can be improved in one small way, although I have not been in a situation where I found any kind of limitation with it. There is one small thing I see: Okta Platform does not support uploading metadata. We have to extract the URL when we are integrating any application. If Okta Platform can fix that, that will be good.
The reason I gave Okta Platform a seven out of 10 is that, cost-wise, I find it a bit expensive compared with other solutions. That is the main cause, because every company is concerned about the budget and everything. Apart from that, I am working in the Saudi region, and Okta Platform does not have a Saudi region. It is hosted somewhere in Germany or elsewhere. It would be much better if Okta Platform were in the Saudi region. That is why I gave it a seven.
For how long have I used the solution?
I have been using Okta Platform for three years, since joining this company.
What do I think about the stability of the solution?
Okta Platform is stable. So far, I have never faced any issues.
Which solution did I use previously and why did I switch?
I have used Microsoft Entra ID previously, though not in my current company. In my current company, I am using Okta Platform.
What was our ROI?
I have seen a return on investment. Time is saved, and fewer resources are required because Okta Platform is more user-friendly. So I have seen a small return on investment, and security-wise as well.
What's my experience with pricing, setup cost, and licensing?
My experience with pricing, setup cost, and licensing is that, as I mentioned, Okta Platform is a bit expensive compared to other products. That applies to pricing.
Which other solutions did I evaluate?
I have evaluated Microsoft Entra ID. It has some limitations compared to Okta Platform, which is more user-friendly and everything. Okta Platform is much better.
What other advice do I have?
On a scale of one to 10, I would rate Okta Platform overall as a seven.
As for governance and security, as I mentioned in my rating explanation, Okta Platform is not in the Saudi region. There are many governance requirements, and data has to be in the Saudi region. Apart from that, it is more secure, and I can go ahead with it.
Okta Platform's AI capabilities are good, and I am very satisfied. We have a team that works together and uses the platform, and they are very satisfied.
Okta Platform is deployed as a public cloud. We use Okta Platform as a SaaS service for our deployment.
Centralized access has improved governance and secures users with single sign-on and MFA
What is our primary use case?
My main use case for Okta Platform is using various products in Okta, including governance, OAuth migrations, device trust, single sign-on, MFA, and day-to-day operation tasks. I provide users with access based on least privilege principles, configure applications, create policies and rules, and upgrade the AD agent and RADIUS agent according to requirements.
These tasks have made the biggest difference in my day-to-day work because I have to do them every day. They have been the biggest achievement in my career and my growth. I learn something new every day in Okta Platform.
I also share knowledge with my team members and provide guidance and support to them.
Okta Platform helps secure access to cloud infrastructure, APIs, containerized workloads, and AI/GenAI services in my architecture. For API access, we use OAuth client credentials, which provide least privilege principles, so access is more secure. I use OAuth this way because the token is short-lived.
Okta Platform does protect non-human identities in my environment, such as service accounts, machine-to-machine access, and AI agents. We provide non-human identities as well, and Okta Platform protects the systems through OAuth client credentials and provides scope and token policies. We use the OAuth 2.0 client credential for this.
How has it helped my organization?
Okta Platform has impacted my organization positively because it has brought many changes, such as improving the security of the applications and providing the least privilege principle for every user, so the right person has the right level of access. I think it has had a positive impact.
I see fewer access issues with users because of the stronger access controls. Sometimes users are not able to access the applications on the service provider side, even though the authentication is happening in Okta Platform. This type of issue arises when the configuration is mismatched on the application side, and we spend less time on it.
I don't notice any measurable security or operational improvements in our cloud-based workloads since implementing Okta Platform.
What is most valuable?
The best features Okta Platform offers are security and single sign-on, so users do not have to apply multiple passwords to access multiple applications. I think this is the best feature of Okta Platform.
SSO and the security controls in Okta Platform have changed the experience for users and my admin team. It takes less time to access any application, and it is user-friendly, so users do not have to remember many passwords to access the applications. I think it is easy, and it is also a centralized system to manage every application in one place. There are fewer password-related issues.
What needs improvement?
Okta Platform can be improved by providing logs to the service provider. The authentication is fine, and the vendor and the Okta team work together to find a solution. We check all the metadata in both the SP and the identity provider, and we solve the issue that way.
I would like to add that there should be clear documentation between Okta Platform and the application so that the problem does not come up in the future.
For how long have I used the solution?
I have been using Okta Platform for five years.
What do I think about the stability of the solution?
Okta Platform is stable.
What do I think about the scalability of the solution?
The scalability of Okta Platform comes from the Okta vendor. According to our requirements, they can provide the scalability.
How are customer service and support?
I think the customer support is nice, and they give a prompt reply.
On a scale of one to 10, I rate the customer support a seven.
What other advice do I have?
On a scale of one to 10, I rate Okta Platform overall an eight.
I rate it an eight because I think it is good to use as a centralized service system and it provides users access with no burden of passwords. It is easy to access everything in one single dashboard. Every application is more secure, and MFA is also configured. I think the right people will access the right application, and that is why I gave it an eight.
With the Okta Platform AI capabilities, we can do many things, such as providing access to users and creating groups. For security and governance, we have to think more about using the AI features in our day-to-day tasks, and we have to work more on that part. I'm working on how we can secure the applications and the access for users. I think a POC is needed for that.
I'm still doing the POC on this part to see how it works.
Okta Platform does not yet help us address specific industry or regulatory requirements, such as healthcare, financial services, or public sector requirements, in our cloud environment.
I suggest that others looking into using Okta Platform use it.
The main reasons I suggest it are single sign-on, security using MFA, and centralized access management. These are the options I suggest they use.
Centralized identity workflows have strengthened security and streamlined user provisioning
What is our primary use case?
Our main use case for Okta Platform is single sign-on, application integration, and provisioning.
Okta Platform fits into our day-to-day identity workflows as we help customers deliver their identity and access management use cases through Okta Platform capabilities such as multi-factor authentication, security policies, and automations.
For our customers, Okta Platform helps secure access to APIs through the authorization service, where you can manage and protect external calls and communications from different applications to your internal APIs. You can manage permissions, you can manage the claims, and you can manage what kind of resources the applications are requesting from your APIs. It does all of that while centralizing all the identity management in your identity provider solution.
We do protect access to some of our service accounts and API tokens by centralizing the authentication flow through Okta Platform and handling some specific exception scenarios with MFA.
There are specific regulatory requirements, since some of our customers are subject to those kinds of regulations. We help those customers with specific and customizable security policies such as password complexity, MFA lifetime, session lifetime, traceability, et cetera.
The AWS services that are integrated or secured through Okta Platform are mostly IAM and EC.
How has it helped my organization?
Okta Platform has positively impacted our organization. For all of our customers, the impact is really high regarding security. We help to reduce the risk of phishing attacks, social engineering, password hacks, and anything related to credential exposure. Our customers also see a really big impact from automation in the provisioning scenario. We help to automate everything related to user onboarding, user modifications, and user terminations.
In terms of reduced onboarding time and fewer support tickets, we help to reduce the number of days that a new employee in the company needs to have access to all the applications and permissions that he needs. We also help to reduce the final number of tickets that I must open regarding application requests.
We have noticed measurable improvements in our cloud-based workloads since implementing Okta Platform. Our customers are able to present some improvements in their cloud environments, at both the security and operational levels.
What is most valuable?
The best features Okta Platform offers are the security capabilities, including all the topics regarding security policies, zero trust, different kinds of multi-factor authentication, and integration possibilities such as YubiKeys, hardware tokens, software tokens, and step-by-step authentication. Everything is related to security.
The integration possibilities help our customers implement those security policies across their environments because they help secure advanced and complex use cases. Examples include different user typologies and different authentication scenarios such as external access, out-of-office access, remote access, and shared environments or shared resources. All of that is secured while maintaining a good user experience.
In addition to the features, we are also able to reduce IT costs and manual operations with all the automation capabilities. We can help both the user experience and the administrators' day-to-day work.
What needs improvement?
Okta Platform could be improved regarding some complex scenarios in user provisioning. For example, I would like to be able to write and read some specific attributes in different flows. I would also like to be able to customize in more detail those scenarios in which you want to provision different user profiles and different user attributes to the same applications with complex use cases.
I would not like to add anything more about the needed improvements.
For how long have I used the solution?
I have been using Okta Platform since 2020.
What do I think about the stability of the solution?
Okta Platform is stable.
Which solution did I use previously and why did I switch?
Most of our customers are not using any specific identity and access management tool, as they are relying on Google Workspace or Entra ID.
What was our ROI?
Most of our customers see a really fast ROI in metrics such as ticket reduction, IT operation reduction, manual operation reduction, and fewer manual errors, as well as a general improvement in security.
The percentage reduction in support tickets is, on average, about 30 to 40% when the product is mature.
What's my experience with pricing, setup cost, and licensing?
For some of our customers, we purchase Okta Platform through the AWS Marketplace, as we are a reseller and a partner. We deliver services and resell licenses, and we do sell the licenses through Amazon Web Services.
My experience with pricing, setup cost, and licensing is good so far for our customers, as we can segregate what the customer needs. If you have a specific requirement, you can buy a license only for the modules that cover it. You don't need to buy the whole product if you are not going to use it, so it's pretty well segmented.
Which other solutions did I evaluate?
Before choosing Okta Platform, we considered other options, and when we go to the market with Okta Platform, the main competitors are OneLogin and Ping Identity.
What other advice do I have?
I do not have anything else to add.
I would tell anyone researching Okta Platform on PeerSpot that I would rate it an eight out of 10.
I give Okta Platform an eight because it's the most solid authentication platform that exists in the market. It is also really good in terms of user provisioning and some governance capabilities, but it could be improved in some complex user governance and provisioning scenarios for big companies.
Okta Platform's AI capabilities for governance and security are doing well now with the agentic AI security capabilities. It's going in the right direction, but there are still some things to improve.
The accuracy and reliability of Okta Platform's AI capabilities output is consistent compared to other tools in the market.
Okta Platform is deployed entirely as a private cloud in our organization, and we also deliver it to different customers in different scenarios. Some of the customers have some on-premises parts that are integrated with Okta Platform, but most of the customers have public or private cloud.
We use Google Cloud Platform, Amazon Web Services, and Azure cloud capabilities as our cloud providers. They are also the cloud providers that host the workloads secured by Okta Platform in our environment. We have different customers for whom we implement Okta Platform, and we have been integrating it with all of these providers.
Quick, Effortless Work Access with Okta’s Chrome Extension
Streamlined tool access for teams and individuals
Okta simplifies identity access and microservice security
Okta Single Sign-On Makes Access Simple
Effortless SSO Access to the Rhombus Dashboard with OKTA
IT Administrator
Centralized access controls have simplified securing cloud workloads and non-human identities
What is our primary use case?
I have worked on all components of Okta Platform starting from Access Gateway to Identity Governance to Okta PAM solution to Okta Workflow. I have worked end-to-end on these components, including requirements gathering, drawing the architecture out, building it out, testing it, deploying to production, and hypercare. I deal with the end-to-end process independently.
For securing access to cloud infrastructure, Okta Platform helps by using an authorization server so we can utilize modern protocols such as SAML or OAuth to have those chains generated, client credential flow or authorization code flows to secure the application. When it comes to AI agents, we can onboard them to Okta Platform. We can run certification campaigns around these AI agents so that these agents are not over-privileged. We have MCP gateways which we can leverage to act as a gateway between the application and MCP gateway. We can secure which particular application or agent is allowed to call which particular MCP gateway and the tools inside it. That is how Okta Platform secures it on a high level.
Okta Platform can help to secure access to non-human identities in my environment, such as service accounts, machine-to-machine access, or AI agents.
Regarding use cases where Okta Platform helps protect non-human identities, when it comes to agent onboarding, that is what it does for non-human identities. It takes in the non-human identities in the form of agents. The XA protocol also plays a key role inside it. Currently, Okta Platform also has the OAuth OBO token which works in case of non-human identities. I have built POCs and also worked in some applications that consume it. I have experienced building solutions regarding non-human identities with Okta Platform.
Regarding the specific industry or regulatory requirements, currently the projects that I am working on include one in the healthcare industry and another in the entertainment industry. They are leaders in their respective industries. Okta Platform is being implemented there.
Regarding AWS services that are integrated or secured through Okta Platform, it is not direct. We are not securing Lambda directly from my current project. We are using Okta Platform to transform the logs to a SIEM platform using Lambda and AWS Gateway.
How has it helped my organization?
I have noticed measurable security and operational improvements in my cloud-based workloads since implementing Okta Platform. Previously when it was being handled by some other configuration logic or tool, it was not able to perform up to the mark. Sometimes the configuration was difficult for it to handle. With onboarding to Okta Platform, it became easier to handle those scenarios. The security rails and the logs around Okta Platform are very good. It has detailed information, so everything becomes easier with Okta Platform.
What is most valuable?
What I appreciate about Okta Platform is that it is currently moving towards agents. Agent Gateways are something that Okta Platform is moving forward with. Okta Platform has come up with an XA solution that is modernly used for agent communication and it is leading in the market. There are other technologies that are following, but Okta Platform is currently leading that space.
The key benefits that I have seen from using Okta Platform are that it is easy to configure. There are a lot of customizations that are available. When it comes to orchestration tools, using them we can do many use cases which might not be possible out of the box. It has a lot of flexibility towards it.
What needs improvement?
Okta Platform is moving towards AI, which is good, but that space is very new. Okta Platform can understand the use case better and move faster in that field because the AI agent has many gaps. The non-human identity part has many gaps which Okta Platform can fulfill.
Apart from the AI aspect, there are missing features in Okta Platform that I would like to see included in the future or enhanced. The MCP gateway onboarding for agents can be made smoother. Agents already have the capabilities to link with Okta Privilege Access for key management. If it could be made easier to map those out, it would be easier to adopt.
For how long have I used the solution?
I have been working with Okta Platform for three years.
What do I think about the stability of the solution?
Regarding the performance and scalability aspect of Okta Platform, it performs very well. It has a very good runtime. Okta Platform has committed to 99.99% uptime that it will be online. When it comes to Okta Workflow, when there are too many flows running at once, those get delayed. Sometimes some of the values in the workflows are not populated correctly. I have opened a ticket with Okta Platform regarding this. It is some system bugs that they cannot fix.
How are customer service and support?
On a scale of one to ten, where ten is the best, I would recommend the technical support of Okta Platform a solid 9.5. The response is very active. Even if the person who is assigned is not able to help, they take help from their subject matter experts of those products to help us out. The technical support of Okta Platform is very good.
Which solution did I use previously and why did I switch?
Apart from Okta Platform, I have worked with Auth0, which is a product of Okta itself. I have also worked with Ping and ForgeRock.
How was the initial setup?
Regarding the deployment aspect, it is not that difficult with Okta Platform. The reason being Okta Platform is a cloud solution and it is not on-premises. Because it is on the cloud, it is very easy to deploy it.
What was our ROI?
I have not seen any ROI with Okta Platform.
What's my experience with pricing, setup cost, and licensing?
My experience with the pricing, setup costs, and licensing part of Okta Platform is that from the licensing perspective, from what I am aware, it is competitive. Some of the tools are more expensive and the pricing is okay. It is not too great, it is not too bad from what I know.
Which other solutions did I evaluate?
The key differences, both pros and cons of Okta Platform in comparison to Ping technologies or ForgeRock that I used are that Ping has more customizable options in regard to journeys. Okta Platform does not provide those customizable journeys. Ping has more towards it. Ping can do identity verification, which Okta Platform lacks. Okta Platform cannot do ID verification built-in and they have to rely on other third-party vendors such as Persona to do identity verification. There are some areas which Okta Platform can still improve with respect to identity verification.
What other advice do I have?
I work with Okta Platform as an AWS version. I have worked on the AWS hosted version of it, not Azure.
For the procurement of Okta Platform, I work for the client and they purchased it from Okta Platform. The way they were reached out is that they have been using Okta Platform for almost five to six years now. They have a strong relationship with Okta Platform and that is how they got it.
Given my varied experience with Okta Platform technologies, one of the key areas that organizations lack currently is security. Many organizations take it lightly because it does not affect their features in a way. But security is one of the key factors. Okta Platform is a better approach to implementing Identity Access Management. As they do not have to rely on versioning, you can directly integrate with Okta Platform and it will help you manage the users, groups, and everything at a central place. Because it is being managed by a separate team, there are less chances of having bugs and it is easier to maintain those.