Connection String for PSM-Web Connections in Microsoft Remote Desktop Connection Manager

cancel
Showing results for 
Show  only  | Search instead for 
Did you mean: 

Connection String for PSM-Web Connections in Microsoft Remote Desktop Connection Manager

L2 Linker

We use Microsoft Remote Desktop Connection Manager and it works great for PSM-RDP connections; however, we're using more PSM-Web connections, but can't figure out how to use the connection string for websites, like Facebook, Instagram, Entra, Exchange Online, etc. We can make it work when using the Connect button in the PVWA, and that downloads a .rdp file, so there has to be a way to make this work in MSRDCM. Any thoughts?

12 REPLIES 12

L7 Applicator

It looks like you’re trying to configure PSM-Web connections for websites but are having trouble with the connection string. Here are some steps to help you out:

  1. Install the necessary components: Ensure you have the latest browser drivers installed for the brows....
  2. Create a new web connection component: In the PVWA (Privileged Vault Web Access), navigate to Administration > Configuration Options > Connection Components. Here, you can create a new connection component based on a default generic connection component1.
  3. Edit the connection settings: Customize the settings for your specific web application. This includes editing the WebForm settings and client-specific settings1.
  4. Test the connection: Once configured, test the connection to ensure it works as expected2.

 

L2 Linker

All of that is in place and we can connect to websites, but only through the Connect button in the PVWA. My question is, how do we construct a connection string in Microsoft Remote Desktop Connection Manager so we can connect to websites from something other than the PVWA?

 

Something like:

psm /u [email protected] /a https://portal.azure.com /c PSM-MS-AzurePortal

or

psm /u fbusername /a https://www.facebook.com.com /c PSM-Facebook

or

psm /u administrator /a https://pvwa.contoso.com/PasswordVault/v10 /c PSM-PVWA

L7 Applicator

The command you provided is a valid string to connect to the Azure portal using CyberArk’s Privileged Session Manager (PSM). Here’s a breakdown of the command:

  • psm: This is the command to initiate a PSM session.
  • /u [email protected]: This specifies the username for the session.
  • /a https://portal.azure.com: This is the address of the target application, in this case, the Azure portal.
  • /c PSM-MS-AzurePortal: This specifies the connection component to be used, which is configured for the Azure portal.

 

L2 Linker

When I use that string for any of the examples provided, I get "Failed to establish connection. Reason: 1062E The requested account does not exist in the vault, or you do not have the appropriate permissions to use it." I'm the administrator, so I know I have the corect permissions on each safe containing the accounts, so it seems like it can't find the account to check out (GlobalAdmin, fBusername, Administrator (CyberArk local Admin), because none of those accounts are entered using our domain name. How do I specify those names correctly so the PSM can find them?

L2 Linker

Maybe this isn't supported except through the PVWA, which doesn't make any sense. If the PVWA Connect button can figure out a non-domain account, why can't the PSM figure it out?

 

https://community.cyberark.com/s/article/KI00022852

Have you gotten an answer to your question?

In the meantime, I've forwarded your question to our PAM Self-Hosted Resource Center to get input from our PAM experts.

 

You can track the progress here:

https://community.cyberark.com/s/feed/0D5Ht0000AT3abHKQR

 

Thanks,

Niv

I have not gotten an answer to the question

I see 2 potential issues with what you are trying to do:

 

If the username in the "RDP start program" parameter contains the "@" character, PSM will treat it in a particular way. For example, if you specify "psm /u bob@domain /a somehost /c PSM-RDP", the PSM will not look for an account with the username "bob@domain" and the address "somehost". Instead, PSM will look for an account with the username "bob", the address "domain", if that exists, try to connect to the targethost "somehost" with the PSM-RDP connection component.I don't know if there is a way around that behavior.

 

I have never tested the PSM direct connect feature with an address that's an actual URL. If you specify the address in the "RDP start program" parameter as "/a blabla" instead of "/a https://blabla/login", it may work, but you will have to tweak the connection component a bit to add the "https://" part and "/login" part.

The documentation states that the username and address need to match what's entered in the PVWA account. When using the PVWA 'Connect' button, it hashes things correctly to create an RDP file, download it, and connects successfully, so clearly it can work; however, when using a connection string that gets passed to the PSM server, there's a breakdown in how it constructs everything. Even if I specify /a portal.azure.com, it fails. So, to reiterate, in my example, the account in the PVWA has the username entered as [email protected] and an address of https://portal.azure.com. Everything works with the 'Connect' button. Why does it know how to construct that correctly but from the connection string, it fails?

The RDP file that's downloaded when you use the "Connect" button on an account via PVWA uses a completely different way of transferring the connection parameters to PSM than when you connect via an RDP client with the "psm /u .. /a .. /c .." syntax.

 

Afaik, the default behavior of PSM is to interpret the @ symbol in the "/u user@domain" parameter value as the domain-seperator, and not as part of the account's username - and I don't think that this can be changed.

I understand that it's different, just wondering why it has to be. It sucks to have people use RDCMan for most things, then tell them they have to use a different method for web access. Seems like a simple problem the developers could solve.

I agree, CyberArk should make this feature be more configurable in detail. And also document it better, so this behavior is way more obvious.

 

A potential workaround for your issue could be to define the account in a different way.

Instead of the account being defined as:

 

... you define it as:

  • Username: GlobalAdmin
  • Address: portal.azure.com
  • Domain: contoso.onmicrosoft.com

 

And in the PSM connection component you reference the username instead of "{Username}" by using "{Username}@{LogonDomain}".

 

Then, the connection via RDCMan with the "psm /u GlobalAdmin /a portal.azure.com /c PSM-MS-AzurePortal" syntax should work.

 

 

  • 932 Views
  • 12 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!