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

VSCE: using the CICS extension with a different host breaks Zowe Explorer #159

Open
davenice opened this issue Nov 27, 2024 · 3 comments · May be fixed by #173
Open

VSCE: using the CICS extension with a different host breaks Zowe Explorer #159

davenice opened this issue Nov 27, 2024 · 3 comments · May be fixed by #173
Assignees
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

davenice commented Nov 27, 2024

Describe the bug

I have multiple hosts in play.
hosta is a z/OSMF host which is https and using a self-signed certificate
hostb hosts a CMCI connection - either https with self-signed certificate or http (no ssl)
I am specifying "rejectUnauthorized": false on both profiles.

Using the CICS extension breaks the Zowe Explorer extension.

Recreation steps

I connect to hosta with z/OSMF correctly and browse data sets.
I connect to hostb with the CICS extension correctly and browse CICS resources.
I attempt to refresh my hosta z/OSMF data sets and receive this error: Retrieving response from MVS list API Error: Failed to send an HTTP request.

I reload my VS Code and able to connect to z/OSMF on hosta correctly, again.

If I stick to just using hostb consistently, I am able to use both z/OSMF and CMCI.

Describe your environment

  • Zowe CLI version installed (run command zowe --version): CLI Version: 8.8.2, Zowe Release Version: v3.0.0
  • Zowe Explorer version installed: 3.0.3
  • Installed plug-ins and their version numbers (run command zowe plugins list --short): no plugins
  • Installed z/OS-related VSCode Extensions and their version numbers: CICS - 3.0.1
  • Node.js and NPM versions installed (run node --version, npm --version): v22.9.0, 10.8.3
Copy link

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.

@davenice
Copy link
Author

@AndrewTwydell - I think you've had a poke at debugging this?

@JillieBeanSim JillieBeanSim 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 Dec 3, 2024
@zowe-robot zowe-robot moved this from New Issues to Medium Priority in Zowe Explorer for VS Code Dec 3, 2024
@AndrewTwydell
Copy link
Contributor

Seems to be caused by the https library global overrides of the rejectUnauthorized value, which doesn't seem to take effect properly when using Axios for requests. Our workaround is moving away from Axios for HTTP requests and using the CICS SDK's getResource method to get all our data. This takes an Imperative Session instance which correctly handles rejectUnauthorized.

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

Successfully merging a pull request may close this issue.

3 participants