What do you like best about Okta?
Well, there are quite a few features that I use the most. However, I will try to summarize them with the following categories:
Single Sign-On (SSO): Allowing users to log in once and access multiple applications (e.g., Microsoft 365, Google Workspace, Salesforce, Slack, etc.) without having to re-enter their credentials.
Multi-Factor Authentication (MFA): Giving an extra layer of security using codes, push notifications, security keys, or biometrics.
User Lifecycle Management: Automating either employee or customer onboarding, changes, and offboarding, and synchronizes users with directories and applications.
Adaptive Access: Assessing the risk of each login attempt (location, device, behavior) and requests additional verification when necessary.
Client Identity Management (CIAM): When developing an application, Okta can manage user registration, login, password recovery, and social media authentication.
Integration with Existing Directories: Connects to services like Active Directory or LDAP to unify identity management. Review collected by and hosted on G2.com.
What do you dislike about Okta?
Here are the things I can say I dislike the most about Okta, for both user and admin perspective:
High costs. As the number of users increases or the need for advanced features, costs can rise significantly. Not ideal for small businesses.
Complex licensing. It is not always clear which features are included in each plan. Some important features require additional licenses, which can lead to unexpected costs.
High learning curve for administrators. Advanced policy configurations, adaptive authentication, deployment workflows, or federation can be complex and require specialized knowledge.
Vendor lock-in. Once a company has integrated hundreds of applications and automated processes around Okta, migrating to another platform can be costly and time-consuming. Review collected by and hosted on G2.com.