Remote Toolchain SSH Authentication and Credential Rotation

CLion utilizes SSH for remote development, delegating authentication to the host system's SSH agent or specific identity files defined in the toolchain configuration. This mechanism allows the IDE to manage a backend instance on a remote host for indexing and compilation.

In environments requiring strict security compliance, credentials such as SSH keys are rotated frequently. Currently, the IDE relies on the underlying OS credential store or the ~/.ssh/config file to resolve identities. When a key expires or is rotated on the remote host, the IDE must re-establish the connection using the updated identity.

There is uncertainty regarding how CLion handles the transition when an active session's credentials expire without a full IDE restart or manual toolchain reconfiguration.

• Does CLion automatically trigger a re-authentication request via the SSH agent when a remote session is terminated due to expired credentials?
• Is there a configuration to define a credential refresh interval for remote toolchains to prevent build failures during long-running sessions?