IBM Cloud App ID vs. Okta

Whenever you need to provide Security Provider functionality for a web based application it is well suited. You can also integrate with other directory services (e.g. SAML, Facebook, Google), but not so easily with other Auth0 based services. The customization of the login page is very intuitive, but does not allow much customisation. using the integrated Cloud Directory, you do not need to integrate with existing security providers and you can build up your own user base - including Multi-Factor Authentication settings and password policies.

Incentivized

It has extensive compatibility and rich feature set of integrating with a wide array of core systems and SaaS platforms. Daily I utilize Okta's user-friendly central hub to simplify access the numerous applications we utilize within my company (Google Workspace, Slack, Zoom, Salesforce, Microsoft Office 365, among many others.)

Incentivized

• Uses OIDC/OAuth, so the protocols for accessing user info and token management is familiar
• Clear pricing model
• API binds nicely with IBM Cloud Functions
• Billed as part of our IBM Cloud, along with our other services
• Front-end SDK for Vue, works well

Incentivized

• Centralized control of enterprise passwords
• Extensive customization of acceptable password criteria
• One system for Identity and Access Management to learn
• Scalable throughout the university for all central services
• Uniform login experience for students, faculty, and staff
• Single point of response to address termination of access
• Ability to use FastPass for lower priority systems
• Excellent support of multi-factor requirements

Incentivized

• Pricing can be heavy on small organizations.
• User interface updates could be timely.
• Cloud services hangs at times, but very rarely.

Incentivized

• I'm not sure it's really a room for improvement thing, but due to the granularity offered by Okta, sometimes it can be challenging to find exactly what you're looking for.
• There was an instance in which we had issues getting SAML configured for an application. I feel this challenge was mostly user error (on our part) because we didn't realize the SAML instructions were SPECIFIC to each app integration and changed (codes) each time. We attempted to mirror the settings/configurations of an existing app (same app, but different domain). I think having a note somewhere that indicated that the instructions were unique to each integration would have saved us a bit of time. Again, I'm not sure this is really an issue with Okta though, more of a user learning curve thing.
• Sometimes searching for things is a challenge (without the "Rockstar" add-in). For example, if you have a user group called "Okta_users_everyone", searching for "everyone" will not find it. You have to search for the beginning of the object name (not just any part of it). The ability to search partial or wildcard would greatly enhance search functionality.

Incentivized

Okta has a passion to provide secure and scalable identity solution. Their passion has come across as advocacy in a way that has deepened my knowledge of the field of authentication. I took identity for granted before but after seeing features such as external authentication I know that Okta can enable my business to reach new heights

Some of its features are great and some are slightly complex and not easy without vendor support.

Incentivized

The Okta Identity Cloud advertises 4 9's of reliability and I would go as far to say that it may even do better than that. As a true Global organization that operates in just about every region of the world, we have yet to have an issue with The Okta Identity Cloud that has impacted our business operations.

Incentivized

From my perspective, for the things that my group uses it for, Okta is very fast. It is as least as fast as the local password database methods that it replaces on our campus enterprise services. I do not believe that it slows anything down at all. In fact, not having to think too much about the login, because they all look the same, probably speeds things up somewhat.

Incentivized

We've had a few support cases over the years and every case has been handled by the Okta support team beautifully. We received clear answers to questions we had regarding setup and even were provided simple to follow guides on how to setup their product to use with custom applications.

Incentivized

Both the software have different use cases, like IBM Cloud App ID, which will be more suitable for internal websites and apps or specific event website authentications, Auth0 can be suitable for consumer websites, e-commerce sites, where social media login is preferred more by the users. Both have their own capabilities so can be chosen according to their needs.

Incentivized

With respective to user interface and license cost, we thought The Okta Identity Cloud was better than other tools for use. Their customization of license was another reason for us to go with The Okta Identity Cloud over other tools.

Incentivized

Being a cloud native application, The Okta Identity Cloud is extremely scalable and easy to setup. By integrating into existing directories and applications via standard techniques and protocols, it is very easy to both initially setup and add additional users as required. Once all the necessary integrations are setup, it's a simple rinse and repeat process to onboard additional users (which can be automated with imports as well)

Incentivized

• This has had a positive impact on security while developing our company's first major application.
• It has impacted our development process heavily by making authentication simpler than ever.
• It has helped reduce time in our development process by having easy integration and useful guides.

Incentivized

• Customer experience has been a big win for us. Extremely minimal issues reported.
• We did not have a PAM in place at all until The Okta Identity Cloud
• Relatively easy to deploy. No major downtimes to deploy was a nice bonus.