IBM Cloud App ID vs. PingOne from Ping Identity

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

Really like [this] solution, it fits our requirements 100%. There are unlimited possibilities to extend the product, either by creating additional adapters or selectors. We really like the policy management level in PingFederate. It's extremely helpful when we can specify customer journey per many different requirements like user location, application type etc. As well, both StepUp and TopDown authentication flows were implemented [easily].

• 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

• Based on open standards, we can use as much or as little of the Ping suite as we like, depending on which other technologies we've already implemented.
• Continuous innovation and product enhancements have ensured their products continue to meet our rapidly evolving needs.
• Ping Identity has been an outstanding partner, starting with the RFP process and continuing to this day, years after the sale. They are focused on our success at every level of the company and are highly responsive to our needs, issues, and product suggestions.

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

Incentivized

• PingID has some limitations when used as the MFA for some LDAP implementations. You need to use it as a RADIUS password credential validator to solve for some of those limitations, which in turn causes challenges with our ephemeral cloud deployment model of PingFederate.
• The basic logon services within PingFederate are adequate and well-documented, but simple features like disabling user input after entering credentials would help with some of the additional customization required to support real world failure modes.
• PingCentral authorization models and configuration remain unpolished compared to other products, and now the features seem to be shifting toward onboarding PingAccess and PingDirectory over improving baseline administrative functionality/operations.

Incentivized

Ping's solutions are a powerful tool, but with that comes the need for skills to operate them. It's not easy for inexperienced engineers to run. From the end-user perspective, it is fully customizable and can be as seamless as you need.

Incentivized

Really good customer support, we always receive what we need. Sometimes instead of [a] solution (which have to be developed) we are receiving [a] work around, which is helping ad hoc. Then after time [needed for support to] develop fix we are receiving full fix or we [are] just waiting for new version of the product where our "bugs" are fixed.

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

PingOne from Ping Identity is the clear winner here. I can say this because the cost of their service is very worth it, and their service offers more than their competitors. In addition to that, this software is still improving daily, which only means that there is still more to come, and their Developers are giving their fair share of service to keep their software the best.

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

• The TCO for our deployment of Ping will be over a million dollars/year less to operate compared to the systems it replaces.
• Moving the organization to federated protocols allows greater flexibility in our cloud migration strategy and zero trust designs.
• Operating with federated protocols internally facilitates M&A and divestiture activities.

Incentivized