Okta Reviews & Ratings

4.6/5

“Strong Brand, Community & Ecosystem; But Watch Out for Hidden Costs”

I chose Okta partly because I trusted the brand, knew many others using it, and integration with my ecosystem was easier. But during budgeting I discovered we needed more modules than we initially thought, which bumped up cost.

Pros : Okta has a strong reputation, large community, many integrations, support resources, docs, marketplace. The reliability, uptime, and trust in the vendor give me confidence.

Cons : But “base cost” often doesn’t include all modules you’ll need. Add-ons for advanced security, custom policies, governance, etc., increase cost. Some customers complain about unclear licensing or expensive mandatory features.

Switched from : Hexnode

Reason to switch : I switched from Hexnode that lacked mature support or ecosystem. Okta cost more but gave me more integrations, trust, and fewer surprises—though financial planning had to adapt.

4.6/5

“Powerful Tools for Mid-Large Businesses, Less Smooth for Small Teams”

As we expanded from ~50 to ~500 users, Okta’s features grew more helpful. But when I joined earlier, I saw that small teams struggle with setup, feature-selection, policies, etc.

Pros : Okta scales well. As our company grew, onboarding/offboarding, user management, auditing, etc. stayed manageable. Permissions, group policies, etc. are top notch.

Cons : For smaller teams, some features feel overkill; the cost and overhead (training, admin) might not justify full usage of all capabilities.

Switched from : Auth0

Reason to switch : I switched from Auth0 provider because we wanted more robust features, concurrent sessions, compliance, etc. Okta gave those, though with higher cost.

4.5/5

“Good for Hybrid Environments, but On-Prem Sync and Legacy Apps Are Tricky”

We have a mix of on-prem Windows servers, old line-of-business apps, and cloud services. Okta helped unify identity but integrating legacy apps or syncing attributes between local AD and Okta required custom work.

Pros : Okta works well when integrating on-prem Active Directory, LDAP, etc., with cloud apps, letting us manage hybrid identity.

Cons : Some legacy apps or internal tools don’t support modern auth (SAML/OIDC), require custom connectors. Sync issues or latency between on-prem directory changes and Okta reflect. Also, sometimes attribute mapping (DNs, manager fields etc.) is inconsistent.

Switched from : FortiAuthenticator

Reason to switch : I switched because our previous system forced us to maintain separate identity systems for cloud vs on-prem. With Okta, we hoped to unify everything, though not all legacy systems play nicely.

4.5/5

“Very Secure & Reliable, But MFA & Usability Trade-Offs for End Users”

In daily operations, Okta helps prevent unauthorized access. But there have been times when someone’s phone died or they didn’t have internet and couldn’t complete MFA, which delayed their work. Admins know to plan for backup methods but user experience can suffer.

Pros : Okta’s security features (adaptive MFA, risk-based authentication) make me feel safe. The ability to enforce zero-trust style access policies strengthens our posture.

Cons : Users sometimes complain about too many MFA prompts, issues with mobile authenticator apps, push/OTP delays. Often if the second factor device is unavailable, login becomes frustrating.

Switched from : OneLogin

Reason to switch : I switched from OneLogin because Okta’s MFA options, integrations, and adaptive policies were more robust and secure.

4.5/5

“Enterprise-Grade Security & Single Sign-On Made Daily Access Easier”

As the IT admin, I used Okta to unify identity and access across more than 50 cloud apps. Once everything was running, user sign-ons dropped, password fatigue reduced, and we improved security posture. On the downside, setting it up involved a steep learning curve.

Pros : Okta’s SSO works beautifully; I only have to log in once to access all my work apps. MFA adds a solid layer of protection. The UI is intuitive, and automating onboarding/offboarding has reduced our IT workload.

Cons : The initial setup was complex; policies and integrations took time to configure correctly. Also, licensing is expensive for smaller teams.

Switched from : Azure Active DIrectory

