Inquiry on Retaining Existing DB Passwords When Importing Tasks in Qlik Replicate

[EE_]

Dear Qlik Support Team,

We are currently planning to migrate Qlik Replicate tasks to another environment, such as UAT. During this process, we would like to confirm whether it is possible to retain the existing database connection passwords that are already configured in the UAT environment when importing tasks from another environment (e.g., DEV or SIT).

Specifically, we want to avoid overwriting the UAT database connection passwords with those from the exported task file.
Is there an option or best practice in Qlik Replicate to preserve the existing DB passwords in the destination environment during the import process?

Your guidance on this would be greatly appreciated.

[john_wang]

Hello @EE_ ,

The exported JSON file does not retain the password. This is by-design and there is no way to retrieve the password from repository.

After importing the JSON file into a new environment, you will need to re-enter the password (or other credentials), while the rest of the connection string remains unchanged.

Hope this helps.

John.

[EE_]

Hello @john_wang,

Thank you for your response.

We understand that the exported JSON file does not retain the password, and it must be re-entered after importing into a new environment. However, we came across the documentation that mentions the option "To change an endpoint password".

https://help.qlik.com/en-US/replicate/November2024/Content/Global_Common/Content/SharedEMReplicate/D...

We would like to clarify:

1. If we manually update the endpoint password in the new environment once, will it persist for future imports of the same task (using command line), or do we still need to re-enter the password every time we import the task JSON?

2. Since we are using the command-line tool to import tasks (e.g., using repctl importrepository ), we want to confirm whether the behavior is the same as importing via the UI — i.e., the password must still be re-entered manually each time.

Appreciate your clarification on this, as we’re trying to streamline our deployment process across environments.

[john_wang]

Hello @EE_ ,

1- Yes, the repository is overwritten during each import operation, so you need to ensure the password is re-entered.

2- Yes, the behavior is the same. However, you can customize your JSON file using applications — for example, by including the password in plain text. After importing into a new environment, the password will be encrypted and stored in the repository. However, since this JSON file contains the password in plain text, it should be stored securely and handled with caution.

Hope this helps.

John.