Skip to content

ZWES1606W Failed to get JWK. rc=HTTP response error - invalid JSON (3), rsn=Invalid port (3) #744

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

Open
Tarfiz opened this issue Jan 20, 2025 · 1 comment
Labels
bug Something isn't working new not yet triaged severity-medium A bug where workaround exists or that doesn't prevent the usage of the Zowe or the use case, just ma

Comments

@Tarfiz
Copy link

Tarfiz commented Jan 20, 2025

When use ZOWE V3.= receive those error messages:

ZWES1014I ZIS status - 'Ok' (name='ZWESIS_SYT ', cmsRC='0', description='Ok', clientVersion='2')
error parsing JSON response
error parsing JSON response
error parsing JSON response
error parsing JSON response
error parsing JSON response
error parsing JSON response
error parsing JSON response
ZWES1606W Failed to get JWK. rc=HTTP response error - invalid JSON (3), rsn=Invalid port (3). Retry in 10 seconds
error parsing JSON response
JWK doesn't contain key
ZWES1602W JWK is in unrecognized format
ZWES1605W Server will not accept JWT

Describe your environment

  • Zowe version number 3.0.0 install method SMPE
  • java 17.0 64
  • Node.js node-v18.14.2
  • z/OS 2.5
  • z/OSMF 2.5.0/wlp-1.0.87.cl240320240311-1901) on IBM J9 VM, version 8.0.8.26 - pmz6480sr8fp26-20240529_01(SR8 FP26)
@Tarfiz Tarfiz added bug Something isn't working new not yet triaged severity-medium A bug where workaround exists or that doesn't prevent the usage of the Zowe or the use case, just ma labels Jan 20, 2025
@1000TurquoisePogs 1000TurquoisePogs transferred this issue from zowe/zlux Jan 24, 2025
@1000TurquoisePogs
Copy link
Member

@Tarfiz I moved this to the ZSS repo since the errors are from ZSS, however, what it appears to be saying is that the server ZSS needs to contact (APIML Gateway) is returning something thats not JSON, and then ZSS does not like that.
So, I would first check - do the job logs show that the gateway is healthy? Can you get to it in your browser? Can you log into the API catalog? ZSS may just be a victim of the status of the gateway.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working new not yet triaged severity-medium A bug where workaround exists or that doesn't prevent the usage of the Zowe or the use case, just ma
Projects
Status: No status
Status: No status
Development

No branches or pull requests

2 participants