PSM-WinSCP question

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 
Announcements

Welcome Idira to LIVEcommunity!

Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.

Meet Idira

PSM-WinSCP question

L4 Transporter

Hi,

 

We are trying to use/add PSM-WinSCP to a custom multiprotocol platform, but I think that it is only using the address of the account as target.

 

I tried adding a PSMRemoteMachine property to the platform level, and it does popup the window asking for the remote machine, but it' kind of unclear whether the PSM-WinSCP is actually using the hostname I enter into that window.

 

Then, I found this ER:

 

https://community.cyberark.com/s/enhancement-request-detail?id=08750000000fxhMAAQ

 

So from that page, I am guessing that that ER has not been implemented yet and that is probably my problem.

 

Does anyone know if that is or is not, the case? Has that ER been implemented (in 10.3, in our case)?

 

Thanks,

Jim

1 accepted solution

Accepted Solutions

L1 Bithead

Hi @James Lum​ 

 

You can also try to edit the connection component for your PSM-WinSCP connector.

 

Under its Target Settings -> Client Specific -> DispatcherParameters

 

----

 

{Address}

{Username}

{Password}

[{PSMClientApp}]

[{Port}]

[{FileTransferProtocol}]

[{WindowTimeout}]

[{RestrictiveMode}]

[{AcceptHostKeyInCache}]

 

----

 

Just change the Address to your PSMRemoteMachine parameter.

 

 

Regards,

Francis

View solution in original post

15 REPLIES 15

L4 Transporter

If I recall correctly, in past have encountered similar issue for a customer in v9.5.

OOTB PSM-WinSCP only supports *nix local Auth not domain auth.

 

You can write a CLI Dispatcher quickly I don't remember the exact command. But I did work for me.

L5 Sessionator

The ER is showing a status of "Under consideration" - so not delivered. I voted for it though.

L7 Applicator

You can always check the release notes and see if it is delivered.

L2 Linker

Until such time the ER is part of the environment, you could cook up your own AutoIT script to tell WinSCP where to connect.

L2 Linker

Here's some of the code you could use to get started

; #FUNCTION# ====================================================================================================================

; Name...........: PSMGenericClient_GetSessionProperty

; Description ...: Fetches properties required for the session 

; Parameters ....: None

; Return values .: None

; ===============================================================================================================================

Func FetchSessionProperties() ; CHANGE_ME

if (PSMGenericClient_GetSessionProperty("Username", $TargetUsername) <> $PSM_ERROR_SUCCESS) Then

Error(PSMGenericClient_PSMGetLastErrorString())

EndIf

 

if (PSMGenericClient_GetSessionProperty("Password", $TargetPassword) <> $PSM_ERROR_SUCCESS) Then

Error(PSMGenericClient_PSMGetLastErrorString())

EndIf

 

;if (PSMGenericClient_GetSessionProperty("Address", $TargetAddress) <> $PSM_ERROR_SUCCESS) Then

; Error(PSMGenericClient_PSMGetLastErrorString())

;EndIf

if (PSMGenericClient_GetSessionProperty("PSMRemoteMachine", $TargetAddress) <> $PSM_ERROR_SUCCESS) Then

Error(PSMGenericClient_PSMGetLastErrorString())

EndIf

EndFunc

 

L1 Bithead

Hi @James Lum​ 

 

You can also try to edit the connection component for your PSM-WinSCP connector.

 

Under its Target Settings -> Client Specific -> DispatcherParameters

 

----

 

{Address}

{Username}

{Password}

[{PSMClientApp}]

[{Port}]

[{FileTransferProtocol}]

[{WindowTimeout}]

[{RestrictiveMode}]

[{AcceptHostKeyInCache}]

 

----

 

Just change the Address to your PSMRemoteMachine parameter.

 

 

Regards,

Francis

L4 Transporter

@Francis Bebita​ 

 

Actually I had tried that and it worked!

 

So does that mean the ER was done (in 10.3, at least)?

 

Jim

L7 Applicator

I dont think it is delivered , By changing the address in the dispatcher parameters , you are basically forcing to take the value of the PSMRemoteMachine. Which works in your case but if there is a use case to connect to the target listed under address it will fail.

I believe the address is the domain name and you probably would not have issue in this case.

L3 Networker

no need to change AUTOID script, just 2 places to make the changes, the purpose is to overwrite fix value "Address" with the variable value inputted at prompt "PSMRemoteMachine"

 

  • Under Options > Connection Components > PSM-WinSCP-NEW -> Target Settings -> Client Specific -> DispatcherParameters

{PSMRemoteMachine} .... this is changed from {Address}

{Username}

{Password}

[{PSMClientApp}]

[{Port}]

[{FileTransferProtocol}]

[{WindowTimeout}]

[{RestrictiveMode}]

[{AcceptHostKeyInCache}]​

 

 

  • under the Platform-NEW > UI & Workflows > Connection Components > PSM-WinSCP-NEW > Overrider User Parameters

​

L4 Transporter

Alternatively, you can use WinSCP (on your client) via PSMP available in 10.3 onwards

L0 Member

The solution provided by 955_Francis worked for us. Thanks all!!

L3 Networker

@Kexin Zhang​ , @Andy Goh​ 

is there anyway we can parse username as well ?

we have a requirement where end user uses same account to logon to different servers with different login user format

e.g:

on Server1: username will be {Username}

on Server2: username will be domain\{Username}

on Server3: username will be {Username}@domain.com

 

is there any way we can populate username field as above during runtime (like PSMRemoteMachine) ?

 

 

 

Good job.

Thanks.

L4 Transporter

I have Integrated Linux Server with AD and now using domain account to connect to winscp where Username field is asking for UPN ([email protected]) but I am not able to append (@dell.com) on the WinSCP dispatcher paramenters under Client Specific as this shows error .

PFB code and help me on this -- How to Append after the username

 

{PSMremoteMachine}

 

{Username}

 

{Password}

 

[{PSMClientApp}]

 

[{Port}]

 

[{FileTransferProtocol}]

 

[{WindowTimeout}]

 

[{RestrictiveMode}]

 

[{AcceptHostKeyInCache}]

  • 1 accepted solution
  • 2122 Views
  • 15 replies
  • 0 Likes
Like what you see?

Show your appreciation!

Click Like if a post is helpful to you or if you just want to show your support.

Click Accept as Solution to acknowledge that the answer to your question has been provided.

The button appears next to the replies on topics you’ve started. The member who gave the solution and all future visitors to this topic will appreciate it!

These simple actions take just seconds of your time, but go a long way in showing appreciation for community members and the LIVEcommunity as a whole!

The LIVEcommunity thanks you for your participation!