The use case I mentioned, particularly for Single Sign-On, is that we have used it for Single Sign-On. It allows users to access multiple applications with one set of credentials. Users don't need to remember different kinds of credentials. Single Sign-On comes into the picture where Ping Identity Platform provides the Single Sign-On feature. Another thing is that Ping Identity Platform provides adaptive multi-factor authentication. It uses context-based security, based on things such as location, device, and different networks, which triggers extra authentication only when the risk is detected. That is what we call adaptive multi-factor authentication. Then comes Identity Orchestration. It is one of the great features that Ping Identity Platform has. It provides a no-code, drag-and-drop interface which builds complex, personalized user journeys, from start to bottom, from when a user starts, then their updates such as transfers, then when a user leaves. All of these things are managed by Identity Orchestration. If we need to define it, we can define it as per the client's requirements. It is completely feasible as per client requirement. As well as it provides complete API security. We have secure data flow which protects APIs through OAuth and OpenID Connect protocols. These are the SSO protocols. Again, it has great features such as Ping One Protect, which is a real-time AI-driven threat detection that prevents bot attacks, account takeovers, and fraudulent activity. Ping Identity Platform is also used for IGA; we have SailPoint, we have Okta. Ping Identity Platform is useful for IGA, that is Identity Governance, which is helpful for user lifecycle management, which includes provisioning, deprovisioning, and compliance, as well as for recertification. I utilize analytics tools for Autonomous Identity within Ping Identity Platform. This product uses machine learning for Identity Governance, specifically for auto-provisioning access, analyzing access patterns which reduces roles, then identifying high-risk access outliers, where it will be used for Autonomous Identity. Then comes PingHelix, which is an AI product used for Ping Identity Platform. It is a strategic initiative that embeds AI at the core of Ping One platform which creates a more intelligent, proactive identity secure posture. Finally, there's Ping Intelligence, which is used to detect anomalies and threats specifically against APIs, identifying potential data breaches in real-time. That is the use for advanced analytics.
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.
I work with Governance ( /categories/grc ), Risk, and Compliance ( /categories/grc )(GRC), IT Service Management (ITSM) ( /categories/it-service-management-itsm ), and Customer Service Management (CSM) modules of ServiceNow ( /products/servicenow-reviews ). My project is related to cybersecurity. I have touched on generative AI and integrations like SOAP APIs. I have used the Ping Identity Platform ( /products/ping-identity-platform-reviews ) for seamless Single Sign-On (SSO) ( /categories/single-sign-on-sso ) in enterprises, offering flexible integrations and federated identity management within a mid-sized enterprise environment.
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.
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.
I have around ten years of experience with IAM tools, and I have been working mostly on access management for the last few projects. My overall experience, considering that I have worked with various access management tools, like PingFederate and Okta. In terms of identity management, I have worked with IDM and SailPoint. In terms of privileged access management, I want to work closely with CyberArk to provide the service account and administer it to the vault. I also understand the concept of PSM and password rotation. Integrating CyberArk with Ping, you get both RADIUS and SAML. Coming to my roles and responsibilities, in my current project for new application onboarding and access assigned to the IAM team who are assigned service tickets. We pick up those tickets and assign them to us, and then we communicate with the application owners.
I use the solution in my company for SSO implementations in different applications using two protocols, one of which is SAML and the other one is OIDC. For implementing SSO into those applications using the aforementioned protocols, I use Ping Identity Platform.
IAM technical architect at Emprest Innovations Private Ltd
Real User
Apr 17, 2024
We use PingFederate to provide SSO (Single Sign-On) solutions to enterprise applications. We support protocols like SAML (Security Assertion Markup Language), OAuth, and OpenID Connect. For example, an organization wants to enable SSO for their applications. We use PingFederate to integrate those applications and onboard them with their IdP (Identity Provider).
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 use case I mentioned, particularly for Single Sign-On, is that we have used it for Single Sign-On. It allows users to access multiple applications with one set of credentials. Users don't need to remember different kinds of credentials. Single Sign-On comes into the picture where Ping Identity Platform provides the Single Sign-On feature. Another thing is that Ping Identity Platform provides adaptive multi-factor authentication. It uses context-based security, based on things such as location, device, and different networks, which triggers extra authentication only when the risk is detected. That is what we call adaptive multi-factor authentication. Then comes Identity Orchestration. It is one of the great features that Ping Identity Platform has. It provides a no-code, drag-and-drop interface which builds complex, personalized user journeys, from start to bottom, from when a user starts, then their updates such as transfers, then when a user leaves. All of these things are managed by Identity Orchestration. If we need to define it, we can define it as per the client's requirements. It is completely feasible as per client requirement. As well as it provides complete API security. We have secure data flow which protects APIs through OAuth and OpenID Connect protocols. These are the SSO protocols. Again, it has great features such as Ping One Protect, which is a real-time AI-driven threat detection that prevents bot attacks, account takeovers, and fraudulent activity. Ping Identity Platform is also used for IGA; we have SailPoint, we have Okta. Ping Identity Platform is useful for IGA, that is Identity Governance, which is helpful for user lifecycle management, which includes provisioning, deprovisioning, and compliance, as well as for recertification. I utilize analytics tools for Autonomous Identity within Ping Identity Platform. This product uses machine learning for Identity Governance, specifically for auto-provisioning access, analyzing access patterns which reduces roles, then identifying high-risk access outliers, where it will be used for Autonomous Identity. Then comes PingHelix, which is an AI product used for Ping Identity Platform. It is a strategic initiative that embeds AI at the core of Ping One platform which creates a more intelligent, proactive identity secure posture. Finally, there's Ping Intelligence, which is used to detect anomalies and threats specifically against APIs, identifying potential data breaches in real-time. That is the use for advanced analytics.
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.
I work with Governance ( /categories/grc ), Risk, and Compliance ( /categories/grc )(GRC), IT Service Management (ITSM) ( /categories/it-service-management-itsm ), and Customer Service Management (CSM) modules of ServiceNow ( /products/servicenow-reviews ). My project is related to cybersecurity. I have touched on generative AI and integrations like SOAP APIs. I have used the Ping Identity Platform ( /products/ping-identity-platform-reviews ) for seamless Single Sign-On (SSO) ( /categories/single-sign-on-sso ) in enterprises, offering flexible integrations and federated identity management within a mid-sized enterprise environment.
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.
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.
I have around ten years of experience with IAM tools, and I have been working mostly on access management for the last few projects. My overall experience, considering that I have worked with various access management tools, like PingFederate and Okta. In terms of identity management, I have worked with IDM and SailPoint. In terms of privileged access management, I want to work closely with CyberArk to provide the service account and administer it to the vault. I also understand the concept of PSM and password rotation. Integrating CyberArk with Ping, you get both RADIUS and SAML. Coming to my roles and responsibilities, in my current project for new application onboarding and access assigned to the IAM team who are assigned service tickets. We pick up those tickets and assign them to us, and then we communicate with the application owners.
I use the solution in my company for SSO implementations in different applications using two protocols, one of which is SAML and the other one is OIDC. For implementing SSO into those applications using the aforementioned protocols, I use Ping Identity Platform.
We use PingFederate to provide SSO (Single Sign-On) solutions to enterprise applications. We support protocols like SAML (Security Assertion Markup Language), OAuth, and OpenID Connect. For example, an organization wants to enable SSO for their applications. We use PingFederate to integrate those applications and onboard them with their IdP (Identity Provider).
I've been managing it in my company. I am more on the implementation side.
PingAccess is used for managing access, URL management, and website management.