Ping Identity Platform Reviews

I've been managing it in my company. I am more on the implementation side.

We implement the MFA feature, multifactor authentication and administrate the application.

When it comes to authentication, the focus is always on security. That means using a separate device to verify the user logging in.

On the security side, PingID adds an extra layer, contributing about 20% of the overall security. Then, authentication brings more advanced features and contributes further.

PingID excels in managing user access and profiles. That's where it integrates most deeply with the existing systems.

The most valuable feature is the two-factor authentication (2FA). 

The mobile biometric authentication option improved user experience. It's always about security because, with two-factor authentication, it's always a separate device verifying the actual user logging in.

The management console needs to be improved. PingID should revise it.

I have been using it for a year. 

I would rate the stability an eight out of ten because there had been some issues.

I would rate the scalability a seven out of ten. PingID is adapting to most challenges. 

We have small and medium businesses as our customers. 

We get support. The support engineers are good. They are quite proactive.

I would rate my experience with the initial setup a seven out of ten, with ten being easy to set up. 

The initial setup is not too complex. Deployment is really quick and typically the entire process takes two hours. 

The pricing is neither too expensive nor too cheap.

Overall, I would rate the solution an eight out of ten because there is room for improvement in terms of usability. 

The only feature we were looking for in PingID was SSO integration with our existing web app. However, they have good support towards MFAs, SSO, and other authentication methods that are either already included in the current plan or made available with a minor upgrade.

PingID should put a little more effort into making a pretty self-explanatory deck about their tech features and the services they offer. I suggested this improvement directly to the sales manager, who was friendly enough to take that feedback.

PingID is a reputed solution. I was already aware of PingID because we used PingID as a solution for all our login functionalities in my previous company. When I had an opportunity to add these capabilities to my new organization, PingID was one of my first choices. It's not because I'm biased but because I already knew the solution was scalable.

The solution architect and the sales managers gave the initial support. PingID's support portal is confusing, and it took a couple of back-and-forths to get some support from the support folks. However, the account manager did help us with the support questions by putting us in touch directly with some of the engineers. I rate PingID an eight and a half out of ten for customer support.

Positive

PingID’s initial setup was pretty straightforward.

The initial deployment with POC took about a month, and the actual production deployment took about a couple of weeks, maybe around four weeks or so. About four engineers, including a tech architect, were involved in the solution's deployment.

PingID's pricing is pretty competitive.

PingID's team was pretty good. We were trying to build a solution and wanted to deploy it for only a couple of hundreds of customers. We didn't want to sign up for a 1,500 or 5,000 feet plan. PingID was pretty understanding about our needs and provided us with great plans for the smallest fee they could provide. We had good negotiations with them, and they were pretty friendly. PingID provided all the required technical support even before we signed up. The sales manager ensured he supported me throughout the process, and we signed a deal with PingID.

Overall, I rate PingID an eight and a half out of ten.

We use PingID for multifactor authentication, passwordless login, and push notifications. 

I like the self-service feature. The 502 and UBP systems are also excellent. PingID's ability to authenticate with SSH, RDP, and Windows login is pretty handy. It covers the entire spectrum of use.

PingID's device management portal should be more easily accessible via a link. They provide no link to the portal like they do for the service. The passwordless functionality could be more comprehensive. You can't filter based on hardware devices. Having that filtering option would be great. Device authentication would be a great feature. 

We have used PingID for five years.

Early on, there were many changes to PingID because the company was trying to address some security vulnerabilities, but we only faced outages twice in three years due to these updates.  It's fairly stable overall. 

PingID's scalability is good. We haven't had any issues, but we don't have a huge amount of traffic. My organization has around 150,000 users. 

We've had issues with incorrect reporting and needed to contact support. Reports were missing values, or the details weren't clear. We had a quick resolution 80 percent of the time. 

Positive

I rate PingID seven out of 10 for ease of setup. It takes less than a day to deploy in one environment. It's a cloud-based solution, so you only need to set up an account and link it to your on-prem environment using an adapter. 

I rate PingID eight out of 10. I would recommend it depending on the use case. You need to clarify your requirements before implementing the solution. 

My primary use case for PingID was multifactor authentication, then I used PingOne, which showed me the transaction, so the whole person authentication, including the errors. Based on the resulting errors, I checked the PingFederate connection mapped for the particular application and published information about the issue.

