<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: We allow third party client tools but are having issues integrating CyberArk to those third-party tools. When they go to connect the MFA challenges sometimes do not respond at all or disregard the approval. Has anyone else dealt with these? in Privilege Cloud Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/we-allow-third-party-client-tools-but-are-having-issues/m-p/1347716#M2872</link>
    <description>&lt;P&gt;What MFA method(s) are affected? If you could provide a bit more detail about the workflow experiencing the problem I could provide some suggestions.&lt;/P&gt;</description>
    <pubDate>Wed, 22 Jan 2025 22:19:06 GMT</pubDate>
    <dc:creator>CyberArkAlumni</dc:creator>
    <dc:date>2025-01-22T22:19:06Z</dc:date>
    <item>
      <title>We allow third party client tools but are having issues integrating CyberArk to those third-party tools. When they go to connect the MFA challenges sometimes do not respond at all or disregard the approval. Has anyone else dealt with these?</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/we-allow-third-party-client-tools-but-are-having-issues/m-p/1347715#M2871</link>
      <description />
      <pubDate>Wed, 22 Jan 2025 18:44:46 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/we-allow-third-party-client-tools-but-are-having-issues/m-p/1347715#M2871</guid>
      <dc:creator>JustinOrenbaun</dc:creator>
      <dc:date>2025-01-22T18:44:46Z</dc:date>
    </item>
    <item>
      <title>Re: We allow third party client tools but are having issues integrating CyberArk to those third-party tools. When they go to connect the MFA challenges sometimes do not respond at all or disregard the approval. Has anyone else dealt with these?</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/we-allow-third-party-client-tools-but-are-having-issues/m-p/1347716#M2872</link>
      <description>&lt;P&gt;What MFA method(s) are affected? If you could provide a bit more detail about the workflow experiencing the problem I could provide some suggestions.&lt;/P&gt;</description>
      <pubDate>Wed, 22 Jan 2025 22:19:06 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/we-allow-third-party-client-tools-but-are-having-issues/m-p/1347716#M2872</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2025-01-22T22:19:06Z</dc:date>
    </item>
    <item>
      <title>Re: We allow third party client tools but are having issues integrating CyberArk to those third-party tools. When they go to connect the MFA challenges sometimes do not respond at all or disregard the approval. Has anyone else dealt with these?</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/we-allow-third-party-client-tools-but-are-having-issues/m-p/1347717#M2873</link>
      <description>&lt;P&gt;Currently for client authentication we use the CyberArk MFA on the Identity app. Our users experience either the MFA challenge is never sent, sometimes they will send the challenge but it will timeout before they can complete the approval, and sometimes approvals do not work. We don't face this issue in the web as we federate logins and use a different MFA for that. For clients the main favorite is Rocket Remote desktop, but vision app and ASG are also used.&lt;/P&gt;</description>
      <pubDate>Thu, 23 Jan 2025 14:19:00 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/we-allow-third-party-client-tools-but-are-having-issues/m-p/1347717#M2873</guid>
      <dc:creator>JustinOrenbaun</dc:creator>
      <dc:date>2025-01-23T14:19:00Z</dc:date>
    </item>
  </channel>
</rss>

