GoLand ↔ Remote Go SDK: Re-authentication Flow After Credential Expiry

Integration Boundary

GoLand delegates compilation, testing, and debugging to a Go SDK that may run on a remote target — SSH host, Docker container, or WSL instance. Authentication to these targets is configured in Settings | Build, Execution, Deployment using JetBrains SSH configurations (password, key pair, or ssh-agent) or per-data-source database credentials stored in the IDE password safe.

Unresolved Behavior

When a credential expires or is revoked mid-session — for example, an SSH key passphrase times out, an ssh-agent socket closes, or a database password is rotated — the IDE’s re-authentication flow for an already-configured remote SDK or data source is not clearly documented. It is unclear whether GoLand prompts inline, fails the active run/debug configuration with a generic error, or requires the user to reopen and resave the SSH or data-source configuration.

Constraints

• Credential storage backend varies by OS (KeePass-style safe vs. native keychain) and GoLand version.
• Agent forwarding exposes the local agent to the remote host; per-target keys are preferred for least privilege.
• Remote Go commands inherit the SSH user’s full permissions; GoLand cannot further restrict them.

What exact prompt or error does GoLand surface when an SSH key passphrase or agent session expires during an active build? Does a revoked database password trigger an inline re-prompt or a run-configuration failure? Is the behavior consistent across SSH, Docker, and WSL remote SDK types?