Use a variable connection for multiple linux hosts

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

Use a variable connection for multiple linux hosts

L4 Transporter

Brain Trust,

I am looking for directions on how to create a "variable" connection for multiple hosts.

For example, lets say I have a group of 20 Linux servers, all of them having same ssh key. What I want to do in CyberArk is to create one connection but let the user populate the ip address of the specific server, thus effectively creating one connection that can be used for any of the 20 hosts. Do I need to create a platform for this?

Thanks for any suggestions

1 accepted solution

Accepted Solutions

L7 Applicator

https://docs.cyberark.com/Product-Doc/OnlineHelp/PAS/Latest/en/Content/PASIMP/PSMServers.htm?Highlight=PSMRemoteMachine#UNIXDomainNISplatforms

 

This will take care of the PSM side - how users will connect with *one* account in the Vault to *many* targets.

 

The problem with that... since this *one* account will only have *one* actual address value, CPM will only rotate the credentials or SSH priv. key on that *one* Linux server. The way to use one SSH private key on multiple servers, is to create multiple accounts, and then group them - but that will go against your goal of having only one account in the Vault.

 

This means that if you want your users to only see one account and use it to connect to many targets, CPM cannot manage the credentials... *or* manage the credentials in a central place, like a LDAP directory (your Linux boxes must then allow login with LDAP credentials, obviously).

View solution in original post

2 REPLIES 2

L7 Applicator

https://docs.cyberark.com/Product-Doc/OnlineHelp/PAS/Latest/en/Content/PASIMP/PSMServers.htm?Highlight=PSMRemoteMachine#UNIXDomainNISplatforms

 

This will take care of the PSM side - how users will connect with *one* account in the Vault to *many* targets.

 

The problem with that... since this *one* account will only have *one* actual address value, CPM will only rotate the credentials or SSH priv. key on that *one* Linux server. The way to use one SSH private key on multiple servers, is to create multiple accounts, and then group them - but that will go against your goal of having only one account in the Vault.

 

This means that if you want your users to only see one account and use it to connect to many targets, CPM cannot manage the credentials... *or* manage the credentials in a central place, like a LDAP directory (your Linux boxes must then allow login with LDAP credentials, obviously).

L4 Transporter

Hello BernhardB,

Thank you very much for the link and even more so for the one gotcha that this solution comes with. Indeed, it will be useful in case we don't want to rotate key or password.

 

 

 

  • 1 accepted solution
  • 477 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!