[WIP, draft] preflight check draft for zosmf jwt#4727
[WIP, draft] preflight check draft for zosmf jwt#47271000TurquoisePogs wants to merge 11 commits intov3.x/stagingfrom
Conversation
Signed-off-by: 1000TurquoisePogs <sgrady@rocketsoftware.com>
1000TurquoisePogs
had a problem deploying
to
marist-zzow10
GitHub Actions
Failure
Signed-off-by: 1000TurquoisePogs <sgrady@rocketsoftware.com>
|
build 9923 FAILED. |
1000TurquoisePogs
had a problem deploying
to
marist-zzow11
GitHub Actions
Failure
Signed-off-by: 1000TurquoisePogs <sgrady@rocketsoftware.com>
1000TurquoisePogs
had a problem deploying
to
marist-zzow11
GitHub Actions
Failure
|
build 9924 FAILED. |
|
build 9925 FAILED. |
| # # Superuser startup check - defaults to zowe.launchScript.startupChecks.default, or "exit" if this is unset | ||
| # user: exit | ||
| # z/OSMF JWT support check - checks whether z/OSMF JWT support is usable when Zowe is configured to use it | ||
| zosmfjwt: "exit" |
There was a problem hiding this comment.
We have discussed this as confusing for customers.
If you setup just zowe.launchScript.startupChecks.default = warn in your main configuration, this default will overwrite it for zOSMF JWT check.
That's why the rest of the checks are commented out here.
Signed-off-by: hrishikesh-nalawade <hrishikesh.nalawade.17@gmail.com>
|
, SMPE build 9967 FAILED. |
1 similar comment
|
, SMPE build 9967 FAILED. |
Signed-off-by: hrishikesh-nalawade <hrishikesh.nalawade.17@gmail.com>
|
, SMPE build 9986 FAILED. |
1 similar comment
|
, SMPE build 9986 FAILED. |
Signed-off-by: 1000TurquoisePogs <sgrady@rocketsoftware.com>
1000TurquoisePogs
had a problem deploying
to
marist-zzow11
GitHub Actions
Failure
|
build 10051 FAILED. |
Signed-off-by: hrishikesh-nalawade <hrishikesh.nalawade.17@gmail.com>
|
, SMPE build 10136 FAILED. |
Signed-off-by: hrishikesh-nalawade <hrishikesh.nalawade.17@gmail.com>
|
, SMPE build 10139 FAILED. |
|
, SMPE build 10139 SUCCEEDED. |
Signed-off-by: hrishikesh-nalawade <hrishikesh.nalawade.17@gmail.com>
Signed-off-by: hrishikesh-nalawade <hrishikesh.nalawade.17@gmail.com>
|
, SMPE build 10239 SUCCEEDED. |
3 participants
Alternative to #4724
This PR intends to use the jar produced in zowe/api-layer#4531 to create a command
zwe validate zosmf jwtwhich checks if a given zowe-zosmf config is valid depending on if jwt support exists and if zowe is using that or just ltpa.I do not know the output of this jar, so this PR can be improved by giving better user responses based upon what the jar returns, but I do have a basic template that functions upon expecting that any return code other than 0 is somehow bad.
This code does nothing if apiml is not in use, and does not result in error when ltpa is used either. It's really checking for if you're requesting jwt but the jwt handling isnt working for some reason.