You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
I have an internal environment that fully works with VERIFY_CERTIFICATES=false and NONSTRICT_VERIFY_CERTIFICATES=true. Except, the swagger for zosmf is not retrieved properly. When I set NONSTRICT_VERIFY_CERTIFICATES=false, the swagger is retrieved and displayed.
Steps to Reproduce
Start Zowe with NONSTRICT_VERIFY_CERTIFICATES=true and STRICT_VERIFY_CERTIFICATES=false
See swagger for zosmf not rendered in API Catalog
Recreate keystore with NONSTRICT_VERIFY_CERTIFICATES=false and restart Zowe
See zosmf swagger in API Catalog
Expected behavior
Given that authentication works with NONSTRICT_VERIFY_CERTIFICATES=true, retrieving swagger should also work.
Additional context
This is in v1.27.4
Related to #2315, I had to manually write in logging and use a custom jar file to identify this issue - otherwise the substitute swagger is created and nothing is logged.
This is because if there are any exceptions thrown while retrieving the swagger for z/OSMF, the substitute swagger is returned. An exception is thrown due to an invalid certificate, which shouldn't happen with verify set to false. There's configuration missing for the code that queries the swagger url.
Describe the bug
I have an internal environment that fully works with
VERIFY_CERTIFICATES=false
andNONSTRICT_VERIFY_CERTIFICATES=true
. Except, the swagger for zosmf is not retrieved properly. When I setNONSTRICT_VERIFY_CERTIFICATES=false
, the swagger is retrieved and displayed.Steps to Reproduce
NONSTRICT_VERIFY_CERTIFICATES=true
andSTRICT_VERIFY_CERTIFICATES=false
NONSTRICT_VERIFY_CERTIFICATES=false
and restart ZoweExpected behavior
Given that authentication works with
NONSTRICT_VERIFY_CERTIFICATES=true
, retrieving swagger should also work.Additional context
This is in v1.27.4
Related to #2315, I had to manually write in logging and use a custom jar file to identify this issue - otherwise the substitute swagger is created and nothing is logged.
https://github.com/zowe/api-layer/wiki/Issue-management
The text was updated successfully, but these errors were encountered: