PingOne for Customers

I run my own IT company where we work with multiple products. Nowadays, we are not doing a lot of Ping Identity Platform  projects because there are other technologies like Ping and Okta and other options available which are better than Oracle. That is why we don't have a lot of Oracle projects these days.

We are working mostly with Ping technology and ForgeRock , and we do have some Oracle projects that we are running, but majorly we are running Ping and ForgeRock .

Ping Identity Platform  can provide a solution for both workforce identity and access management and also for consumer identity and access management, which is CIAM .

There are many things that are better in Ping Identity Platform. First, it is a very lightweight product. Second, I would say it's a converged platform which can do both identity management, access management, and recently they are bringing privilege management capability as well. Another thing is that they also have something very unique, which is their user interface-based journeys, which provides their single sign-on experience. That is a very good thing. Ping Identity Platform also supports all the latest features such as passwordless and managing agentic identity. They also have AI capabilities within the product itself.

They provide out-of-box almost all the MFA options, including email OTP, text-based OTP, TOTP, HOTP, biometric, and passwordless. They can also integrate with any third-party MFA provider. From that perspective, it's a complete platform.

They support OAuth and OpenID. They also have this product called Ping Gateway, which you can use to implement API security. It provides features such as throttling, adding authentication, or everything you can do as part of Ping Gateway.

From the improvement perspective, they could bring IGA  capability, which right now they only have in their SaaS offering. Other than that, Ping Identity Platform has multiple products for access management, identity management, a solution for API security, a solution for authorization, and a product for identity verification. From that perspective, it is complete, and they are improving it.

I think a nine.

Ping Identity Platform can be compared with any other leader in the identity and access management space, but I would say it would be high because they have been the leader in all the analytics reports, whether it's Gartner or KuppingerCole or any other reports.

I would say Okta, and Okta and IBM from that perspective. IBM and even Oracle could be alternatives, but Oracle is a dying technology at this point in time.

Ping Identity Platform has some analytic capability, but mostly it produces the logs which can be sent to any external SIEM  tools such as QRadar or Grafana  or anything similar. It basically produces the logs which can be consumed by any analytics tool.

It is very easy to integrate.

They have been the leader for the last eight or nine years according to Gartner and KuppingerCole or any other analyst reports.

I would rate Ping Identity Platform at a ten. Overall, I would rate my experience between nine and ten. My overall review rating for Ping Identity Platform is nine.

I work with Governance , Risk, and Compliance  (GRC), IT Service Management (ITSM) , and Customer Service Management (CSM) modules of ServiceNow . My project is related to cybersecurity. I have touched on generative AI and integrations like SOAP APIs. I have used the Ping Identity Platform  for seamless Single Sign-On (SSO)  in enterprises, offering flexible integrations and federated identity management within a mid-sized enterprise environment.

I appreciate that the Ping Identity Platform  does not require coding and offers flexible integrations and federated identity management. Generative AI helps to automate access review and streamline governance workflows. The platform enhances security measures by analyzing multi-factor authentication attempts, highlighting suspicious patterns, and generating compliance reports.

In SSO , I would like to enable ServiceNow  Generative AI for auto-diagnosing PingFederate SSO failures and suggest remediation steps. I would like to see enhanced incident summarizations and awareness virtual agents driven by Generative AI.

I have gained experience with the Ping Identity Platform for about two and a half years. My recent experience is interrelated with my core project on cybersecurity.

During the initial setup, I faced challenges resolving high-volume authentication failures by using Generative AI to pinpoint PingFederate policies. However, I addressed delays in user onboarding by automating access provision through Generative AI workflows.

I have not experienced any stability issues personally. However, some colleagues have mentioned API connectivity, data security, and privacy issues.

In Ping, I have reached out to technical support for troubleshooting SAML certificate mismatches and federated errors between Ping and enterprise apps. They have helped support incident resolution for authentication failures using ServiceNow incident workflows and Generative AI summary.

I have not worked with any other SSO or IAM  solutions before the Ping Identity Platform.

The initial setup of PingFederate in a cloud environment using Generative AI took around one to two weeks. Once everything is set, it does not require much maintenance.

I evaluated ServiceNow and the Ping Identity Platform.

I would recommend PingFederate as an IAM  solution for its no-code environment, single sign-on, multi-factor authentication, bidirectional services, and advanced features. On a scale of one to ten, I would rate the Ping Identity Platform as ten out of ten.

I usually deploy single sign-on and multi-factor authentication using PingOne  for customer-facing applications to enhance security and user convenience. I use PingFederate  to integrate with Kerberos-based systems, such as Salesforce , AWS , ServiceNow , and Google. I configure various OAuth grant types and set up Windows Service Federation and SAML 2.0 protocol service provider endpoints using PingOne and PingFederate.

It's convenient for users to log in through Ping using the Kerberos adapter because it doesn't require them to authenticate again. If a user is already logged into the organization's domain, the system automatically checks the Kerberos ticket in the background when they try to access another application through Ping. It logs them in without prompting for a password or reauthorization.

You don't need prior experience to use this; you need to understand how it works. Experience is only necessary when integrating it with systems. For instance, when using any application through Ping in your organization, it just needs to be connected to the organization's domain. This setup works seamlessly on a PC, automatically detecting the Kerberos ticket and logging you in. However, it won't work on a mobile device since the mobile doesn't have a Kerberos ticket. On a mobile phone, you'll be prompted to authenticate again.

It's important to keep learning and improving in every phase of life. There are instances when you need to use programming languages like Java and Python, especially when integrating systems or making code changes.

