Our main use case for Okta Customer Identity is that all of our in-house applications are under Okta. A user or customer has to log in to Okta Customer Identity and then they can access the application. It serves as our main SSO application which we are using.
Okta Platform
Okta, IncExternal reviews
External reviews are not included in the AWS star rating for the product.
Okta, Inc. – The World's Leading Identity and Access Management Platform.
Multi-Factor Authentication (MFA) adds an extra layer of security.
Simple and intuitive user interface.
Automates user onboarding and offboarding.
Integrates with thousands of cloud and on-premises applications.
Centralized management for user accounts and devices.
Adaptive authentication for risk-based security.
Self-service password reset and management.
Strong audit, compliance, and access review tools.
The most helpful aspect of Okta is its ability to provide secure single sign-on (SSO) to all workplace applications, allowing users to access everything with just one set of credentials and making daily workflows seamless and efficient. This dramatically reduces the time spent logging in, minimizes password fatigue, and enhances security across the organization.
Other highly helpful features include:
Automated user onboarding and offboarding, which streamlines IT processes and reduces manual work.
Multi-factor authentication (MFA), adding strong protection against unauthorized access.
Centralized management of users, devices, and access policies for better control and visibility.
Self-service password resets, empowering users to manage their credentials and reducing IT support tickets.
Key Upsides
Single Sign-On (SSO): Users log in once to access all necessary apps, saving time and reducing password fatigue.
Multi-Factor Authentication (MFA): Keeps sensitive data safe by requiring an additional verification step for logins.
Easy Integration: Connects with thousands of applications and platforms, both cloud and on-premises.
Automated Onboarding/Offboarding: Allows quick provisioning and deprovisioning of accounts, reducing manual labor for IT teams.
Centralized User Management: IT administrators manage all users and devices from a single dashboard, enhancing control and oversight.
Self-Service Tools: Empowers users to reset passwords and manage their own profile, significantly lowering helpdesk workload.
Adaptive Authentication: Responds to risks dynamically by requiring stronger verification if suspicious activity is detected.
Compliance & Audit Capabilities: Tracks activities and access for reporting, compliance, and security reviews.
Common Dislikes
Complexity for New Users: Initial setup and configuration can be complex and time-consuming, especially for organizations without dedicated identity management expertise.
Mobile App Issues: Some users experience battery drain and occasional glitches with Okta Verify and mobile authentication apps.
Frequent Authentication Prompts: End users may find repeated MFA prompts or login verifications disruptive to workflow.
Support Challenges: While Okta support is generally helpful, some users report delays or difficulties with advanced troubleshooting and integration issues.
Learning Curve: The range of features and configuration options can have a steep learning curve for some administrators.
Problems Solved by Okta
Password Fatigue and Security Risks: By providing Single Sign-On (SSO), Okta eliminates the need for users to remember and manage multiple passwords, reducing weak password use and associated security risks.
Complex Access Management: Centralizes user access control across cloud and on-premises applications, enabling IT teams to enforce consistent access policies and reduce unauthorized access.
User Provisioning and Offboarding Challenges: Automates account creation, modification, and deactivation based on employee lifecycle, streamlining IT workload and mitigating risk of orphaned accounts.
Multi-Factor Authentication Complexity: Integrates adaptive MFA to strengthen security without burdening users, dynamically adjusting to risk levels.
Compliance and Auditing: Provides detailed access reports and logs for regulatory compliance and security audits, reducing manual tracking efforts.
Benefits
Improved Security Posture: Stronger authentication and centralized policies reduce cyber risks and breaches.
Increased Productivity: Users spend less time managing passwords and troubleshooting login issues, focusing more on productive work.
Operational Efficiency: IT teams save time with automated onboarding/offboarding and simplified access management, reducing support tickets.
Better Compliance: Easier generation of audit reports and adherence to security standards supports regulatory compliance requirements
Centralized dashboard with multiple IAM & Security Controls
User provisioning and deprovisioning
automation
policy control
API integrations
Has improved secure access to all applications through a single login point
What is our primary use case?
What is most valuable?
The main features of Okta Customer Identity that I find most valuable are its security and easy accessibility.
We are using the self-service feature in Okta Customer Identity for almost one year now. Previously, it was not configured, but now we are using it.
We find Okta Adaptive Authentication useful as whatever feature we feel should be implemented and beneficial for users, we have implemented it. We use multi-factor authentication and it is 100% implemented. Multi-factor authentication is also useful for the security part for us.
The report functionality is another important part of Okta Customer Identity; we might need to check logs and other things. The report part is very much useful. I am 100% satisfied with the customizable options in Okta reporting features. This is a very good feature, and it is 100% implemented, so I do not want any changes because it is working as expected.
What needs improvement?
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.
For how long have I used the solution?
I have been working with Okta Customer Identity for more than three years.
What do I think about the stability of the solution?
I rate Okta Customer Identity a 10 out of 10 for stability; it is the best.
What do I think about the scalability of the solution?
The scalability part of Okta Customer Identity is fine, there is no blocker and we can upgrade whenever we need.
How are customer service and support?
Okta Customer Identity's technical support is fine; they help to fix tickets within the timeline and their support is very good.
How would you rate customer service and support?
Neutral
How was the initial setup?
The initial setup process for Okta Customer Identity is simple.
Which other solutions did I evaluate?
I do not think there are other competitors to Okta Customer Identity in the market. In my previous company, we tried to switch from Okta Customer Identity to some other SSO authentication method, but we did not find anything relevant. We kept going with Okta Customer Identity.
What other advice do I have?
We discontinued the license for Barista and have moved to Workato Genie. We implemented Workato Genie around six months ago. It is required for the sales team, and they purchased some licenses for the sales and marketing team in the US. We have configured that for IT as well. There can be multiple Genies according to the requirement. If you ask something for the Genie, there is a global Genie and it can redirect that task to the relevant Genie for sales, IT, HR, and other things.
We are not using Google except G Suite. We have some licenses for ChatGPT, but that is not for IT requirements. We are still using AWS, Okta Customer Identity, and Jamf; these are our main core business applications.
The main benefits Okta Customer Identity provides to users include single point of login for all applications and single authentication, which saves time and reduces frustration. If something is not working, users just open a ticket with the Okta team instead of reaching out to other application owners or POCs.
I give Okta Customer Identity a rating of 10 out of 10.