Through PingID, there was multifactor authentication. In particular, secondary authentication was enabled to secure the application and is supported in IOS, even for mobile devices.

During the PingID authentication, you need to swipe or give your fingerprint on your mobile and then get the SMS for authentication.

What I like best about PingID is that it's very user-friendly.

PingID is well-built as a developer tool and regularly upgrades and updates via patches. Sometimes, my company faces vulnerability issues, and PingID even helps through vulnerability patches.

The tool has excellent features.

I also like that PingID has clear documents that will help you integrate it with other solutions.

PingID classifies the type of environment into internal and external, with the internal environment for internal users and the external environment for external users. For example, the external users would be cabin crew members who log in using the mail ID through multifactor authentication. This is an area for improvement in PingID because you need to take additional steps so you can trust both internal and external users.

My company had to use the CIDR authentication selector as an additional step, through policy creation in the PingFederate website, with the help of trusted IP, where all people belong to a particular network, then my company needs to do some IP load balancing. My company had to configure the particular IP in the CIDR authentication selector, then only then can it classify users into internal or external.

An internal user doesn't need to do multifactor authentication, but an external user will be redirected to a request from the PingFederate console, and then, based on the user authentication method, through biometrics, the user will be authenticating from Active Directory. If the user is valid, authenticated, and the authorization is approved, the user will then be redirected to the application.

I have more than three years of experience with PingID. The last time I used PingID was six months ago. I'm now working on the PingFederate side.

Stability-wise, PingID is an eight out of ten for me. It's a very stable solution, but sometimes, failures occur that you can't control. For example, my company checked logs in Sumo Logic and had Dynatrace as a monitoring tool. If there's a failure in the software system, where everything is connected, for example, if PingFederate isn't working, Dynatrace will send a report to my company. If PingFederate or an agent isn't working, my company won't receive any logs, so it depends on the policy and infrastructure, but PingID stability is an eight for me.

The scalability of PingID purely depends on the server side and how you're going to configure it. In some cases, it would also depend on how you'll do performance tuning. How scalable PingID  is will differ from infrastructure to infrastructure. For example, I supported the easyjet.com environment which had more than ten thousand user bandwidth.

Support-wise, PingID is an eight out of ten because when my company faced a P1 incident or issue that company members couldn't resolve, my company created a P1 request. The PingID SME joined the call within thirty to forty minutes, which was the vendor's service agreement, but only for P1 issues.

For P2 issues, it takes around one hour and forty minutes; for P3 incidents, it could take eight hours; for P4, it usually takes ten hours but could reach up to twenty hours.

Positive

I used PingFederate with PingID because PingFederate can assign internal and external users and configure validation. Based on the improv setup, you can also use PingFederate for your internal environment. Still, in my company, I'm using PingFederate for the external environment, where servers run outside the company's environment.

I used CA SiteMinder in the past, which was an older tool, and I wanted to use the latest technology, so I switched to a newer tool, PingDirectory, which I installed. Now I can work on PingDirector in terms of schema rules, mapping, etc.

The initial setup for PingID is seven out of ten for me. I had to install PingFederate, have experience with PingDirectory and Apache Studio, and do everything myself, including the environment setup. I've successfully implemented the project.

PingID for mobile apps is okay, as you don't need to deploy PingID in any of the servers. Still, you need to create the connection, enabling PingFederate in a particular environment. PingFederate is not infallible, and it's the only inject site, so you inject, then run the property file, configure the admin port, cluster port, and the index number for the engine node. You need to denote how many engine nodes you must classify for the admin node on the property file, then run that file. Once the PingFederate console runs, automatic cancellation will occur, and the application will work.

The complete deployment of the PingID project didn't take more than five to six months, including the POC, development, and production.

I've implemented PingID, so it was an in-house implementation.

PingID saves you time between thirty to forty percent, so time is the ROI, at least to me.

PingID pricing is a ten out of ten because it's a little bit cheaper than other tools, such as Okta and ForgeRock, and supports multiple tools. It also has the main feature of MFA via finger swiping or SMS versus other MFA tools, where you need to wait for a few seconds to get the new code, even if you've been authenticated. The speed of transactions in PingID is also very fast because it only takes microseconds after swiping your finger. I like the tool very much.

I've evaluated other software, such as PingFederate, PingDirectory, PingAccess, and PingOne, apart from PingID.

I'm working in the identity access management domain, so I've used software such as PingFederate, PingDirectory, PingID, PingOne, and PingAccess.

