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

• Solutions are attractive to engineers but harder to sell to upper management.
• Support was initially a challenge but has improved immensely.

Incentivized

As I mentioned earlier, efficiency and security are this software's bread and butter. The usability is very simple and straightforward, very user-friendly. As a result, it is efficient in a way that we can provide faster quality service to our merchants, and security in a way that our credentials will never leak since PingOne always values Personal Identifiable Information.

Incentivized

Ping's support is willing and attentive, but if I am in a position to engage them I am often at a point where most of the usual support engineers would not be in a position to answer the questions I have. However, Ping has been more than willing to engage their product and development teams with our organization as we take advanced deployment and use case challenges to them.

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

This solution is selected before my time so, not much influence ,but product allow to customized and require decent ping skills to configure the solution. Okta and Other solutions are well suited in this category with some positive and some negative capabilities. it must say that Auth0 is the best option with Azure Identity to move ahead.

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

• Decreased overall number of help desk calls for password reset.
• Reduced time need for authentication; user[s] now have to authenticate once to be able to use more than 20 applications, instead of authenticating 20 times (per app).