Usage in Remote Environments - zowe/zowe-explorer-vscode GitHub Wiki

Now that Zowe Explorer and Zowe Explorer API no longer use node-keytar, some users might encounter issues when trying to interact with remote environments.
This applies to:

  • Remote Docker
  • Remote SSH
  • Remote Tunnel

"ProfInfoErr: Failed to initialize secure credential manager"

Some users might encounter this error if they are trying to connect over Remote SSH or a container where the keyring is locked:

image

If the keyring on the remote container/server is already unlocked, you must expose the unlocked keyring to VS Code.
Export DBUS_SESSION_BUS_ADDRESS in your .bashrc file.

Note: If this environment variable changes, issue the following commands from the VS Code command palette to reflect those changes:

  • Remote-SSH: Kill Current VS Code Server
  • Developer: Reload Window

Using Zowe Explorer in remote environments with multiple VSCode windows

When using Zowe Explorer on more than one window, you might encounter the error above. If so, follow the steps to Unlock the keyring manually and then reload the window. Here is a summary of the steps to follow:

  • Open an integrated terminal on the VSCode windows with the error (Ctrl + `)
  • Run the echo root | gnome-keyring-daemon -r --unlock --components=secrets
  • Open the command palette (Ctrl + Shift + P)
  • Issue the > Developer: Reload Window command.