<?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: SSH support with FIDO 2 authentication in Privilege Cloud Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/ssh-support-with-fido-2-authentication/m-p/1295623#M17</link>
    <description>&lt;P&gt;Hi @ba31 ba31​&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you for engaging with the community! Since two of our members have shared solutions to your question, could you please let us know if any of them have resolved your issue? If so, please consider marking the most helpful response as “Select as Best”- this helps others with similar questions find the right answer quickly.&lt;/P&gt;&lt;P&gt;If the question remains unresolved, I recommend submitting a ticket with our support team for further assistance.&lt;/P&gt;&lt;P&gt;Thank you,&lt;/P&gt;&lt;P&gt;Shaked&lt;/P&gt;</description>
    <pubDate>Wed, 11 Feb 2026 10:24:42 GMT</pubDate>
    <dc:creator>CyberArkAlumni</dc:creator>
    <dc:date>2026-02-11T10:24:42Z</dc:date>
    <item>
      <title>SSH support with FIDO 2 authentication</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/ssh-support-with-fido-2-authentication/m-p/1295620#M14</link>
      <description>&lt;P&gt;Trying to enforce FIDO2 Authentication with SSH Native client via SIA ZSP approach  but its keep reporting "You have no supported MFA factors assigned. Please contact your tenant administrator". Is it supported by Windows SIA connector or need Unix SIA connector ?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Wed, 04 Feb 2026 15:19:00 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/ssh-support-with-fido-2-authentication/m-p/1295620#M14</guid>
      <dc:creator>ba31</dc:creator>
      <dc:date>2026-02-04T15:19:00Z</dc:date>
    </item>
    <item>
      <title>Re: SSH support with FIDO 2 authentication</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/ssh-support-with-fido-2-authentication/m-p/1295621#M15</link>
      <description>&lt;P&gt;@ba31 ba31​&amp;nbsp;PSMP and SIA does not currently support FIDO2 as an MFA mechanism. This ER may address it in the future: https://community.cyberark.com/s/article/Recognize-biometric-FIDO2-tokens-like-Yubikey-Bio--3e2d-e77&lt;/P&gt;</description>
      <pubDate>Wed, 04 Feb 2026 22:22:09 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/ssh-support-with-fido-2-authentication/m-p/1295621#M15</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2026-02-04T22:22:09Z</dc:date>
    </item>
    <item>
      <title>Re: SSH support with FIDO 2 authentication</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/ssh-support-with-fido-2-authentication/m-p/1295622#M16</link>
      <description>&lt;P&gt;a possible workaround is that you can enable MFA caching for SIA connections, which will enable end-users to first authenticate to the web UI with FIDO2 and from there download a token valid for x hours that can be used as a password for SIA connections. If using this token then the user is not prompted again for MFA. It might not be suitable for you, but especially for SSH with the custom "Alias" scripts that CyberArk provide it can make for a pretty smooth user experience. The token is locked to the IP address of the machine so it can't be stolen and re-used.&lt;/P&gt;</description>
      <pubDate>Thu, 05 Feb 2026 14:27:22 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/ssh-support-with-fido-2-authentication/m-p/1295622#M16</guid>
      <dc:creator>Jon_Musker</dc:creator>
      <dc:date>2026-02-05T14:27:22Z</dc:date>
    </item>
    <item>
      <title>Re: SSH support with FIDO 2 authentication</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/ssh-support-with-fido-2-authentication/m-p/1295623#M17</link>
      <description>&lt;P&gt;Hi @ba31 ba31​&amp;nbsp;&lt;/P&gt;&lt;P&gt;Thank you for engaging with the community! Since two of our members have shared solutions to your question, could you please let us know if any of them have resolved your issue? If so, please consider marking the most helpful response as “Select as Best”- this helps others with similar questions find the right answer quickly.&lt;/P&gt;&lt;P&gt;If the question remains unresolved, I recommend submitting a ticket with our support team for further assistance.&lt;/P&gt;&lt;P&gt;Thank you,&lt;/P&gt;&lt;P&gt;Shaked&lt;/P&gt;</description>
      <pubDate>Wed, 11 Feb 2026 10:24:42 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/ssh-support-with-fido-2-authentication/m-p/1295623#M17</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2026-02-11T10:24:42Z</dc:date>
    </item>
    <item>
      <title>Re: SSH support with FIDO 2 authentication</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/ssh-support-with-fido-2-authentication/m-p/1295624#M18</link>
      <description>&lt;P&gt;I do not think SSH token can be locked down to IP address. It seems only supported with RDP file. When you use SSH token it generate PEM/PPK while and it only contains I guess public key that allow to authenticate against SIA .Once SIA expires public key that Public key no longer usable. &lt;/P&gt;</description>
      <pubDate>Wed, 11 Feb 2026 13:57:00 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/ssh-support-with-fido-2-authentication/m-p/1295624#M18</guid>
      <dc:creator>ba31</dc:creator>
      <dc:date>2026-02-11T13:57:00Z</dc:date>
    </item>
  </channel>
</rss>

