When the user requests credentials from the vault how are these transferred to the target machine when a connection starts?

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

When the user requests credentials from the vault how are these transferred to the target machine when a connection starts?

L1 Bithead

I know the PSMConnect user normally connects to the target machine and has its own creds or the same for a shadow user. 

 

Does the PSMConnect / Shadow User use these credentials to connect? I am confused how the vault credentials get to the target machines.

 

Thanks

1 accepted solution

Accepted Solutions

L7 Applicator

Afaik, this is how it works:

  1. When you click "Connect" in PVWA, a RDP file is downloaded, which contains some kind of "connection id" as the username
  2. At the same time, PVWA stores information about you and which account you are connecting to in a specific safe under the same "connection id"
  3. When your RDP connection arrives at the PSM, it checks this safe to find out which connection component it should launch
  4. PSM retrieves the target account's credentials under your username using its "gateway account" (using the "impersonation" Vault feature)
  5. PSM starts the connection component in the shadow user profile and passes the target account's credentials via environment variables (the password is encrypted)
  6. The relevant connection component executable (for example Chrome dispatcher, PSM SSH dispatcher, etc...) reads the environment variables and opens the connection to the target system

 

If you are using PSM HTML5 GW, the PVWA doesn't give you an RDP file, it redirects you to the PSM HTML5 GW website, which then opens the RDP connection to PSM.

And if you are using Distributed Vaults, the process of passing the "id" between PVWA->PSM is slightly different because it involves the message queuing mechanism.

View solution in original post

2 REPLIES 2

L7 Applicator

Afaik, this is how it works:

  1. When you click "Connect" in PVWA, a RDP file is downloaded, which contains some kind of "connection id" as the username
  2. At the same time, PVWA stores information about you and which account you are connecting to in a specific safe under the same "connection id"
  3. When your RDP connection arrives at the PSM, it checks this safe to find out which connection component it should launch
  4. PSM retrieves the target account's credentials under your username using its "gateway account" (using the "impersonation" Vault feature)
  5. PSM starts the connection component in the shadow user profile and passes the target account's credentials via environment variables (the password is encrypted)
  6. The relevant connection component executable (for example Chrome dispatcher, PSM SSH dispatcher, etc...) reads the environment variables and opens the connection to the target system

 

If you are using PSM HTML5 GW, the PVWA doesn't give you an RDP file, it redirects you to the PSM HTML5 GW website, which then opens the RDP connection to PSM.

And if you are using Distributed Vaults, the process of passing the "id" between PVWA->PSM is slightly different because it involves the message queuing mechanism.

L2 Linker

The Connection chain is as follows:

 

RDP file created from PVWA to connect to the PSM server this uses the PSMConnect user

 

PSMinitSession opens an RDP file from the PSM Server to the target using the Privilege Account

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