PSMP Error: PSPSD072E Perform session error occurred. Reason: PSPSD033E Error receiving PSH For SSH server response (Extra information: [076E Password object was not found (Diagnostic Info: 5).

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

PSMP Error: PSPSD072E Perform session error occurred. Reason: PSPSD033E Error receiving PSH For SSH server response (Extra information: [076E Password object was not found (Diagnostic Info: 5).

L4 Transporter

When try connect to TS with PSMP get error:

PSPSD072E Perform session error occurred. Reason: PSPSD033E Error receiving PSH For SSH server response (Extra information: [076E Password object was not found (Diagnostic Info: 5). Please check that there is

а password object that answers your query in the Vault and that both the PSM SSH Proxy and the Vault user have the appropriate permissions needed in order to use the password). [1]). (codes: -1, 1)

Field_Content_versions_oct20__0682J000006yDl6QAE.gif

 

i use IPV4 address for connection

 

With PSM all good, i can connect without any problem

 

Answers https://community.cyberark.com/s/feed/0D52J00006zcS4qSAE does not help

 

Solutions 00004018

Does not help too

 

 

 

1 accepted solution

Accepted Solutions

L4 Transporter

Problem is solved. To solve this problem i change address from domain name of domain controller to domain, for examle i change DC.bnppua.net.intra to BNPPUA (CPM steel able to manage password with this configuration) and in connection link via PSMP i use this link:

 

<Vault username>@<Target username>#<Domain>@<address TS>@<PSMP address>

 

My link look like this:

 

Administrator@LinuxAdmin01#[email protected]@192.168.0.3

 

This solution i get from CyberArk support.

 

Thank you everyone for help

View solution in original post

6 REPLIES 6

L4 Transporter

Hi @Yaroslav Malookiy​ I've reproduced this error by passing an invalid user name or invalid target server in the string and get the same error as you've mentioned. Not that this is the exact reason, but is the target server reachable over 22 from your client machine. It could be working from the PSM as 22 could be open from PSM to target.

user@TargetaAccount@Targetserver@PSMPServer

L4 Transporter

Problem is solved. To solve this problem i change address from domain name of domain controller to domain, for examle i change DC.bnppua.net.intra to BNPPUA (CPM steel able to manage password with this configuration) and in connection link via PSMP i use this link:

 

<Vault username>@<Target username>#<Domain>@<address TS>@<PSMP address>

 

My link look like this:

 

Administrator@LinuxAdmin01#[email protected]@192.168.0.3

 

This solution i get from CyberArk support.

 

Thank you everyone for help

L3 Networker

L2 Linker

Additionaly you shoud to check registr because PSM a case sensetive. Error will be same if you will use not propertly registr of account name

In Addition to that, If we are using multiple PSMP servers with load balancer we need to use the below syntax

 

<Vault username>@<Target username>#<Domain>@<address TS>@<PSMP LB DNS Record>

L3 Networker

Hi,

 

We have a similar requirement , but in our case its a local SSH accounts. So the above mentioned approach is not working.

So someone let us know how to proceed with single local accounts for different servers.

  • 1 accepted solution
  • 10989 Views
  • 6 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!