Skip to content
This repository has been archived by the owner on Nov 13, 2023. It is now read-only.

[next] Config auto-store may store secure properties in plain text #709

Closed
t1m0thyj opened this issue Dec 16, 2021 · 0 comments · Fixed by #710
Closed

[next] Config auto-store may store secure properties in plain text #709

t1m0thyj opened this issue Dec 16, 2021 · 0 comments · Fixed by #710
Assignees

Comments

@t1m0thyj
Copy link
Member

Given the following config JSON file that contains nested profiles (subprofiles):

{
    "$schema": "./zowe.schema.json",
    "profiles": {
        "parent": {
            "profiles": {
                "child": {
                    "properties": {},
                    "profiles": {
                        "zosmf": {
                            "type": "zosmf",
                            "properties": {
                                "port": 443
                            },
                            "secure": []
                        }
                    },
                    "secure": [
                        "host"
                    ]
                }
            },
            "secure": [
                "user",
                "password"
            ],
            "properties": {}
        },
        "base": {
            "type": "base",
            "properties": {},
            "secure": []
        }
    },
    "defaults": {
        "zosmf": "parent.child.zosmf",
        "base": "base"
    },
    "autoStore": true
}

The expected behavior is for all 3 missing properties to be stored securely: host, user, and password.
The actual behavior is that only 2 missing properties get stored securely: user and password but not host.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

1 participant