One significant challenge was ensuring smooth user migration during system upgrades in Ping. At my current company, based on successful authentication, I enabled secure user migration in the PingOne directory to maintain continuity in user access and minimize disruptions. Another challenge was troubleshooting and resolving issues related to PingID MFA flows, which I addressed through performance tuning, logging, and debugging.

I have been using Ping Identity Platform for eight years.

I manage the scale of integration across multiple applications, ensuring minimal disruption to ongoing business operations. This requires effective communication and coordination with the team and stakeholders to address issues and mitigate risks promptly.

In several projects, particularly when deploying Ping across large environments, I encountered challenges supporting many users during peak times, which strained the authentication infrastructure. To address this, I implemented PingID clustering to distribute the load across multiple servers, ensuring high availability and load balancing to prevent single points of failure. The multi-factor authentication process didn't introduce significant latency, especially for high-transaction applications. This involved thorough performance tuning, optimizing network configurations, and fine-tuning Ping settings. I regularly monitor system performance to identify and resolve any bottlenecks.

150-200 users are using this solution.

I rate the scalability as seven out of ten.

The product is affordable and starts at 20,000 dollars/year, depending upon the license and maintenance requirement. It makes our work easier and saves a lot of time.

I haven't faced any debugging issues. It was only during the testing that I faced.

I advise you to be extremely careful when integrating Ping with any application, especially during authentication. If an intruder manages to get authorized, they're just one step away from accessing all your organization's data. With PingFederate, users only need to log in once, so if an attacker gains access, it becomes tough to track and stop them. The critical takeaway is to be vigilant during integration and ensure that every security measure is thoroughly implemented.

Overall, I rate the solution a nine out of ten.

I primarily use the platform for OAuth and SAML-enabled applications, especially third-party and SaaS applications. I utilize the SAML protocol for those that support SAML, while for OAuth-supporting applications, I use OAuth, OIDC, and OpenID tokens. Additionally, for server-to-server communication, I employ the client credentials grant. For mobile-based native applications that require refresh tokens, I utilize those as well. I manage OAuth client ID registrations for certain SaaS applications and implement various authorization flows, such as Kerberos authentication for intranet requests and form-based authentication for external network requests. Furthermore, I have integrated Multi-Factor Authentication (MFA)  to enhance the security of critical applications.

From a security perspective, I highly value the product's biometric authentication methods such as FIDO, FaceID, YubiKey , and the mobile app. These methods provide a higher security level than email authentication, which can be compromised if the email is breached.

There is room for improvement in the solution, particularly in security. With the increase in phishing attacks, organizations are moving towards passwordless authentication, which is the best approach.

It involves checking certificate authentication or other methods instead of relying on user-entered passwords. This is where Multi-Factor Authentication becomes crucial.

I have been using Ping Identity Platform  for almost 13 to 14 years.

The product is stable overall, with most issues arising from integration with other systems like Splunk. Weekly restarts help maintain stability and minimize the risk of crashes due to system connections.

The solution has supported varying numbers of users across different organizations, ranging from 65,000 to 70,000 users in my current environment to handling millions of requests per hour in previous organizations.

Scalability can present challenges, depending on what needs to be scaled. For example, adding servers is straightforward, but care must be taken to avoid disrupting existing environments during integration. Increasing memory or heap size is seamless, and I can restart one server at a time without any issues.

The customer support team is quite responsive and knowledgeable. Whenever I encounter any issues or require assistance, they quickly provide solutions.

The setup is generally straightforward, but it can depend on the environment. For example, in a previous organization, two companies merged, each with its own Active Directory and identity management instances. I had to build a new environment to match both the SSO-enabled applications. Although the process was straightforward, it depended highly on the organization’s architecture and requirements.

The deployment timeline depends on the availability of the application team. I aim to make SSO  seamless between environments, avoiding multiple authentication logins for end users. Typically, the implementation takes about a month, considering network ACLs and other configurations. However, migrating applications can be challenging and may take months. My last project took almost one and a half to two years to complete the migration process.

The platform's value justifies the pricing, especially considering its security features and scalability. While it might seem a bit higher, the return on investment regarding security and efficiency is well worth it. The pricing is appropriate for the level of service and capabilities the platform delivers.

I have evaluated other solutions in the past, but I found this platform to be the most comprehensive regarding security, scalability, and ease of integration. Its strong support for various authentication protocols like OAuth, SAML, and MFA, along with its robust disaster recovery capabilities and adaptive clustering model, made it the ideal choice for our organization's needs.

I use Ping Identity Platform  as the Multi-Factor Authentication solution. Once the first level of authentication is completed with a user ID, password, or card authentication, the request is directed to PingID. I have configured profiles that allow the use of devices like the mobile Ping app. I also use email in some scenarios, although I prefer FIDO authentication methods like YubiKey  or FaceID for enhanced security.

I have integrated the platform into all environments using an adaptive clustering model that operates in an active-active configuration. Two regions are active-active, while the third serves as a passive disaster recovery region. When integrating new applications, I follow a structured process, beginning with intake forms to determine whether OAuth or SAML is required, depending on whether the application is accessing internal or external systems. ServiceNow  tickets are used for configuration. This adaptive clustering ensures that the requests are automatically routed to the disaster recovery center if two data centers are down.

It includes a centralized tool where users can create their OAuth client IDs. However, I do not recommend this practice as it can lead to unnecessary client IDs and access tokens, increasing system load. Instead, I have developed a controlled process where users can request what they need, and the request is then sent to me for approval. This approach ensures that the process is managed effectively.

Overall, my experience with the solution has been very positive. It has played a crucial role in enhancing the security and efficiency of our access management processes. While there are always areas for improvement, particularly in terms of scalability and phishing resistance, it has consistently met our expectations. I would highly recommend it to organizations looking for a reliable and secure access management solution.

I rate it an eight.