PingID is deployed on the AWS service, so that's on a cloud environment.

I'm part of the engineering team, with three members working on the PingID project and five from the support team working on PingID. Within the environment I supported, twelve thousand people used PingID, particularly crew members who used the MFA feature of the solution.

The maximum number of users I've seen from PingID based on the environment I supported was up to twelve thousand.

My recommendation to anyone looking into implementing PingID is that before working with the tool or any other tool, you first need to understand it and get some basic knowledge about it. With basic knowledge, you can implement PingID. Consider why you'd implement the tool in your environment and for what purpose. How many people will benefit from using the tool? Before implementing, it would be best to compare PingID with other tools to see the features and benefits.

My rating for PingID is eight out of ten because it's a faster tool with multiple features. It also supports one of the adapters of PingFederate, the composite adapter, which allows you to enable MFA on an adapter-based setup.

My company is a PingID partner.

We use the product to run different reports. 

We have encountered instances where it is not easy to do authentication. 

I have been using the product for two years. 

I would rate the tool's stability a ten out of ten. 

My company has 1000 users for the product. 

My experience with the support team is good. 

The product's setup is easy if you have all the information and support. 

I would rate the product a nine out of ten. 

The solution has a smooth and configurable user interface for single sign-on capabilities. We can do a lot of configurations. It is a fairly good product for workforce identity management.

The product is not customizable. It is not suitable for consumer identity management.

I have been working with the product for two years.

Our clients are mainly government entities and big investment firms.

The technical support is not proactive. If an issue or concern is raised, the support person must jump on a call as soon as possible, but it is not happening now.

Neutral

We also recommend ForgeRock. It is used for access management. It doesn’t have many configurations but allows customizations. We can achieve a lot of things using customizations. Wherever PingID is not suitable for the customer, we ask them to choose ForgeRock so that we can customize it as per the requirements and deliver the solution.

The tool is very easy to set up.

The product is costly. Large organizations can afford it. However, it is not suitable for smaller companies. Smaller organizations can choose Okta or One Identity.

We recommend the product to our customers. Organizations can buy the product if they are ready to spend a lot of money. They must be aware that the support is average. However, the tool is very good. Overall, I rate the solution a seven out of ten.

We primarily use PingFederate for access management authentication. It is mainly for authenticating employees, but we sometimes use it to authenticate customer applications. 

PingFederate gives you granular control over the settings. There are many options for fine-tuning policies. 

PingFederate's UI could be streamlined. They have recently made several improvements, but it's still too complex. It's a common complaint. The configuration should be simplified because the learning curve is too steep. 

PingFederate is stable. 

PingFederate is an efficient solution, but the scalability depends on the environment. It's an on-prem solution, so it depends on the number of servers we have. We have around 150,000 users. 

Deploying PingFederate is straightforward. The deployment time depends on the size of your environment and the things you need to do to get it working, such as configuring the server and the firewall rules. Installing it is simple, but you might need to spend a week configuring it to work in your environment. 

I rate PingFederate eight out of 10. 

PingID is similar to identity access management and customer identity access management, however, the profile is different.

With PingID, we were able to integrate all of our devices easily. It provides ease of connection with all of our devices.

PingID is more secure than other products. We have a BYOD policy, and we have different devices that are used within our company like laptops and iPhones. 

PingID would benefit from a better user interface for integration. Currently, we are doing manual configuration for a changeover. If some of the scripts could be automated, the integration would be faster, and we would reduce the manual effort.

I have been working with PingID for one year.

PingID is stable. With respect to stability, I would rate it a nine out of ten. The product only requires a small team to maintain it. We use both an offshore model and an onsite-to-offshore model to support them. We have a separate team used for migration and maintenance. In total, there are eight people with both teams put together.

The solution is scalable. It is pretty easy to expand. This is one of the reasons we chose to implement it in our organization. We wanted to connect many BYODs and expand to more devices.

We have 9,000 profiles that need to access PingID.

Previously, we used SiteMinder. We switched to PingID because our standards had changed with respect to information security. 

Also, PingID is seen as better performance-wise, and it meets the requirements for our application landscape. 

The initial setup of PingID is simple. We had to migrate the applications from the cloud and from on-premises, one application at a time, directly to Ping. We had to move to the Ping directory so that it can identify all the users. This all takes time to set up.

Overall, I would rate PingID a nine out of ten.