SSH PSM why does it not just work?

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

SSH PSM why does it not just work?

L3 Networker

After having to fix an External IDP issue we now need to get SSH for PSM working with domain accounts using UPNs not just usernames.

 

Vault user [email protected]

with some additional config on the server the following should work but doesn't

 

[email protected]#TargetAccount#TargetSever@PSMSSHClusterName

 

We reach the login prompt for the Vault users password but then get authentication failed as below

 

Using username "[email protected]#target#Server".

Keyboard-interactive authentication prompts from server:

Enter Password

Authentication (login or challenge) has failed. Please try again or contact your system administrator.

 

Its like the SSH servers are unable to authenticate the domain account with CyberArk. Annoyingly this all worked on our previous on prem setup but since moving to new servers for PrivCloud, it worked with just the username until we had to block authentication with SamAccountnames as it bypassed Okta for website logins which got security very excited.

Now we can't use SSH because computer says no.

 

I am sure there is a doc that covers this but fed up with trying to find it so if anyone has any pointers that would be great.

9 REPLIES 9

L7 Applicator

https://community.cyberark.com/s/article/PSM-for-SSH-Syntax-Cheat-Sheet

 

Does

[email protected]%TargetAccount%TargetSever@PSMSSHClusterName

 

Work?

L6 Presenter

Hi @Jeremy Roberts​,

 

please check the document PSM for SSH Syntax Cheat Sheet.

 

Nino

L7 Applicator

Hi @Jeremy Roberts​ 

 

To isolate an issue with UPN, can you please try testing local account via PSMP ?

 

 

L3 Networker

That cheat sheet seems to be full of contradictions and lies

It says out of the box this will work (assuming no changes anywhere)

[domain-username]@[domain-domain]@[targetuser]@[targetaddress]@[PSM for SSH address]

but that never worked with a Vault user account that is a domain account, too many @.

 

It also suggests

VU@VD%TU%TA@PSM but I just get "Failed to connect to the target"

 

At least with # I get a password request even if it does not accept the password that is supplied.

 

I may need to get in to the config on the SSH server and see what got configured. fortunately Puuty from the web Gui still works.

 

For the local account i assume you meen a local one in CyberArk, I'll have to set something up and grant access.

 

L3 Networker

/etc/opt/CARKpsmp/components/components.conf

already contained

AdditionalDelimiter=%

So the % should work but doesn't

 

I added

AdditionalDelimiter=#

 

Makes no difference.

 

I have also checked for account activity and there is none, no failed attempts, so must be something not passing/parsing the user name somewhere.

L3 Networker

using a local account and format below just keeps requesting the password.

LocalVaultUser@TargetAccount@TargetSever@PSMSSH

 

Hi @Jeremy Roberts​ 

 

As the community has not yet provided an answer to this question for some time, could you kindly share if you were able to resolve the issue, and how? Your solution could help other community members who may face a similar issue.

If the issue is still relevant, I would advise raising a ticket with our Support team for further assistance.

 

Thanks, Liad

Not had time to investigate further.

Will need to do an update on the servers so will look in to it then.

 

 

L4 Transporter

Hi Jez

 

For PSM-SSH, when an external provider such as Okta is completing the Authentication process, you would need to make use of MFA Caching. - https://docs.cyberark.com/ispss-deployment/latest/en/content/pasimp/mfa-caching.htm?Highlight=MFA%20Caching

 

Thanks

 

Michael

 

 

 

  • 275 Views
  • 9 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!