- Access exclusive content
- Connect with peers
- Share your expertise
- Find support resources
07-31-2024 12:11 PM
I'm deploying a Vault 13.2 in Azure on a Windows Server 2019 VM and I modified the CustomScriptExtension in the ARM template to call my custom script hosted in a storage account instead of calling the configure-vault.ps1 from the cyberark github.
My custom script does exactly that, it calls the configure-vault.ps1. Basically I just added an extra step which shouldn't change anything but by doing so the Admin Password somehow changed.
I don't understand how simply calling the configure-vault script from my custom script can cause this result.
08-01-2024 07:02 AM
The problem has been solved!
As expected, there was a problem with my arguments: there's an unwanted comma after the admin password argument which added a comma at the end of the password.
-AdminPass $AdminPass,Special thanks to M@ (CyberArk Community Manager) (CyberArk) for his help in this matter!
07-31-2024 12:17 PM
Hey @Dumitru Zlotea
If you perform the deployment without customizing things to call your script, does it work as expected?
This should at least confirm it's something within your customizations that is causing this.
-Matt
07-31-2024 12:23 PM
Hello,
Yes, the base template works as intended. The problem appears only when I add my script.
07-31-2024 12:25 PM
Great, so what are the details of the script? I'm not really sure how to assist without knowing these details as that's where the issue seems to be.
-Matt
07-31-2024 12:31 PM
Initially the script was to download and install Microsoft Edge as well as download the PrivateArk Client, then call the configure-vault script.
Since I was experiencing that problem, I commented the entirety of the script, leaving only the call to configure-vault.ps1 but I still have the same problem:
param(
[string]$StorageAccountName,
[string]$ContainerName,
[string]$StorageAccountKey,
[string]$AdminPass,
[string]$MasterPass,
[string]$PrimaryOrDR,
[string]$PrimaryVaultIP,
[string]$DRPassword,
[string]$LicenseFileName,
[string]$RecPubFileName,
[string]$VKMName,
[string]$Secret
)
&".\configure-vault.ps1" -AdminPass $AdminPass, -MasterPass $MasterPass -PrimaryOrDR $PrimaryOrDR -PrimaryVaultIP $PrimaryVaultIP -DRPassword $DRPassword -LicenseFileName $LicenseFileName -RecPubFileName $RecPubFileName -StorageName $StorageAccountName -ContainerName $ContainerName -StorageAccountKey $StorageAccountKey -VKMName $VKMName -Secret $SecretI thaught surely there's an error with an argument somewhere but I checked multiple times and all the arguments seem to receive the intended values.
07-31-2024 12:49 PM
and is the built-in Vault Administrator account the one that is being changed? or the OS level Admin account?
I'm assuming it's the built-in Vault Admin account, but figured I'd double check.
I'm also not seeing anything jumping out that could be a problem. Is the password being changed to a randomly generated one? or is it a known-test password situation?
-Matt
07-31-2024 12:57 PM
It's the built-in one as you guessed.
Also I don't know the value of the new password. The only way to login into the Admin account is to login as Master and change the Admin's password back to the original one.
08-01-2024 07:02 AM
The problem has been solved!
As expected, there was a problem with my arguments: there's an unwanted comma after the admin password argument which added a comma at the end of the password.
-AdminPass $AdminPass,Special thanks to M@ (CyberArk Community Manager) (CyberArk) for his help in this matter!
08-01-2024 07:46 AM
Great to hear it's solved! nice work!
-Matt
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!

