Profile authentication method is unknown when using APIML tokens

[adam-wolfe]

Describe the bug

I am prompted for username and password whenever I try to access z/OSMF via the APIML, despite having a valid token. I can hit the escape key to bypass the username prompt and then enter a filter and get back a list of data sets.

Furthermore, whenever I right click on a z/OSMF profile and select Manage Profile, the line "[DEBUG] Profile dev.zosmf authentication method is unkown." is added to the log. I am then presented with these quick pick options:

If I choose to Add Credentials, user and password are added to my z/OSMF profile. If I choose to Log in to authentication service, I am able to get a new token, but I still get prompted for a user name anytime I try to list data sets, USS files, or jobs (I can still ignore the prompt and enter a filter and things work normally).

The same config works normally in Zowe CLI and with Zowe Explorer 2.13.0 in a Linux VM.

I also deleted the credentials in Windows Credential Manager and deleted ~/AppData/Roaming/Code without success.

To Reproduce

1. Right-click on a z/OSMF profile
2. Click manage profile
3. Click Log in to authentication service
4. Enter creds, get a token
5. Try to list data sets
6. I am prompted for user name.

Expected behavior

Zowe Explorer should realize that the config is using token authentication for the z/OSMF profile I am using.

Screenshots

Desktop (please complete the following information):

• OS: Windows 10
• Zowe Explorer Version: 2.13.0, and latest from main (as of 1/8/2024)
• (Optional) Zowe CLI Version:
• (Optional) Are you using Secure Credential Store?

[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.

[adam-wolfe]

Had a zowe.config.json in my user home directory. After deleting that everything is fine.