Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Zowe Explorer 3.1.1 no longer allows profiles that have "user" and "password" in-lined in their properties #3498

Open
Joe-Winchester opened this issue Mar 5, 2025 · 2 comments
Assignees
Labels
bug Something isn't working needs more info

Comments

@Joe-Winchester
Copy link
Member

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 password properties into a zowe.config.json profile, e.g.

 "zosmf_svl_09": {
     "type": "zosmf",
      "properties": {
         "host": "abc.host.england.com",
         "port": 443,
         "rejectUnauthorized": false,
         "protocol": "https",
         "user": "ME"
         "password": "LOVECOOKIE
     },
 },

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

Image

Working under 3.0.3

Image

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

Image
Copy link

github-actions bot commented Mar 5, 2025

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.

@t1m0thyj
Copy link
Member

t1m0thyj commented Mar 5, 2025

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

{
    "$schema": "./zowe.schema.json",
    "profiles": {
        "lpar1_zosmf": {
            "type": "zosmf",
            "properties": {
                "host": "lpar1.broadcom.net",
                "port": 443,
                "rejectUnauthorized": false,
                "protocol": "https",
                "user": "timothy",
                "password": "zowe"
            }
        }
    },
    "defaults": {
        "zosmf": "lpar1_zosmf"
    },
    "autoStore": false
}

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working needs more info
Projects
Status: New Issues
Development

No branches or pull requests

3 participants