Item: Okta
Rating: 6
Author: Verified User

Overall Satisfaction with Okta

Use Cases and Deployment Scope

Okta replaces a legacy single-signon system that was hosted in on our own systems.

Pros and Cons

Pros

It works with several multi-factor methods.
software as a service is nice for eliminating in-house maintenance issues

Cons

Without single-signon services I have to authenticate dozens of times per day.
Short time out settings cause data lose during long sessions.

Return on Investment

We no longer have to maintain our own ID services.

Independent Platform

mhh! Not really a fan. Google is the only cloud service we interface with.

Reliability

Our in-house CAS servers with FIPS 140 password store had better MTBF. Likewise, Okta was hacked, whereas our in-house system was never hacked.

Not too well. The password store in NetIQ (a.k.a. eDirectory) was FIPS 140 certified.
The CAS opensource platform, paired with eDirectory was never hacked and provided true SSO across more than 200 in-house and hosted servers.

Key Insights

Do you think Okta delivers good value for the price?

Not sure

Are you happy with Okta's feature set?

Did Okta live up to sales and marketing promises?

I wasn't involved with the selection/purchase process

Did implementation of Okta go as expected?

Would you buy Okta again?

Likelihood to Recommend

It works, but . . .
It replaces a legacy single-signon system, but I miss those features. Having to re-login multiple times per day is annoying. I'm sure the other problems may be caused by our own settings.

For instance, while uploading hours worth of online learning content into our LMS, my session will sometimes timeout during a "save" operation, and I have to start over.

Okta Feature Ratings

Comments

Please log in to join the conversation

Mhh. . .

Software Version