<?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: AD Credentials with SSH connections in Privilege Cloud Discussions</title>
    <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/ad-credentials-with-ssh-connections/m-p/1379093#M4305</link>
    <description>&lt;P&gt;Default config uses customised version of putty. Likely you'll need to add putty.exe to Components directory and configure applocker. Can try these settings :&lt;/P&gt;&lt;P&gt;&lt;A alt="https://community.cyberark.com/s/article/How-to-create-a-connection-component-for-PuTTy" href="https://community.cyberark.com/s/article/How-to-create-a-connection-component-for-PuTTy" target="_blank"&gt;https://community.cyberark.com/s/article/How-to-create-a-connection-component-for-PuTTy &lt;/A&gt;&lt;/P&gt;</description>
    <pubDate>Fri, 10 Dec 2021 01:15:25 GMT</pubDate>
    <dc:creator>CyberArkAlumni</dc:creator>
    <dc:date>2021-12-10T01:15:25Z</dc:date>
    <item>
      <title>AD Credentials with SSH connections</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/ad-credentials-with-ssh-connections/m-p/1379090#M4302</link>
      <description>&lt;P&gt;When it comes to using AD Credentials to log onto a Linux server via SSH, I can see two ways of going about it:&lt;/P&gt;&lt;P&gt;1) Duplicate the Windows Domain Account platform, then add the PSM-SSH connector component.&lt;/P&gt;&lt;P&gt;2) Duplicate the Unix via SSH platform, then edit the platform settings to replace the CPM Plug-in ExeName value 'CyberArk.TPC.exe' with 'PMWindows.dll'.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;My first question is:&lt;/P&gt;&lt;P&gt;Is one of the above ways better than the other, and if so why?&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;----------------&lt;/P&gt;&lt;P&gt;The complication I'm finding is that our linux servers expect the username to be presented as 'domain\username' at the logon prompt. If I add an account with 'domain\username' in the Username field, the SSH connection succeeds, but the CPM fails to rotate the password in AD. Alternately if I add the account as 'username' only, SSH connection fails to log in but the password rotates just fine.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;My second question is:&lt;/P&gt;&lt;P&gt;Is there a way I can onboard the accounts as 'username' and then modify the Linux login process for that platform to prepend domain\ to the username?&amp;nbsp;&lt;/P&gt;&lt;P&gt;In a web-connector this would look something like “UserName &amp;gt; wlife\{username} (SearchBy=Id)” in the web form settings. I can't find an equivalent in the PSM-SSH connector.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;I've searched high and low for an answer to this, the closest match I can find is this page of doco which talks about modifying the /etc/opt/CARKpsmp/components/components.conf file. https://docs.cyberark.com/Product-Doc/OnlineHelp/PAS/Latest/en/Content/PASIMP/Configuring-Customized-Credentials-Prompt-in-PSMP.htm?TocPath=Administration%7CComponents%7CPrivileged%20Session%20Manager%20for%20SSH%7CPSM%20for%20SSH%20Configuration%7C_____25&lt;/P&gt;&lt;P&gt;However, that doesn't fit my situation as this connection isn't going via a PSMP server. It's just the standard PSM-SSH that you get from a PSM server.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Specifically, my connection path is:&lt;/P&gt;&lt;P&gt;PVWA Cloud portal &amp;gt; HTML5 Gateway &amp;gt; Secure Tunnel &amp;gt; PSM server &amp;gt; SSH to target server.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;This discussion (https://community.cyberark.com/s/question/0D52J00007BwKUDSA3/psmssh-for-ad-user?t=1638937702336) also does not answer my situation.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;---------&lt;/P&gt;&lt;P&gt;As we're using AD credentials for linux servers, we expect the same credential to be used across multiple servers. This can be handled by onboarding the account multiple times and using a password group, but I'd consider it far more tidy to add the 'Remote machine access (optional)' property to the platform. Weirdly this property doesn't seem to show up anywhere in platform settings, not even on the Windows Domain Accounts platform.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;My third question is:&amp;nbsp;&lt;/P&gt;&lt;P&gt;Is there a way to add the 'Remote machine access' property to other platforms, and if so, is it possible for SSH connections to reference it?&lt;/P&gt;</description>
      <pubDate>Wed, 08 Dec 2021 04:42:33 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/ad-credentials-with-ssh-connections/m-p/1379090#M4302</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2021-12-08T04:42:33Z</dc:date>
    </item>
    <item>
      <title>Re: AD Credentials with SSH connections</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/ad-credentials-with-ssh-connections/m-p/1379091#M4303</link>
      <description>&lt;P&gt;First: I prefer option number 1 (add PSM-SSH to the Windows platform), because you need to change fewer things than option 2.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Second: This should help --&amp;gt; https://community.cyberark.com/s/question/0D52J00008L6fVbSAJ/how-to-pass-domainusername-in-psmssh-not-psmp&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Third: Yes, PSM connection components can use it as the "PSMRemoteMachine" parameter (usually in place of the "Address" parameter). Afaik most built-in CCs like PSM-RDP and PSM-SSH already do that.&lt;/P&gt;</description>
      <pubDate>Wed, 08 Dec 2021 10:22:37 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/ad-credentials-with-ssh-connections/m-p/1379091#M4303</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2021-12-08T10:22:37Z</dc:date>
    </item>
    <item>
      <title>Re: AD Credentials with SSH connections</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/ad-credentials-with-ssh-connections/m-p/1379092#M4304</link>
      <description>&lt;P&gt;First point: Your reasoning makes sense. I'll try doing it both ways if for no purpose other than for my own education.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Second point: I'm struggling with this. It looks like what I need, but it's not working.&lt;/P&gt;&lt;P&gt;I duplicated the PSM-SSH connector and updated ClientApp to the below per your instruction:&lt;/P&gt;&lt;OL&gt;&lt;LI&gt;"putty.exe" -ssh "{LogonDomain}\{UserName}"@"{PSMRemoteMachine}" -pw "{Password}"&lt;/LI&gt;&lt;/OL&gt;&lt;P&gt;The connection appeared to be ignoring the changes. Then I noticed the comment about CommandLine, so I updated 'ClientInvokeType'&amp;nbsp;to CommandLine.&lt;/P&gt;&lt;P&gt;Now I get an error upon connecting stating: &lt;/P&gt;&lt;P&gt;PSMSR113E [afc5409c-17f6-43f6-a3ed-06f6c7fd4420]&lt;/P&gt;&lt;P&gt;Failed to create process "putty.exe". Code: 2&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;My theory is that this is because putty.exe isn't in the \CyberArk\PSM\Components directory but that begs the question; how is PSM-SSH able to launch putty in the first place when that file doesn't actually exist anywhere that I can find.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Third point: Thanks, I've got that part working beautifully.&lt;/P&gt;</description>
      <pubDate>Thu, 09 Dec 2021 10:10:56 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/ad-credentials-with-ssh-connections/m-p/1379092#M4304</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2021-12-09T10:10:56Z</dc:date>
    </item>
    <item>
      <title>Re: AD Credentials with SSH connections</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/ad-credentials-with-ssh-connections/m-p/1379093#M4305</link>
      <description>&lt;P&gt;Default config uses customised version of putty. Likely you'll need to add putty.exe to Components directory and configure applocker. Can try these settings :&lt;/P&gt;&lt;P&gt;&lt;A alt="https://community.cyberark.com/s/article/How-to-create-a-connection-component-for-PuTTy" href="https://community.cyberark.com/s/article/How-to-create-a-connection-component-for-PuTTy" target="_blank"&gt;https://community.cyberark.com/s/article/How-to-create-a-connection-component-for-PuTTy &lt;/A&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 10 Dec 2021 01:15:25 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/ad-credentials-with-ssh-connections/m-p/1379093#M4305</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2021-12-10T01:15:25Z</dc:date>
    </item>
    <item>
      <title>Re: AD Credentials with SSH connections</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/ad-credentials-with-ssh-connections/m-p/1379094#M4306</link>
      <description>&lt;P&gt;for you query regrading domain\username , you can  try adding logon to : parameter at platform level .&lt;/P&gt;</description>
      <pubDate>Fri, 10 Dec 2021 09:58:46 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/ad-credentials-with-ssh-connections/m-p/1379094#M4306</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2021-12-10T09:58:46Z</dc:date>
    </item>
    <item>
      <title>Re: AD Credentials with SSH connections</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/ad-credentials-with-ssh-connections/m-p/1379095#M4307</link>
      <description>&lt;P&gt;I appear to have it almost fully working now. However, when closing the session by typing ctrl-d I'm met with an error code psmsr483e &amp;nbsp;&amp;lt;Session Unique Identifier&amp;gt; Failed to stop thread &amp;lt;thread&amp;gt;.&lt;/P&gt;&lt;P&gt;Checking session logs shows that the recording either never started or didn't save (0KB).&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Yet if I close the session by simply closing the HTML5 browser tab, the recording works (sometimes, but not always) and is playable.&lt;/P&gt;&lt;P&gt;What makes this particularly weird is that I can start a session, start active monitoring of that session, end it with ctrl-d and still find that the recording has not saved.&lt;/P&gt;&lt;P&gt;There is very little detail available on PSMSR483E, other than this previous question: &lt;A alt="https://community.cyberark.com/s/question/0D52J00006QY4vO/when-user-tried-to-connect-target-machine-then-getting-below-error-psmsr483e-session-unique-identifier-failed-to-stop-thread-thread" href="https://community.cyberark.com/s/question/0D52J00006QY4vO/when-user-tried-to-connect-target-machine-then-getting-below-error-psmsr483e-session-unique-identifier-failed-to-stop-thread-thread" target="_blank"&gt;Question Detail (force.com)&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;</description>
      <pubDate>Mon, 13 Dec 2021 06:59:33 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/ad-credentials-with-ssh-connections/m-p/1379095#M4307</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2021-12-13T06:59:33Z</dc:date>
    </item>
    <item>
      <title>Re: AD Credentials with SSH connections</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/ad-credentials-with-ssh-connections/m-p/1379096#M4308</link>
      <description>&lt;P&gt;Nevermind. Changing the ConnectionComponentInitTimeout from 0 (infinite) to 900000 (15 minutes) seems to have resolved that. Somehow.&lt;/P&gt;&lt;P&gt;I'd love to understand this, but understanding is less important than it working.&lt;/P&gt;</description>
      <pubDate>Mon, 13 Dec 2021 07:39:59 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/ad-credentials-with-ssh-connections/m-p/1379096#M4308</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2021-12-13T07:39:59Z</dc:date>
    </item>
    <item>
      <title>Re: AD Credentials with SSH connections</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/ad-credentials-with-ssh-connections/m-p/1379097#M4309</link>
      <description>&lt;P&gt;In case anyone else finds this article and wants the whole solution, know that enabling a Linux connector which can add the domain\ to the username takes quite a few steps.&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;As pointed out by F.Lee, CyberArk's "SSH" connector is a modified version of putty which doesn't accept customised input. Therefore you must install your own copy of the standard putty client. We'll treat that as the first stage.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Stage 1, prepare the PSM servers:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Install putty&lt;/LI&gt;&lt;LI&gt;Copy putty.exe from the install directory to C:\Program Files (x86)\CyberArk\PSM\Components&lt;/LI&gt;&lt;LI&gt;Add the following line to C:\Program Files (x86)\PSM\Hardening\PSMConfigureAppLocker.xml&lt;/LI&gt;&lt;LI&gt;&amp;lt;Application Method="Publisher" Path="C:\Program Files (x86)\CyberArk\PSM\Components\PuTTY.exe" Type="Exe" Name="PuTTY"/&amp;gt;&lt;/LI&gt;&lt;LI&gt;Run C:\Program Files (x86)\PSM\Hardening\PSMConfigureAppLocker.ps1 in an admin level powershell window.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Stage 2, prepare the Connector Component:&lt;/P&gt;&lt;P&gt;Log into PVWA, and switch to System Configuration (I can never remember the PAS way of getting there. Administration &amp;gt; Options? Something like that. It's hidden in Privilge Cloud so you have to just edit the address bar to PasswordVault/v10/Classic/System.aspx) and edit the Options.&lt;/P&gt;&lt;P&gt;Expand Connection Components, and create a copy of PSM-SSH. We'll call it PSM-Putty.&lt;/P&gt;&lt;P&gt;Edit the target settings of this component as follows:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Protocol: SSH&lt;/LI&gt;&lt;LI&gt;ClientApp: "putty.exe" -ssh "{LogonDomain}\{UserName}"@"{PSMRemoteMachine}" -pw "{Password}"&lt;/LI&gt;&lt;LI&gt;ClientDispatcher: Irrelevant&lt;/LI&gt;&lt;LI&gt;ClientInvokeType: CommandLine&lt;/LI&gt;&lt;LI&gt;ConnectionComponentInitTimeout: 900000&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;Save these settings.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Note that the timeout of 900000 is 15 minutes. Setting it to 0 (infinite) should theoretically work, but I encountered errors with recordings.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Stage 3, create the platform:&lt;/P&gt;&lt;P&gt;For the platform, you can start either from a Windows platform or a *NIX platform. the *NIX platform just takes a bit more effort. I personally find it to be the more logical starting point since this is ultimately a *NIX connector, just using credentials sourced from Active Directory. Instructions are written on that basis.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Duplicate Unix via SSH, call it something like Unix via Putty&lt;/P&gt;&lt;P&gt;Manage the PSM connectors for this platform, disassociate PSM-SSH. Associate PSM-Putty. Save changes.&lt;/P&gt;&lt;P&gt;Edit the platform as follows:&lt;/P&gt;&lt;P&gt;Add a Property under UI &amp;amp; Workflow\Properties\Optional&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Name: LogonDomain&lt;/LI&gt;&lt;LI&gt;ResolveFrom: Address&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Navigate to Connection Components. Set 'PSMConnectorDefault' to 'PSM-Putty' or whatever you called the connector.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Expand your PSM-Putty connector, Add Override User Parameters. Add a parameter with the following details.&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Name: PSMRemoteMachine&lt;/LI&gt;&lt;LI&gt;DisplayName: &amp;lt;Blank&amp;gt;&lt;/LI&gt;&lt;LI&gt;Visible: Yes&lt;/LI&gt;&lt;LI&gt;Type: CyberArk.PasswordVault.Web.TransparentConnection.RemoteMachineUserParameter, CyberArk.PasswordVault.Web&lt;/LI&gt;&lt;LI&gt;Required: Yes&lt;/LI&gt;&lt;LI&gt;Value: &amp;lt;Blank&amp;gt;&lt;/LI&gt;&lt;LI&gt;EnforceInDualControlRequest: No&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Navigate to Automatic Password Management\CPM Plug-in. Change the DllName to PMWindows.dll&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Stage 4, onboard an account. You'll notice that it looks more like onboarding a standard windows account than a standard *NIX account. Put the domain into the "Log On To (optional)" field. Add the linux server(s) to the "Remote machine access (optional) field".&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Stage 5, cross all of your fingers and toes for good luck then test your connection &lt;span class="lia-unicode-emoji" title=":grinning_face:"&gt;😀&lt;/span&gt; &lt;/P&gt;</description>
      <pubDate>Mon, 13 Dec 2021 08:26:58 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/ad-credentials-with-ssh-connections/m-p/1379097#M4309</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2021-12-13T08:26:58Z</dc:date>
    </item>
    <item>
      <title>Re: AD Credentials with SSH connections</title>
      <link>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/ad-credentials-with-ssh-connections/m-p/1379098#M4310</link>
      <description>&lt;P&gt;Updated version of 1_bwooding’s answer above, but correcting the session audit configuration to allow the component to initialise correctly.&amp;nbsp;The 900000 timeout below was crashing the sessions after 15 minutes.&amp;nbsp;This method should prevent that.  With huge thanks to 1_bwooding as well - theirs was a great answer:&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;B&gt;Stage 1, prepare the PSM servers:&lt;/B&gt;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Download putty.exe (32-bit, as 64-bit cannot be launched by PSM) from reliable source.&amp;nbsp;No need to run an installer&lt;/LI&gt;&lt;LI&gt;Place/copy putty.exe into “C:\Program Files (x86)\CyberArk\PSM\Components”&lt;/LI&gt;&lt;LI&gt;Add the following line to “C:\Program Files (x86)\PSM\Hardening\PSMConfigureAppLocker.xml”&lt;/LI&gt;&lt;LI&gt;&amp;lt;Application Method="Hash" Path="C:\Program Files (x86)\CyberArk\PSM\Components\putty.exe" Type="Exe" Name="putty"/&amp;gt;&lt;/LI&gt;&lt;LI&gt;Run “C:\Program Files (x86)\PSM\Hardening\PSMConfigureAppLocker.ps1” in an admin level powershell window.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;B&gt;Stage 2, prepare the Connector Component:&lt;/B&gt;&lt;/P&gt;&lt;P&gt;Go to Administration &amp;gt; Configuration Options&lt;/P&gt;&lt;P&gt;Expand Connection Components, and create a copy of PSM-SSH. We'll call it PSM-Putty.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Edit the Target Settings of this component as follows:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Protocol: SSH (should be already set to this)&lt;/LI&gt;&lt;LI&gt;ClientApp: "putty.exe" -ssh "{LogonDomain}\{UserName}"@"{PSMRemoteMachine}" -pw "{Password}"&lt;/LI&gt;&lt;LI&gt;ClientDispatcher: Irrelevant&lt;/LI&gt;&lt;LI&gt;ClientInvokeType: CommandLine&lt;/LI&gt;&lt;LI&gt;ConnectionComponentInitTimeout: 0&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;In Target Settings &amp;gt; Supported Capabilities&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Remove “SSHTextRecorder” and “SSHKeystrokesAudit”&lt;/LI&gt;&lt;LI&gt;Now right click “Supported Capabilities” and add 2 new Capabilities named “KeystrokesAudit” and “KeystrokesTextRecorder”&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;(Note: changing these Capabilities allows the Component to initialise fully, and will prevent the errors seen on closing the session if ConnectionComponentInitTimeout is set to 0.&amp;nbsp;Setting to 900000 only masks the problem, and sessions would crash after 15 minutes without this change.&amp;nbsp;This also enables the Keystroke recording to work successfully which you can then find in Privileged Session monitoring)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;Finally right click the Component User Parameters and Add a parameter, then edit the details:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Name: PSMRemoteMachine&lt;/LI&gt;&lt;LI&gt;DisplayName: &amp;lt;Blank&amp;gt;&lt;/LI&gt;&lt;LI&gt;Value: &amp;lt;Blank&amp;gt;&lt;/LI&gt;&lt;LI&gt;Visible: Yes&lt;/LI&gt;&lt;LI&gt;Required: Yes&lt;/LI&gt;&lt;LI&gt;Type: CyberArk.PasswordVault.Web.TransparentConnection.RemoteMachineUserParameter, CyberArk.PasswordVault.Web&lt;/LI&gt;&lt;LI&gt;EnforceInDualControlRequest: No&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;(Note: I prefer to add this parameter here rather than in the Platform specific Override User Parameters. &amp;nbsp;This way the Component can be re-used more easily, but the effect is the same)&lt;/P&gt;&lt;P&gt;Ensure to save all these settings.&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;B&gt;Stage 3, create the platform:&lt;/B&gt;&lt;/P&gt;&lt;P&gt;For the platform, you can start either from a Windows platform or a *NIX platform.&amp;nbsp;These instructions assume starting with a Windows platform (as 1_bwooding has already described the other way)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Duplicate “Windows Domain Accounts”, call it something like “SSH-putty-domain”&lt;/LI&gt;&lt;LI&gt;Manage the PSM connectors for this platform, and disassociate PSM-RDP. Associate PSM-Putty. Save changes.&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;OPTIONAL - Edit the platform as follows:&lt;/P&gt;&lt;UL&gt;&lt;LI&gt;Change General Properties &amp;gt; PlatformBaseType from “Window” to “Unix”&lt;/LI&gt;&lt;/UL&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;(Note: This moves the platform into the *NIX group instead of the Windows group for better searching)&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;B&gt;Stage 4, onboard an account.&lt;/B&gt;&lt;/P&gt;&lt;P&gt;You'll notice that it looks more like onboarding a standard windows account than a standard *NIX account. Put the domain fqdn into the “Address” field and the domain shortname into the "Log On To (optional)" field. Add the Linux server(s) to the "Remote machine access (optional) field".&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&amp;nbsp;&lt;/P&gt;&lt;P&gt;&lt;B&gt;Stage 5,&lt;/B&gt;&lt;/P&gt;&lt;P&gt;Cross all of your fingers and toes for good luck then test your connection &lt;span class="lia-unicode-emoji" title=":grinning_face:"&gt;😀&lt;/span&gt;&lt;/P&gt;</description>
      <pubDate>Fri, 08 Dec 2023 13:53:51 GMT</pubDate>
      <guid>https://live.paloaltonetworks.com/t5/privilege-cloud-discussions/ad-credentials-with-ssh-connections/m-p/1379098#M4310</guid>
      <dc:creator>CyberArkAlumni</dc:creator>
      <dc:date>2023-12-08T13:53:51Z</dc:date>
    </item>
  </channel>
</rss>

