The areas where I think PingFederate needs room for improvement include that the most significant area I would recommend is that things such as redirects still do not have majority of the application direct integration, such as Oracle ERP. There are many other applications which do not have direct integration between identity provider and service provider, and we see that in terms of business, there is a lot of complexity involved and a lot of customization required. PingFederate has to improve a lot in terms of providing the single tenant facility rather than depending on other third parties.
Regarding areas for improvement in Ping Identity Platform, there is not much. In terms of licensing and implementation costs, it has premium pricing, and it has a very complex implementation. It provides greater feasibility, but it takes a very long time in terms of complete building. There is a very limited number of legacy support, which can pose potential difficulties in integrating with certain older or legacy systems. Additionally, issue troubleshooting can be difficult at times. Sometimes issues can be difficult to diagnose and require extensive technical expertise. There is also a very steep learning curve for administrative purposes and potential difficulties with offline authentication scenarios.
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.
In SSO ( /categories/single-sign-on-sso ), I would like to enable ServiceNow ( /products/servicenow-reviews ) 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.
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.
Cyber Security Engineer at TECHMINDZ DIGITAL CONSULTING PRIVATE LIMITED
Real User
Jul 17, 2024
The application only supports specific protocols. SAML is more secure than OAuth or OIDC because OAuth and OIDC expose user ID and password. It's similar to using grant types for access and authorization in production and non-production environments. These are the areas that need improvement.
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.
Streamline the user interface for administrators and end-users to make configuration and daily use more intuitive. Reduces the learning curve and administrative burden, leading to better adoption and more efficient management. Optimize performance to handle high-load environments more efficiently, reducing latency and improving response times. Provide more comprehensive and user-friendly documentation, including more use cases, troubleshooting guides, and best practices.
In access token management, we have to attach a certificate. In that column, I have to enable the search option to edit certificates. We can choose a drop-down to search for which certificate we have to create, which is difficult.
They could enhance the product's device tracking for better zero-trust security would be beneficial. Currently, it tracks IPs well but lacks detailed device information, which is crucial from a security standpoint. Setting up applications and configuring policies can be complex, requiring meticulous planning and manual configurations.
IAM technical architect at Emprest Innovations Private Ltd
Real User
Apr 17, 2024
It requires some expertise to set up and manage. Also, having dedicated support is helpful. It's not something anyone can just set up and run without assistance – ideally, a team using PingFederate should have at least one or two people with in-depth knowledge of the product.
Ping Identity Platform offers cloud capabilities for applications, supporting Single Sign-On, Multi-Factor Authentication, and passwordless authentication. It features flexible integrations and federated identity management, enhancing security through detailed compliance features and seamless IDP integration.This platform meets enterprise needs with role-based access control, device management, API security, and risk-based adaptations. Its BYOD support, ease of integration, biometric...
The areas where I think PingFederate needs room for improvement include that the most significant area I would recommend is that things such as redirects still do not have majority of the application direct integration, such as Oracle ERP. There are many other applications which do not have direct integration between identity provider and service provider, and we see that in terms of business, there is a lot of complexity involved and a lot of customization required. PingFederate has to improve a lot in terms of providing the single tenant facility rather than depending on other third parties.
Regarding areas for improvement in Ping Identity Platform, there is not much. In terms of licensing and implementation costs, it has premium pricing, and it has a very complex implementation. It provides greater feasibility, but it takes a very long time in terms of complete building. There is a very limited number of legacy support, which can pose potential difficulties in integrating with certain older or legacy systems. Additionally, issue troubleshooting can be difficult at times. Sometimes issues can be difficult to diagnose and require extensive technical expertise. There is also a very steep learning curve for administrative purposes and potential difficulties with offline authentication scenarios.
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.
In SSO ( /categories/single-sign-on-sso ), I would like to enable ServiceNow ( /products/servicenow-reviews ) 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.
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.
The application only supports specific protocols. SAML is more secure than OAuth or OIDC because OAuth and OIDC expose user ID and password. It's similar to using grant types for access and authorization in production and non-production environments. These are the areas that need improvement.
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.
Streamline the user interface for administrators and end-users to make configuration and daily use more intuitive. Reduces the learning curve and administrative burden, leading to better adoption and more efficient management. Optimize performance to handle high-load environments more efficiently, reducing latency and improving response times. Provide more comprehensive and user-friendly documentation, including more use cases, troubleshooting guides, and best practices.
In access token management, we have to attach a certificate. In that column, I have to enable the search option to edit certificates. We can choose a drop-down to search for which certificate we have to create, which is difficult.
They could enhance the product's device tracking for better zero-trust security would be beneficial. Currently, it tracks IPs well but lacks detailed device information, which is crucial from a security standpoint. Setting up applications and configuring policies can be complex, requiring meticulous planning and manual configurations.
Ping Identity Platform must improve its UI since its management console is complicated.
It requires some expertise to set up and manage. Also, having dedicated support is helpful. It's not something anyone can just set up and run without assistance – ideally, a team using PingFederate should have at least one or two people with in-depth knowledge of the product.
The management console needs to be improved. PingID should revise it.
The product is not customizable. It is not suitable for consumer identity management.
The initial setup appears to be difficult in the beginning.