- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
Our community just got stronger! Explore new identity security resources, connect with experts, and discover more ways to learn and collaborate.
03-04-2026 09:34 AM
Hello,
After upgrading the infrastructure from version 14.2 to 14.6, the PrivateArkClient connection component stopped automatically populating the credentials. When it opens, it only shows the PrivateArk client and the configured Vault.
Anyone had this issue?
03-05-2026 03:44 AM
An update regarding the issue.
To resolve the issue, we replaced the PrivateArkClientDispatcher with the older 14.5 version and also used the previous versions of Eagle.dll and CyberArk.Extensions.Utilities.dll instead of the latest ones.
03-04-2026 11:26 AM
is it possible to share globaconfig data hiding sensitive info?
You upgraded within the server? Also, did you upgrade PA client too? if Not then do please
03-04-2026 03:15 PM
Hey @Bernardo Silva Make sure you're using the version of the plugin from the Marketplace:
https://community.cyberark.com/marketplace/s/#a3550000000EiAbAAK-a3950000000jjT3AAI
If you're using the Digital Vault Plugin, the dispatcher version that comes with 14.6 does not work with the new "PVWA Address" parameter.
03-05-2026 03:12 AM
Hey Sanzy
The config is this:
[CyberArk\PrivateArk\Client\Servers\1******]
ServerName=1*******
ServerInputPortNumber=1858
RequestTimeout=30
AuthMethod=0
NTAuthAgent=
NTAuthAgentKey=
VaultID=*****
DistinguishedName=
UseProxy=0
ProxAddress=
ProxPort=0
ProxProtocol=2
ProxUser=
SessionType=0
CISFGatewayName=
HTTPGatewayName=
ConnectionTimeout=60
UseOnlyHTTP_1_0_InProxy=0
UseOnlyHTTP_1_0_InFirewall=0
NumOfRecordsPerSend=983055
UseConnectionTimeout=0
UseEnhancedSSL=0
UsePreAuthenticatedSession=0
TrustSelfSignedCert=0
Allow3PartyUseSSC=0
I didn´t the understand the question "You upgraded within the server?". The PA client is also updated.
03-05-2026 03:13 AM
Hey pbx,
I tried with both dispatchers, the 14.5 and 14.6. The behavior is the same.
03-05-2026 03:44 AM
An update regarding the issue.
To resolve the issue, we replaced the PrivateArkClientDispatcher with the older 14.5 version and also used the previous versions of Eagle.dll and CyberArk.Extensions.Utilities.dll instead of the latest ones.
03-05-2026 03:44 AM
To resolve the issue, we replaced the PrivateArkClientDispatcher with the older 14.5 version and also used the previous versions of Eagle.dll and CyberArk.Extensions.Utilities.dll instead of the latest ones.
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!

