You can change the password of the existing Daml index database after the reconfigure deployment to bind the newly created nodes to the existing VMware Blockchain node.

As a best practice, changing the Daml Index database password is recommended if you have a weak password or you suspect a security threat.

Prerequisites

Procedure

  1. SSH into the Client node to change the password.
  2. Connect to the Daml index database and change the indexdb user password.
    #Getting daml_index_db container ID, note the port:
    #sudo docker ps
    
    #Getting daml index db IP
    sudo docker inspect -f '{{range .NetworkSettings.Networks}}{{.IPAddress}}{{end}}'<daml_index_db container ID>
    
    #Log in onto the DB
    psql -h <the-db-ip> -p <port> -U indexdb
    #enter password from step 1
    
    #enter postgresql password change prompt
    indexdb=# \password
    
    # enter and repeat the new password
    # exit
    indexdb=# \q
  3. Use the VI editor in the Client node VM to edit the configuration files.
    • Daml Ledger API configuration file /config/daml-ledger-api/environment-vars

    • Daml index database configuration file /config/daml-index-db/environment-vars

    • Telegraf configuration file /config/telegraf/telegraf.conf

    Sample Configuration Commands

    # Sample configuration commands
    sudo vi /config/daml-ledger-api/environment-vars
    #edit the value of INDEXDB_PASSWORD, to accomplish this:
    # press [Insert]
    # navigate to value and edit
    # press [Esc], type:
    # :w [to safe]
    # :q [to exit vi]
     
    # Do the same with:
    sudo vi /config/daml-index-db/environment-vars
    # change the value of POSTGRES_PASSWORD
     
    sudo vi /config/telegraf/telegraf.conf
    # change the value of [[inputs.postgresql]]
  4. Restart the containers.
    sudo docker restart <daml_ledger_api ID> <daml_index_db ID> <telegraf ID>
  5. (Optional) Check the container logs for any errors and resolve the errors.

    If transient errors appear after all the containers are restarted and running, resolve these errors.

  6. Update the new password in the VMware Blockchain Orchestrator output file.
    Node Id: 7489ddfa-d435-43d4-a8d1-92cf0e6273a0, name: /blocks/sddc6-vmware-vpn-onprem-5/segments/0a48d800/addresses/0a48d8b3, key: PRIVATE_IP, value: 10.72.216.179
    Node Id: 7489ddfa-d435-43d4-a8d1-92cf0e6273a0, name: https://vcenter.sddc-34-236-221-173.vmwarevmc.com//rest/vcenter/vm/vm-13549, key: CLIENT_ENDPOINT, value: https://{{ip}}:6865
    Node Id: 7489ddfa-d435-43d4-a8d1-92cf0e6273a0, name: https://vcenter.sddc-34-236-221-173.vmwarevmc.com//rest/vcenter/vm/vm-13549, key: CLIENT_GROUP_ID, value: 8647c2ec-659b-463c-905f-3f157d339ce0
    Node Id: 7489ddfa-d435-43d4-a8d1-92cf0e6273a0, name: https://vcenter.sddc-34-236-221-173.vmwarevmc.com//rest/vcenter/vm/vm-13549, key: CLIENT_GROUP_NAME, value: Group2
    #add this ---->>>>
    Node Id: 7489ddfa-d435-43d4-a8d1-92cf0e6273a0, name: https://vcenter.sddc-34-236-221-173.vmwarevmc.com//rest/vcenter/vm/vm-13549, key: Daml_DB_PASSWORD, value: new-pass   
    <<<<---add this
    Node Id: 7489ddfa-d435-43d4-a8d1-92cf0e6273a0, name: https://vcenter.sddc-34-236-221-173.vmwarevmc.com//rest/vcenter/vm/vm-13549, key: Daml_SDK_VERSION, value: 1.18.0
    Node Id: 7489ddfa-d435-43d4-a8d1-92cf0e6273a0, name: https://vcenter.sddc-34-236-221-173.vmwarevmc.com//rest/vcenter/vm/vm-13549, key: GENERATE_Daml_DB_PASSWORD, value: True
    Node Id: 7489ddfa-d435-43d4-a8d1-92cf0e6273a0, name: https://vcenter.sddc-34-236-221-173.vmwarevmc.com//rest/vcenter/vm/vm-13549, key: IMAGE_TAG, value: 0.0.0.2320
    Node Id: 7489ddfa-d435-43d4-a8d1-92cf0e6273a0, name: https://vcenter.sddc-34-236-221-173.vmwarevmc.com//rest/vcenter/vm/vm-13549, key: NODE_LOGIN, value: <password>
    Node Id: 7489ddfa-d435-43d4-a8d1-92cf0e6273a0, name: https://vcenter.sddc-34-236-221-173.vmwarevmc.com//rest/vcenter/vm/vm-13549, key: NOTARY_VERIFICATION_ENABLED, value: true
    Node Id: 7489ddfa-d435-43d4-a8d1-92cf0e6273a0, name: https://vcenter.sddc-34-236-221-173.vmwarevmc.com//rest/vcenter/vm/vm-13549, key: VM_CPU_COUNT, value: 4
    Node Id: 7489ddfa-d435-43d4-a8d1-92cf0e6273a0, name: https://vcenter.sddc-34-236-221-173.vmwarevmc.com//rest/vcenter/vm/vm-13549, key: VM_MEMORY, value: 32
    Node Id: 7489ddfa-d435-43d4-a8d1-92cf0e6273a0, name: https://vcenter.sddc-34-236-221-173.vmwarevmc.com//rest/vcenter/vm/vm-13549, key: VM_STORAGE, value: 100