passexec_name not loaded from servers.json file #10702

Activity

1. deefdragon

   added

   Bug

   on Oct 30, 2026
2. deefdragon

   changed the title [-]PGADMIN_REPLACE_SERVERS_ON_STARTUP not loading passexec_name into existing servers[/-] [+]passexec_name not loaded from servers.json file[/+] on Oct 30, 2026
3. dpage commented on Nov 5, 2026

   

   dpage

   on Nov 5, 2026

   Contributor

   More actions

   Thanks for the report. The key in servers.json is still PasswordExecCommand, and there is no PasswordExecName key. In 9.19 the free-text command was replaced in server mode by an allowlist, and in server mode PasswordExecCommand now holds the name of an entry in SERVER_PASSEXEC_COMMANDS. On import that name is stored as the server's password exec name, and on export the same name is written back out under the same key. The code you linked is the export path. The import side is _load_server_passexec(), which is called from load_database_servers().

   So for a config such as:

   SERVER_PASSEXEC_COMMANDS = {
       'vault': ['/usr/local/bin/get-pg-pass']
   }

   the server entry should contain:

   "PasswordExecCommand": "vault",
   "PasswordExecExpiration": 300

   If that still doesn't work, two other things can cause it:

   • The name must be in SERVER_PASSEXEC_COMMANDS when servers.json is loaded. Otherwise the server is imported without a command, and a warning appears in the container log: "Ignoring the password exec command for server '...' as it is not the name of a command in SERVER_PASSEXEC_COMMANDS."
   • The container only loads servers.json the first time it starts, unless PGADMIN_REPLACE_SERVERS_ON_STARTUP is set. Editing the file after that has no effect on servers that already exist.

   Users connecting to a shared server inherit the owner's command, unless they have chosen a different one (or none) in their own copy of the server's properties.

   Could you try the correct key and let us know whether it works?
4. deefdragon commented on Nov 6, 2026

   

   deefdragon

   on Nov 6, 2026

   Author

   More actions

   Yup. Setting PasswordExecCommand worked. Missed that that was what needed to have the command key.
5. deefdragon

   closed this as completedon Nov 6, 2026