PSM Connector - "PSMGenericClientWrapper error"

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 Connector - "PSMGenericClientWrapper error"

L0 Member

I have a requirement to directly launch a PowerShell window from PVWA. So, I have developed a custom launcher using an AutoIT script that launches a PowerShell window on PSM Server using target account credentials. This is fully working on my personal lab environment. On trying to deploy the connector in our actual test environment, I am receiving the following error:

 

0682J0000066xijQAA.jpg

 

Which is followed by a time-out error. Does anyone have any suggestions on where to look? The logs are not proving to helpful.

5 REPLIES 5

L5 Sessionator

This could be PSMShadowUser (PSM-****)permission issue. I'm thinking you can try with a tool in SFE ( CyberArk support Portal) called Add-PSMAppLockerRules (Its a powershell script)

 

This tool generally used to investigate applocker issues, but this will open your connector using PSMShadow Users .. so you can easily isolate the issues

 

Also make sure post installations tasks and hardening are properly completed in that psm server.

 

Let me know how it goes !! Good luck

L7 Applicator

I would try to re-run the PSMHardening.ps1 script, this fixes any permission problem with the PSMShadowUsers group.

L4 Transporter

It took me a while to make this work via AutoIT when I was at a different site.

Things to consider

1) Do you want to run powershell window on PSM as the PSM Shadow user just by launching in the AutoIT or with user credentials stored in the vault? If you want to give the user a powershell window with a specific user you'll need to RunAs. https://www.autoitscript.com/autoit3/docs/functions/RunAs.htm. That's extra useful as you could then use a PSRemote connection to a target with it. So you ultimately give users a powershell remotely connected to their target.

2) Have you got PowerShell executables in your applocker rules

3) If you RunAs it could be any arbitrary user so you might want to look at who is allowed to authenticate as a user on the PSM and as an interactive logon, but you don't definitely don't want to allow those users to connect to the computer from the network as that would cause all sorts of security problems

4) Are you OK with users having a powershell window on the PSM, do you want them snooping around your PSM? Perhaps you could consider Start-Transcript to a text file before you make a PS-Remote session. When the user exits the remote session you can see the prompt go back and kick them off the PSM if you monitor the transcript text in AutoIT

Enjoy..

L3 Networker

Also look at your AutoIT script, and you RunAs command. I can see from the screen-shot, the path to the PSMDispatcherUtils.dll has two slashes in front of it. (e.g. \\PSMDispatcherUtils.dll instead of just \PSMDispatcherUtils.dll )

Did you ever find a resolution to this, @Andrew Lawson​ ? I've just run into the same issue and from the tracelog, it appears the PSMConnectorFolder somehow gets an extra backslash:

 

class CPSMConnectionClientBase *  | PSM\PSMServer\PSMConnectionClientBase.cpp(635)        | :: | PSMSR341I [353612b8-78cb-4f3c-b749-4d33a6fdd2d4] Finished parsing the ClientApp parameter. Executable: ["C:\Program Files (x86)\AutoIt3\AutoIt3.exe"] Parameters: ["C:\Program Files (x86)\CyberArk\PSM\Components\\PSMADUCDispatcher.au3" "C:\Program Files (x86)\CyberArk\PSM\Components\\"]

 

If you try to provide a full path in the target settings, it has issues creating the path for the generic wrapper dll. Logic seems to be self-contained on Cyb side, so curious if anyone can shed some light here.

  • 1316 Views
  • 5 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!