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
External reviews are not included in the AWS star rating for the product.
Okta AWS Integration
Capable platform with tons of features
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
An extremely reliable tool
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.
Straightforward IDP deployment and management.
Identity access enhancement with good support and an easy setup
What is our primary use case?
The solution is used to eliminate a VPN, provide identity authentication, and single sign-on (SSO). We use Zscaler authentication to manage endpoint logins, endpoint report management, and single sign-on for applications.
What is most valuable?
The most valuable feature is the identity access authentication.
What needs improvement?
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.
For how long have I used the solution?
I have been working with Okta Workforce Identity for four years.
What do I think about the stability of the solution?
The solution is rated as a nine in terms of stability.
What do I think about the scalability of the solution?
Okta is not designed fully for scalability.
How are customer service and support?
Okta provides good support. While we are unable to have it in-house, we can raise a ticket, and they support us well.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
We utilize Okta and Zscaler for multifactor authentication.
How was the initial setup?
The setup process is very user-friendly and has no issues.
What about the implementation team?
Our internal team underwent training materials and configured the implementation successfully.
What's my experience with pricing, setup cost, and licensing?
The pricing is very high, which is an area for improvement.
What other advice do I have?
I recommend Okta Workforce Identity to others, particularly for mid-sized and large enterprises.
I'd rate the solution nine out of ten.
Enhancing secure access with single sign-on and multi-factor authentication
What is our primary use case?
As an Okta Identity engineer, I implement Okta for different clients such as banks, telecoms, and insurance companies. These companies need an IAM solution to manage their employees securely and provide them with access to the right applications. Okta is used to automate provisioning and support any errors encountered during and after deployment.
Companies use Okta Workforce Identity to manage their employees' secure access to applications and to minimize the effort required by IT teams to manage identities. The solution helps organizations allow their employees to log into their applications without re-entering credentials and securely access their applications via MFA.
What is most valuable?
The most valuable functions are Single Sign-On (SSO) and Multi-Factor Authentication (MFA). These two modules serve as dual components, essential for securing application access for employees.
What needs improvement?
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.
For how long have I used the solution?
I've been handling Okta Workforce Identity for five years now.
What do I think about the stability of the solution?
There might be occasional glitches or bugs that need improvement, so I would rate its stability as eight out of ten.
What do I think about the scalability of the solution?
Okta scores a nine out of ten for scalability.
How are customer service and support?
Okta support is efficient, actively responding on time. They deserve a rating of eight out of ten for their technical support.
How would you rate customer service and support?
Positive
Which solution did I use previously and why did I switch?
How was the initial setup?
The setup process for Okta is relatively straightforward and not overly complex.
What's my experience with pricing, setup cost, and licensing?
Okta is one of the more expensive IAM solutions, and I would rate it an eight regarding cost.
Which other solutions did I evaluate?
The main competitor to Okta Workforce Identity is CyberArk Identity.
What other advice do I have?
I would recommend Okta Workforce Identity to other users.
I'd rate the solution nine out of ten.