Are there additional changes needed to enable the PSM-PrivateArkClient connection component, when storing an account using the new CyberArk Digital Vault platform that was just announced?

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

Are there additional changes needed to enable the PSM-PrivateArkClient connection component, when storing an account using the new CyberArk Digital Vault platform that was just announced?

L1 Bithead

The new account platform shifts away from using the Vault database server's IP address in the account's 'address' field, in favor of using the PVWA server IP (or name), to enable REST API connectivity. However the PSM-PrivateArkClient connection component consumes this address field to establish connectivity, and is failing to find a Vault database on my PVWA server (shocking, I know).

 

Have I missed an update in the last few years to the PrivateArk connection component, or is this an undocumented item that may need to be accounted for when shifting to the newly released CyberArk Digital Vault platform, from the older CyberArk Vault platform that's set to be deprecated at the end of February 2025.

1 accepted solution

Accepted Solutions

L1 Bithead

This behavior was confirmed via a support case. The newly released CyberArk Digital Vault account platform changes the usage of the stored accounts 'address' field, which breaks the existing PSM-PrivateArkClient connection component.

 

The suggested workaround that we implemented, was to modify the first line of the PrivateArkConfigurationData.ini file on the PSM server, such that the IP address used in that first line matches the new value of the stored account (the IP/FQDN of the PVWA server). This ensures the PSM connection component lookup finds a match in the configuration file, and connectivity can continue to utilize the Vault database IP address noted lower in the configuration file under 'ServerName'. Of note, this runs counter to the KB articles related to configuring the PrivateArkClient connection component, which emphasizes that these two values must match.

 

Field_Content_versions_oct20__068Ht00000Vdbi3IAB.png 

It seems that the development of the new account platform moved forward, but the interaction with the PSM connection component for PrivateArk was overlooked. I expect that documentation will need to be updated in the future, or potentially a new PSM Connection component released for PrivateArk to match this new behavior. For now, the workaround above enables us to fully manage the stored local account in the Vault using the new account platform, and retain PSM-hosted PrivateArk connections tied to that account.

View solution in original post

3 REPLIES 3

L7 Applicator

Hi @Richard Jones​ 

 

I would think the PVWA Hostname in ‘address’ filed will not work in this case.

 

Have you tried using Vault IP in the address field ?

 

Please refer to the following KB!

 

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

I believe that's the crux of my issue, the PSM-PrivateArkClient connection component assumes the Vault IP address is in the address field, but the newly released CyberArk Digital Vault account platform, assumes the PVWA IP address is in the address field (a change from the legacy version, which also used the Vault IP). Using the existing connection component, in tandem with the newer account platform, does not work out of the box.

 

New Vault Account Platform (marketplace)

New Vault Account Platform (documentation)

L1 Bithead

This behavior was confirmed via a support case. The newly released CyberArk Digital Vault account platform changes the usage of the stored accounts 'address' field, which breaks the existing PSM-PrivateArkClient connection component.

 

The suggested workaround that we implemented, was to modify the first line of the PrivateArkConfigurationData.ini file on the PSM server, such that the IP address used in that first line matches the new value of the stored account (the IP/FQDN of the PVWA server). This ensures the PSM connection component lookup finds a match in the configuration file, and connectivity can continue to utilize the Vault database IP address noted lower in the configuration file under 'ServerName'. Of note, this runs counter to the KB articles related to configuring the PrivateArkClient connection component, which emphasizes that these two values must match.

 

Field_Content_versions_oct20__068Ht00000Vdbi3IAB.png 

It seems that the development of the new account platform moved forward, but the interaction with the PSM connection component for PrivateArk was overlooked. I expect that documentation will need to be updated in the future, or potentially a new PSM Connection component released for PrivateArk to match this new behavior. For now, the workaround above enables us to fully manage the stored local account in the Vault using the new account platform, and retain PSM-hosted PrivateArk connections tied to that account.

  • 1 accepted solution
  • 230 Views
  • 3 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!