Hashicorp vault integration

Hi ​@mayank_singh 

You cannot wire an FDA (or any external account) password directly to HashiCorp Vault via a special syntax in Campaign today.

• The dataStore/@useVault, @vaultUrl, @vaultSecretPath, @vaultTokenPath flags only tell Campaign to pull core crypto keys/secrets (like XtkKey) from Vault, not to resolve arbitrary passwords in the UI fields. https://experienceleague.adobe.com/en/docs/campaign-classic/using/installing-campaign-classic/appendices/the-server-configuration-file
• Once XtkKey is available (now coming from Vault in your case), Campaign still stores FDA and other external‑account passwords in the database, encrypted with that key, as documented for XtkKey ("used to encrypt most passwords in the database"). https://experienceleague.adobe.com/en/docs/campaign-classic/using/installing-campaign-classic/appendices/configuring-campaign-options

So:

• There is no supported syntax like vault:... or cst-vault://... that you can put in the FDA password field.
• The supported pattern is still:
  • Enter the FDA password in the external account.
  • Let Campaign encrypt it with XtkKey (which, in your setup, is itself fetched from Vault).

Any attempt to have Campaign read arbitrary connector passwords directly from Vault would be a custom, unsupported extension and not something you can rely on as a product feature.