You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
On systems where I don't have a secure credentials store, or where I'm not wanting to use it, it's possible to in-line user and passwordproperties into a zowe.config.json profile, e.g.
It no longer seems to work with Zowe Explorer after upgrading to 3.1.1. It does work with 3.0.3 (I re-installed from .vsix to be sure the upgrade is what broke things).
To Reproduce
In-line "user" and "password" in a profile (i.e. don't use "secure").
Screenshots
OS: Mac Sonoma 14.7.1
Zowe Explorer Version: 3.1.1
(Optional) Zowe CLI Version:
(Optional) Are you using Secure Credential Store? Y
Failure under 3.1.1
Working under 3.0.3
When it fails there is a suspect error message about basicAuth and tokens, which may be the culprit for where the bug is hiding in the codebase
The text was updated successfully, but these errors were encountered:
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.
@Joe-Winchester Could you attach your complete zowe.config.json with any private info redacted? I've created a minimal config (contents below) that matches yours and haven't been able to reproduce the issue. I'm curious if there is some combination of zosmf and base profiles needed to cause the issue.
Describe the bug
On systems where I don't have a secure credentials store, or where I'm not wanting to use it, it's possible to in-line
user
andpassword
properties
into azowe.config.json
profile, e.g.It no longer seems to work with Zowe Explorer after upgrading to 3.1.1. It does work with 3.0.3 (I re-installed from .vsix to be sure the upgrade is what broke things).
To Reproduce
In-line "user" and "password" in a profile (i.e. don't use "secure").
Screenshots
Failure under 3.1.1
Working under 3.0.3
When it fails there is a suspect error message about basicAuth and tokens, which may be the culprit for where the bug is hiding in the codebase
The text was updated successfully, but these errors were encountered: