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

API Catalog doesn't work properly with NONSTRICT_VERIFY_CERTIFICATES with swagger #2318

Closed
CarsonCook opened this issue Apr 25, 2022 · 1 comment
Assignees
Labels
bug Verified defect in functionality Priority: High v2

Comments

@CarsonCook
Copy link
Contributor

CarsonCook commented Apr 25, 2022

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

  1. Start Zowe with NONSTRICT_VERIFY_CERTIFICATES=true and STRICT_VERIFY_CERTIFICATES=false
  2. See swagger for zosmf not rendered in API Catalog
  3. Recreate keystore with NONSTRICT_VERIFY_CERTIFICATES=false and restart Zowe
  4. 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.

https://github.com/zowe/api-layer/wiki/Issue-management

@CarsonCook CarsonCook added bug Verified defect in functionality new New issue that has not been worked on yet labels Apr 25, 2022
@CarsonCook
Copy link
Contributor Author

CarsonCook commented Apr 26, 2022

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Verified defect in functionality Priority: High v2
Projects
None yet
Development

No branches or pull requests

3 participants