401 after refreshing APIML token when trying to view job spool

[adam-wolfe]

Describe the bug

If I have an expired token, reauthenticate, list jobs, then try to view the spool files, I get an error 401. This behaves similarly to #3150, except with viewing job spool rather than members.

To Reproduce

1. Start VS Code with an expired APIML token.
2. Try to list data sets and get prompted to refresh your token.
3. Refresh your token by reauthenticating.
4. List jobs by user ID
5. Expand a job and click on a spool file
6. Get an error 401

Not sure if it's relevant, but I am using nested profiles for APIML connections.

Expected behavior

The new token should be used when trying to download spool files.

Screenshots

Desktop (please complete the following information):

• OS:
• Zowe Explorer Version: built from main as of dbce388
• (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.

[JTonda]

#3243 - This PR should improve the experience of getting a 401 error when opening a file in the editor.

[traeok]

#3243 - This PR should improve the experience of getting a 401 error when opening a file in the editor.

Update - sorry for the confusion, but this PR will not improve this behavior as we have outstanding bugs with the credential prompt that need resolved. Once those are fixed, users can update credentials through the Manage Profile menu. The "Try again" button will work as expected in the editor, using the new creds.

We cannot prompt the users from the provider to enter in credentials as this would be a breaking change for extenders calling readFile.