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

Using autostore as false results in a failure to connect with no error message. #224

Open
Tracked by #3286
davenice opened this issue Feb 4, 2025 · 2 comments
Open
Tracked by #3286
Labels
bug Something isn't working priority-medium Not functioning - next quarter if capacity permits severity-medium Bug where workaround exists or that doesn't prevent the usage of Zowe. Just makes it more complex

Comments

@davenice
Copy link
Contributor

davenice commented Feb 4, 2025

Describe the bug

I am trying to use autoStore set to false so that I am prompted for my username and password each time it's required (and after the work in #217 that should be less frequently!)

I have a config like this:

{
    "$schema": "./zowe.schema.json",
    "profiles": {
        "myhost-autostore-no": {
            "properties": {
                "host": "myhost.com"
            },
            "profiles": {
                "mycics-ssl": {
                    "type": "cics",
                    "properties": {
                        "protocol": "https",
                        "port": 28961,
                    }
                },
            }
        }
    },
    "autoStore": false
}

Expected and actual results

I am expecting to be able to connect, although likely I will be prompted several times for my creds until #217 is complete.

The actual result is that I'm prompted for my creds, but then my profile shows a no entry sign to indicate that it is broken. There is no error message logged or posted, that I can see.

@davenice davenice added the bug Something isn't working label Feb 4, 2025
Copy link

github-actions bot commented Feb 4, 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.

@JTonda JTonda added priority-medium Not functioning - next quarter if capacity permits severity-medium Bug where workaround exists or that doesn't prevent the usage of Zowe. Just makes it more complex labels Feb 6, 2025
@zowe-robot zowe-robot moved this from New Issues to Medium Priority in Zowe Explorer for VS Code Feb 6, 2025
@AndrewTwydell
Copy link
Contributor

Seems to be similar (or exactly the same bit of code failing) as zowe/zowe-explorer-vscode#3360.

The error occurs during the ZoweVsCodeExtension.updateCredentials method call which seems like it would be shared code for all profile types.

Their suggestions is to override the VSCode settings value - I'd rather ignore it's value if autoStore is false rather than changing it, but whatever works best!

I imagine the desired behaviour is:

  • autoStore: true and Secure Credentails: enabled = Update creds in secure storage
  • autoStore: true and Secure Credentials: disabled = Update creds in config JSON
  • autoStore: false and Secure Credentials: * = Do nothing...!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working priority-medium Not functioning - next quarter if capacity permits severity-medium Bug where workaround exists or that doesn't prevent the usage of Zowe. Just makes it more complex
Projects
Status: Medium Priority
Development

No branches or pull requests

3 participants