Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

Version 1 Current »

Applies to: (tick) Kyvos Enterprise  (error) Kyvos Cloud (SaaS on AWS) (error) Kyvos AWS Marketplace

(error) Kyvos Azure Marketplace (error) Kyvos GCP Marketplace (error) Kyvos Single Node Installation (Kyvos SNI)


There can be four combinations of inputs for node reachability validation  

  • Username and Private key file path in init conf file  

  • Username in init conf file & password stored in secret  

  • Username and Plain text password in init conf file  

  • Username and Encrypted password in init conf file  

  1. If a password is used for node validation, enable password authentication on each BI Server, Query Engine, and Kyvos Manager nodes as explained in the Instances configuration to use password-based authentication for Kyvos deployment section.

  2. Refer to the following combination of keys in init conf file:

    Key name  

    Description  

    username 

    Required in init conf file  

    privateKey 

    Required in init conf file, this key is used to connect the Kyvos nodes when secret is not used and password (encrypted/plain text is not specified) in init conf file.

    secretStoreId  

    Required in init conf file, if external secret is used. In case of secret exist in deployment, password read from secret used in deployment.

    kyvosnodespassword  

    Required in init conf file if plain text password or encrypted password is used to validate nodes. If nodepasswordEncAlgo key is present in init conf file this value is treated as encrypted else this is treated as plain text.

    nodepasswordEncAlgo  

    Required in init conf file if validation needs to perform on encrypted password. Kyvosnodespassword key should be encrypted.


  3. Run the environment validation using command line or wizard.

  • No labels