zftp profile gives "Rest API failure with HTTP(S) status 401 Authentication error."

[dkelosky]

Describe the bug

Credentials fail to load in zftp whether plain text or in secure credential store with these error logs.

[2025/03/05 10:23:35] [INFO] Profile validation failed for zftp.
[2025/03/05 10:23:35] [ERROR] Error: Rest API failure with HTTP(S) status 401 Authentication error.
{
  errorDetails: [o [Error]: Rest API failure with HTTP(S) status 401 Authentication error.
  	at U.<anonymous> (/Users/----/.vscode/extensions/zowe.zowe-explorer-ftp-extension-3.1.1/out/src/main.extension.js:49:13623)
  	at Generator.throw (<anonymous>)
  	at y (/Users/---/.vscode/extensions/zowe.zowe-explorer-ftp-extension-3.1.1/out/src/main.extension.js:49:12357)] {
    mDetails: {
      msg: 'Rest API failure with HTTP(S) status 401 Authentication error.',
      errorCode: '401'
    },
    mMessage: 'Rest API failure with HTTP(S) status 401 Authentication error.'
  },
  profile: undefined
}
[2025/03/05 10:23:59] [ERROR] Profile zftp is inactive. Please check if your Zowe server is active or if the URL and port in your profile is correct.

zftp CLI for Zowe CLI works (as does z/OSMF & zssh). The credentials and Zowe Explorer tree views for z/OSMF and zssh work as well.

To Reproduce

Expected behavior

Screenshots

Desktop (please complete the following information):

• OS:
• Zowe Explorer Version:
• (Optional) Zowe CLI Version:
• (Optional) Are you using Secure Credential Store?

Additional context

[github-actions]

Thank you for creating a bug report.
We will investigate the bug and evaluate its impact on the product.
If you haven't already, please ensure you have provided steps to reproduce the bug and as much context as possible.

[traeok]

Update: This issue is because we always throw a credential error from the FTP extension in the event that await this.ftpClient fails in getStatus:

https://github.com/zowe/zowe-explorer-vscode/blob/main/packages/zowe-explorer-ftp-extension/src/ZoweExplorerAbstractFtpApi.ts#L95-L103

We should refactor this logic as this error handling is not valid in cases where the client returns an error unrelated to credentials.