Different behaviors when using Unix via SSH - Keys

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

Different behaviors when using Unix via SSH - Keys

L2 Linker

Hello! I wanted to understand the behavior of the SSH connector with Keys.

I embedded an account with a private key, and CPM works normally, successfully verifying the key and setting it to "compliance".

The issue is that when a connection attempt is made, it returns a failure. The error in question is: SH019E PSMSSHClient Initialization failed. Code -1.

This same PSM is working normally on other connections. I found a community thread discussing the key format, stating that "-----BEGIN OPENSSH PRIVATE KEY-----" is not supported, only "----BEGIN RSA PRIVATE KEY-----".

 

I requested the infrastructure team to build a new key in the correct format, but I wanted to understand if this is really the cause of the error and how CPM is able to verify it.

2 REPLIES 2

L7 Applicator

The cpm uses the CyberArk TPC framework to verify and change passwords .

 

The PSM uses Plink to connect to target accounts .

 

TPC can handle various key formats , plink can't .

This explains the difference in behavior and reinforces the action of generating a new key in the correct format. Thank you!

  • 134 Views
  • 2 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!