Reason to switch : : I switched from AAD because although it was decent, Okta provided better cross-platform SSO, more flexible lifecycle management, and vendor-neutral identity tools that worked more smoothly with non-Microsoft resources.

4.5/5

“Useful for User Self-Service, But Occasional Frustrations with MFA & Recovery”

I used to spend time helping users when they forgot passwords or couldn’t access apps. Okta’s self-service features cut down those tickets. But there have been scenarios where someone lost their phone and backup options were not obvious, which delayed access.

Pros : Self-service password reset, user profile management, etc., reduce helpdesk load. Users like being able to fix minor pain points themselves.

Cons : When MFA device is lost or unavailable, recovery can be more painful; also, some users complain about too many forced password resets or strict password policy causing friction.

Switched from : Hexnode

Reason to switch : I switched from our old SSO which had no self-service options, so helpdesk was overwhelmed. Okta improved that.

4.5/5

“Great Audit Trails and Compliance, But Configuration Complexity Can Delay Deployment”

Our compliance team uses Okta’s audit tools constantly. We can see who accessed what, when, etc. That helps with internal reviews and external audits. But getting those set up correctly initially took many meetings and trial-and-error.

Pros : Okta provides excellent logs, audit reports; helps with regulatory compliance (GDPR, HIPAA, SOC2 etc.). Very helpful for risk assessments and audits.

Cons : Setting up correct audit policies, log retention, fine-grained permissions often requires deep expertise or consulting. Mistakes at configuration become security risk.

Switched from : miniOrange

Reason to switch : We moved from miniOrangel that didn’t have good logs or audit capability. Okta’s auditing made compliance much easier.

4.5/5

“Excellent Uptime & Reliability; Some Performance Hiccups During Peak Usage”

Most of my day I take Okta for granted—it just works. But there have been moments, especially start-of-day or after weekends, when login latency spikes, causing small but noticeable slowdowns.

Pros : Logins, SSO, MFA are usually fast and reliable. Okta’s infrastructure is solid. Downtime is rare.

Cons : Occasionally during high traffic or after an update, there’s latency or delays in authentication or login flows. Some report delays in OTP/push notifications.

Switched from : LastPass

Reason to switch : Our prior system had worse outages or was on-premises and more brittle. We moved to Okta for better reliability and lower maintenance.

4.3/5

“Strong Lifecycle Management & Compliance Tools, But Pricing Hits Hard at Scale”

My organization needed strong governance, access reviews, and audit trail. Okta delivers. But when we added more apps, more policies, and more security demands, the pricing and administrative overhead increased substantially.

Pros : Okta’s user provisioning/deprovisioning is very reliable. The compliance/audit capabilities are very helpful for regulation-heavy industries.

Cons : The cost for advanced modules (adaptive MFA, custom rules, advanced policies) escalates quickly. Smaller or mid-size organizations may find the pricing tough. Also some custom configurations (e.g. nested group rules, RADIUS integration) are not trivial.

Switched from : Rublon

Reason to switch : I switched because our previous Rublon did not provide such strong compliance auditing or lifecycle management; Okta offered more mature features in these areas.

4.3/5

“Huge Integration Catalog & Vendor Neutrality Are Big Pluses”

Our org uses dozens of tools-Slack, Salesforce, internal tools, payroll, etc. Everything tied into Okta so users have one source of truth. When we onboard new apps, Okta usually supports them; custom ones take more work.

Pros : Almost every SaaS app we use is integrated or has a connector in Okta. It works with both cloud and many on-premises systems. That reduces friction when adopting new tools.

Cons : Some legacy or custom apps are harder to integrate or support non-standard protocols. The integration process for those can take time and sometimes custom development.

Switched from : Avatier

Reason to switch : I switched from Avatier alone because while Azure works well for Microsoft stuff, Okta’s vendor-neutral catalog meant fewer workarounds for non-Microsoft tools.