I use Okta Platform as an administrator to set up new SAML and SSO apps. We also use the governance module as well. We also use the automation functions with workflows. We use it mainly as our main identity platform. I have been using it at all my past companies.
Okta Platform
Okta, IncExternal reviews
1,210 reviews
from
and
External reviews are not included in the AWS star rating for the product.
Unified identities have simplified secure access management and improved compliance
What is our primary use case?
What is most valuable?
What I appreciate about Okta Platform is that it is most of the time a very good no-code platform. It allows us to set up new SSO integrations quite easily, even if the app doesn't really support SSO natively. It is pretty easy to configure on Okta Platform.
Okta Platform has impacted my organization positively by providing convenience, first of all. There are no more different passwords for many different apps, since SSO doesn't really require password storing. Security has also improved because we eliminate a very big weak point that passwords represent. Additionally, we maintain control to ensure we only give access to the necessary apps to the necessary people.
What needs improvement?
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.
For how long have I used the solution?
I have been working with Okta Platform for more than five years at this point.
What do I think about the stability of the solution?
Regarding the Okta Platform, it has been stable. We do have different cells in different countries since we work on a hub-spoke model. On our EMEA cell, it has been quite stable. We did have some problems before on our US cells in these past few months, but nothing too serious. Most of the time, issues happen after hours on the US market. On our EMEA side, there have been no issues in these past few months.
What do I think about the scalability of the solution?
I find Okta Platform scalable and have not hit any limitations or scalability issues with it. We do have a good contract with our vendor that allows us to set up new users at any time and they basically review the contract a year after if we need to have more users. We really don't have scalability issues.
How are customer service and support?
If I would evaluate customer service and technical support of Okta Platform from one to ten, I would say a very good nine. We do have a very good relationship with our customer support representative, customer support manager in this case, or CSM. We also have a dedicated Okta Platform tech that we go to with more high-level questions. The level one support with the normal ticketing system from Okta Platform works pretty well most of the time. I never faced any issues, and if we need to escalate it for more complex issues, we can go to our dedicated tech manager support or our customer success manager and they are pretty quick to respond.
Which solution did I use previously and why did I switch?
I have mainly used Okta Platform. I did use a bit of Ping Identity, but it was so long ago that I really don't remember a lot of the platform at this point.
How was the initial setup?
When it comes to the deployment process of the initial setup with Okta Platform, we definitely faced some complexities, especially related to the way users authenticate. Sometimes authentication policies are a bit buggy in the sense that sometimes they really don't detect the correct browser that the user is using or there are issues related to the location of the user. The part of security authentication sometimes really doesn't work as well as it could. We did experience some problems in that sense.
What about the implementation team?
The deployment of Okta Platform was implemented fully in-house.
Which other solutions did I evaluate?
We did look at other solutions as well, such as One Identity and Ping Identity, before choosing Okta Platform. We decided to go with Okta Platform since it was the more complete option on the market at the time, with all the necessary functions that we had, especially related to authentication policies. It also had a better catalog of pre-built apps as well, so it was a bit more simple. We also started looking a few years ago to maybe replace Okta Platform with Entra ID, because we also did have Azure products, but we decided to keep Okta Platform because Okta Platform still has much more documentation and much more time in the market. Their solution is a bit better in that sense.
What other advice do I have?
My best piece of advice for others who are looking into implementing Okta Platform would be related to the knowledge base. I would make sure people read through the main knowledge base from Okta Platform, so the main steps of integrations. One of the good advantages of Okta Platform is that most applications and authentication are all the same, since it uses base protocols such as SAML or OIDC. If you are able to build one, the other ones are pretty easy to build. Go through the knowledge base that Okta Platform has, which is very rich for understanding if it is actually a good solution for your problems. If it is, Okta Platform would be a good solution to use.
The AWS services that are integrated or secured through Okta Platform mainly include AWS Cloud directly for cloud computing purposes.
Okta Platform does protect non-human identities in our environments, such as service accounts. We have the perspective that we can monitor the access, so who actually accesses the accounts and who is the manager of those accounts. We maintain password rotation and password policies for those types of accounts, which are different from a normal user account. Okta Platform helps us with that.
Related to the financial market, Okta Platform helps our company address specific regulatory requirements because we need to be SOX compliant, since we are a public traded company. Okta Platform helped us with being SOX compliant.
I have noticed measurable security and operational improvements in our cloud-based workloads since implementing Okta Platform. One of the main ones is access to AWS cloud environments. Thanks to Okta Platform, we can set up push groups to the AWS IAM module. We can actually give access to specific AWS spaces to specific teams in this case. For example, if we have a cloud team that works on a specific region, we can give access to an Okta Platform group to that specific team, and they will have access to that AWS cloud space. We have a lot of that, and it helped us a lot.
I would rate this review a nine overall.
Robust, Reliable SSO with Endless Okta Integrations
What do you like best about the product?
Okta is very robust and includes endless integrations. Any tool today that respects itself supports SSO connectivity with Okta. It allows a lot of connections, management of users and access, the UI is easy and it's extremely reliable.
What do you dislike about the product?
As an admin of several tools (but not a full admin of Okta) - I sometimes require the help of a full admin (usually someone from IT) to support the more complex integrations or errors. You have to be extremely technical to be able to administrate Okta.
What problems is the product solving and how is that benefiting you?
It helps secure employees’ connections to the tools they use, giving us strong control and a high level of security. It’s also useful for anything involving more complex permissions, automations, and user provisioning.
Big Performance, Seamless Integrations, and a Friendly UI
What do you like best about the product?
I love that the performance and the integrations are so big and about the UI is so friendly.
What do you dislike about the product?
I feel that is necessary to expand their integrations in Mexico because so many applications in Mexico are not using OKTA their SSO
What problems is the product solving and how is that benefiting you?
currently I did not present problems
Centralized access has streamlined secure authentication and accelerated cloud integrations
What is our primary use case?
The main use cases for Okta Platform are authorization and authentication. From the SSO, I can understand if the person logging in is authorized to redirect to the correct URL. The second use case involves JWT token generation, which includes all the information about the user, such as SSO Gmail and other information about the permissions that person has. When I get that JWT from the code, I can access more user information and authenticate for other services using 3LO.
I haven't handled 2LO, which refers to service-to-service authentication. Okta Platform provides protection for non-human identities in our environment through 2LO, enabling services to call databases or APIs without human involvement, which allows M2M access. For instance, if an MCP gateway needs to access tools without human interaction, Okta Platform offers this option.
One example of how Okta Platform helps secure access to cloud infrastructure is through the AWS service called Bedrock Agent Core, where I can directly integrate with Okta Platform. AWS provides an option for this integration, allowing us to connect our API after authentication.
What is most valuable?
The best features of Okta Platform are fast authentication and smooth integration with AD groups. AD groups control the permissions people have in our enterprise through our in-house software called CIAM. This integration with Okta Platform is very smooth, the authentication is fast and reliable, and I can retrieve the JWT token, 3LO, and 2LO.
The benefit of using Okta Platform is that for authentication-related things, I don't have to consider build versus buy since this product is reliable for the majority of our applications, significantly reducing our time to develop authentication-related features.
I have seen an improvement in our cloud-based workloads since implementing Okta Platform, which provides faster connections than traditional applications. Previously, I used Redis cached and session-based systems, but through Okta Platform, I work with JWTs for a faster experience.
What needs improvement?
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.
For how long have I used the solution?
As a developer, I have been using Okta Platform for around four months. As an employee doing SSO and all, it has been more than a year, so it is around one year as an employee and four to five months as a developer.
What do I think about the stability of the solution?
Okta Platform is stable, as I haven't faced any authentication issues in the year I have been using it. It works smoothly even with hundreds of applications and hasn't encountered production issues.
How are customer service and support?
The customer service and technical support for Okta Platform at the enterprise level are good, as I primarily rely on consultants who manage these interactions effectively.
Which solution did I use previously and why did I switch?
Before choosing Okta Platform, I evaluated other solutions like AWS Cognito. The main advantages of Okta Platform are its JWT option, which is passwordless, and its good integration with Vault and Terraform, while Cognito lacks such features, leading to slower session-based processes.
From the start in our application, I have been using Okta Platform and still maintain some session-based systems in the cache layer.
How was the initial setup?
I was not involved in the initial setup of Okta Platform. After the setup was completed, I have been using it for over a year, so I cannot comment on any challenges faced during the initial setup.
What about the implementation team?
I employed consultants from other organizations to assist with the deployment of Okta Platform, which has been effective.
What was our ROI?
Financially, I cannot provide specific data points for the return on investment with Okta Platform. However, technically, managing these aspects myself would incur server costs for generating JWT tokens and reliability improvements through the OAuth mechanism provided by Okta Platform reduce my technical load.
Which other solutions did I evaluate?
My company purchases Okta Platform through direct Okta, not through the AWS Marketplace. It is the Okta Platform Enterprise SaaS offering.
What other advice do I have?
My advice for companies considering Okta Platform is to make it more platform-agnostic. While Cognito is limited to AWS, Okta Platform's flexibility allows us to avoid being restricted to a single cloud provider. I would rate this review as a 9 out of 10.
Which deployment model are you using for this solution?
On-premises
If public cloud, private cloud, or hybrid cloud, which cloud provider do you use?
Amazon Web Services (AWS)
Everything in One Place for Quick, Easy Access
What do you like best about the product?
Everything is in one place, which makes the app system quick and easy. I can access all of our information in a single area without having to search around.
What do you dislike about the product?
I don’t have any downstream experience with this product yet. The main issue so far is how often we’re asked to log into the system just to access Okta.
What problems is the product solving and how is that benefiting you?
Okta has been a great tool for our company and has been working very well. We haven’t had any issues so far, or any need to switch to another tool. It’s also easy to search for other apps and add them to our main page for quick access.
Okta Is Easy to Use Once Set Up
What do you like best about the product?
Okta is easy to use once it’s set up. However, the implementation process is difficult and can take some effort to get right.
What do you dislike about the product?
The implementation process took a long time and was confusing throughout.
What problems is the product solving and how is that benefiting you?
It helped create a much more secure login experience for the company I was working for.
Intuitive UI, Easy Integrations, and Reliable Okta Uptime
What do you like best about the product?
The UI is very intuitive and you can find what you're looking for very quickly. Also the amount of out of box integrations with major software products makes it easy to setup and implement. There is very little downtime with in the Okta environment. And the support given for onboarding an after installation is great.
What do you dislike about the product?
When connected to an Active Directory for user and group integration, it doesn't automatically sync after changes are made. The sync has to be done manually every time you make change in Active Directory. A little irritating but not a deal breaker by any means.
What problems is the product solving and how is that benefiting you?
Being able to have a secure way to log in to our enterprise apps and be able to utilize the same security for log in to our home grown in house designed apps. This is huge because it saves time and coding effort in implementing a login
Efficient, Mobile-Friendly Logins with Okta
What do you like best about the product?
It’s very efficient for logging in to my software programs. I like that I can use it on my phone, and that it works with my Google Authenticator app as well.
What do you dislike about the product?
I really have nothing bad to say about Okta. I just wish it didn't time out during my work day but I can understand that is for security purposes.
What problems is the product solving and how is that benefiting you?
Okta solves me being able to log into my software apps simultaneously and in a secure manner. It saves me time from logging into individual apps.
Simplifies App Management with Robust Security
What do you like best about the product?
I like how Okta manages multiple apps at one place, saving me from remembering multiple passwords. Okta's passwordless future is great, allowing the use of multiple apps without the hassle of logging in and remembering different URLs. I appreciate that Okta manages security on its own and is highly secure. The performance and ease with which I don't have to manage security and performance are also things I value. The initial setup was easy too.
What do you dislike about the product?
While the basic APIs are excellent, the documentation for more niche or advanced edge cases can sometimes be sparse or outdated. Many essential security features like adaptive MFA or lifecycle management are sold as separate add-ons rather than being part of a unified core package. Compared to legacy heavyweights like SailPoint, Okta's governance feature can feel a bit 'light' and sometimes struggles with highly complex, multi-condition access certifications.
What problems is the product solving and how is that benefiting you?
Okta is like a magic key for my computer. Instead of having to remember a hundred different passwords for all my apps, I only have to remember one. It saves me from getting frustrated when I forget a password. It also makes sure all my work tools are ready. It even makes everything run fast and smooth so I don't have to wait for my apps to load. Basically, it does all the hard "security work" in the background so I can just jump in and start having fun working.
Streamlined Identity Management and Security with Okta SSO and MFA
What do you like best about the product?
Okta’s SAML and OIDC single sign-on capabilities really help streamline identity management and make employee access more efficient. The added security of funneling access through Okta, together with its flexible MFA configuration options, has been very beneficial—especially when it comes to removing system access in a timely and thorough way. Furthermore, the ability to provision and maintain downstream accounts via SCIM integration saves valuable time and effort for our IT staff.
What do you dislike about the product?
While Okta provides numerous integrations with mainstream platforms, there’s still room to improve its third-party integration offerings. Leveraging pre-built integrations with 3rd-party applications is easy and straightforward, however custom integrations to 3rd-party applications can be rather cumbersome for our organization.
What problems is the product solving and how is that benefiting you?
We used to have to maintain many different sets of credentials for many different sites or systems, but now with Okta our users are able to quickly and easily log into Okta and then access all their other sites via SAML or OIDC single-sign-on. This saves our users a ton of time and hassle. Also, having a single place to deactivate a user's access upon termination is an enormous benefit from a security perspective.
showing 1 - 10