Validate key vault configuration - Precisely Data Integrity Suite

Data Integrity Suite
Product
Spatial_Analytics
Data_Integration
Data_Enrichment
Data_Governance
Precisely_Data_Integrity_Suite
geo_addressing_1
Data_Observability
Data_Quality
dis_core_foundation
Services
Spatial Analytics
Data Integration
Data Enrichment
Data Governance
Geo Addressing
Data Observability
Data Quality
Core Foundation
ft:title
Data Integrity Suite
ft:locale
en-US
PublicationType
pt_product_guide
copyrightfirst
2000
copyrightlast
2026

When configuring the key vault connection, ensure that the Agent secret name in the user interface(UI) exactly matches the key stored in the key vault.

Steps to verify:

  1. Run the following command: ./discli keyvault deploySecret --listkeys

    This will list all keys available across namespaces. Look for the key name under your relevant namespace, for example:

    Listing keys in 'precisely-keyvault-secret'
agentaprolesecret
SUCCESS: Total keys: 1
    The key name (e.g., agentaprolesecret) must exactly match the value configured as Agent secret name in the UI key vault connection.
  2. If no keys are found, the output is 
    INFO: Secret 'precisely-keyvault-secret' missing in <namespace>

    It indicates that no keys have been deployed in that namespace.

  3. Error in UI: If the Agent secret name configured in the UI does not match any key available on the Agent, the following error appears in the UI.
    [KEYVAULT-FILE-ERROR] KeyVault Agent Secret not accessible. Please verify the secret configuration and ensure the agent secret is properly mounted.
  4. Optional: To explore additional options for this command, run ./discli keyvault deploySecret --help

    This displays supported flags such as --listkeys, which can assist during validation and troubleshooting.