In Okta Customer Identity, I primarily respond to application handling with around three thousand applications. This includes handling internal applications for permanent employees and third-party applications for contractors. I also work on certification renewal annually and the setup of SSO pages to enhance security.
Okta Platform
Okta, IncExternal reviews
1,142 reviews
from
and
External reviews are not included in the AWS star rating for the product.
Two-Factor Authenticator
What do you like best about the product?
The platform offers atrong security capabilities, such as single sign-on (SSO) and multi-factor authentication (MFA), while maintaining an intuitive user interface for end users.
What do you dislike about the product?
The intricacy of setup and configuration is yet another possible drawback.
What problems is the product solving and how is that benefiting you?
By reducing the risks to passwords, Okta imprves security while streamlining the user experience by enabling users to access different apps using a single set of credentials.
One place for all our apps
What do you like best about the product?
Our tech stack is very large. Without Okta, we had to create multiple logins with different passwords and save them somewhere. Not to mention, every product had unique requirements for their passwords! In came Okta with an easy to use product that let me have a single sign on to all my apps— life saver!!!
What do you dislike about the product?
Not a lot. Sometimes, I’d struggle with getting my notification to sign in but all those bugs have been solved and the product works seamlessly now!
What problems is the product solving and how is that benefiting you?
I don’t need multiple login details and passwords stored in random places.
Setting Up Two-Factor Verification
What do you like best about the product?
Applications and resources are protected by Okta's identity managed and user authentication.
What do you dislike about the product?
The maximum number of Okta Verify devices that can be linked to a user account is unlimited.
What problems is the product solving and how is that benefiting you?
Just one sign-on. Secure SSO from any devices, whether SAML, Wsfed, or OIDC, for all of your web apps, both locally and in the cloud, with customizable restrictions.
Great for Organizing apps
What do you like best about the product?
Great for using a Single Sign on. Makes it easy to sign into apps from one location.
What do you dislike about the product?
Setting up the single sign on could be an easier process.
What problems is the product solving and how is that benefiting you?
It allows for our clients to login to many of our applications without the need to remember a lot of different passwords.
Okta AWS Integration
What do you like best about the product?
Easy to use, Easy to integrate , Supports wide range of products integration
What do you dislike about the product?
I dont experience any issues as such.....
What problems is the product solving and how is that benefiting you?
Using Okta as single source of identity, integrated with Active Directory. It provides seamless integration using SAML with AWS IAM and Identity center. Also it provide integration with wide range of applications using SAML.
Capable platform with tons of features
What do you like best about the product?
How granular of a system it can be when needed
What do you dislike about the product?
No downsides as of yet. Setting up SSO has been straight forward and workflows seem to do the job fine as well
What problems is the product solving and how is that benefiting you?
Having an active directory of users, creating workflows like offboarding, and having a single sign on platform for users.
Leverage reliable server management for seamless identity operations
What is our primary use case?
What is most valuable?
The most valuable aspect of Okta Customer Identity is the server's reliability, especially for directory and node management. I set up different directories for traffic redirection, ensuring backup when a data center faces issues and maintaining seamless operations.
What needs improvement?
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.
For how long have I used the solution?
I have been working with Okta Customer Identity for nine months.
What do I think about the stability of the solution?
I would rate the stability of Okta Customer Identity as eight. It has allowed us to manage identity signals effectively, though some customers are resistant to certain procedures, making stability slightly challenging.
What do I think about the scalability of the solution?
I rate the scalability of Okta at nine. I have a clear understanding of the architecture and processes involved, which allows for effective scaling to manage user privileges, application logins, and leveraging tools like Splunk for efficient data management.
How are customer service and support?
We have a strong internal support system including application support, data center, and IDM teams. However, direct interaction with Okta's technical support is minimal as we typically manage internally.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
Before using Okta Customer Identity, I did not utilize a different solution for these use cases.
How was the initial setup?
The initial setup of Okta Customer Identity took about five hours and required a team of three.
What about the implementation team?
We needed three people for deployment and now require about four people for maintenance, including rotations among five to six employees.
What's my experience with pricing, setup cost, and licensing?
The pricing for Okta Customer Identity is very economical. It is much cheaper compared to Oracle Access Manager, and the company focuses on internal training to mitigate additional certification costs.
Which other solutions did I evaluate?
We evaluated Microsoft Azure as another option, but both Okta and Azure are quite similar in functionality.
What other advice do I have?
Overall, I rate Okta Customer Identity as nine. Although there are some areas of improvement, its pricing and scalability make it a preferred choice for managing user identity and applications.
Okta review
What do you like best about the product?
The security is top notched. It is very versatile since you can add services within the system.
What do you dislike about the product?
One thing is the lack of troubleshooting steps or guide when Okta encounter technical issues.
What problems is the product solving and how is that benefiting you?
We value the security of our tools and Okta does best on managing to keep all our tools in one place.
An extremely reliable tool
What do you like best about the product?
Okta has a ease of use and implementation for contstant frequency of use along with the number of features and the ease of intergration along with the product makes it reliable
What do you dislike about the product?
constant login and authentication issues along with lack of customer support on their end.
What problems is the product solving and how is that benefiting you?
It's able to compile and unify all the programs our company uses to help intergrate them seamlessly without any additional add-ons or steps lacktherof.
Protects the applications by avoiding cross-site scripting
What is our primary use case?
I have used Okta for security purposes. It grants access only when you have the proper credentials, which I find essential for utilizing new technologies and web applications.
What is most valuable?
The most valuable feature of Okta is its security. You can only log in if you have the access, which protects the applications by avoiding cross-site scripting. Hackers cannot access the system directly. Only after receiving a message from Okta, you can log in, making it highly secure.
What needs improvement?
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.
What do I think about the stability of the solution?
Okta is a stable product.
What do I think about the scalability of the solution?
Currently, scalability is a top priority, but there are no issues with adding many users to Okta.
Which solution did I use previously and why did I switch?
Before Okta, I manually created portals using a username and password stored in a database. Okta introduced a different process.
How was the initial setup?
Initially, it was complicated to set up since I was a beginner and there was no proper documentation. Now that I am more experienced, it is easier to handle.
What other advice do I have?
I need to analyze fully in the future, and if I do not have any concerns, I will share any with you via LinkedIn. As of now, I do not have any additional advice.
I'd rate the solution eight out of ten.
showing 131 - 140