Authentication provider looks available even the communication between Gateway and z/OSMF is not working
pj892031 opened this issue · comments
Describe the bug
This bug was found during the testing AT-TLS. There was a configuration issue in the configuration: outbound rule from the Gateway to z/OSMF was AT-TLS enabled but the static definition contained HTTPs protocol. Therefore the communication cannot be successful (ie. login in the API Catalog ends with 503), but the checkbox on the ZUUL was marked as available
Steps to Reproduce
- configure Zowe to use z/OSMF provider
- create a not working communication between Gateway and z/OSMF (ie. HTTPs protocol over AT-TLS)
- open the homepage of the Gateway
Expected behavior
The authentication provider is not available, but there is a green check instead.
Details
- Tested on Zowe V3 with Gateway from V2
It's known issue and duplicate, it was mentioned multiple times. The Authentication Service doesn't properly reflect the state of the Authentication Service.
Specifically duplicates #1562 and as such I am closing this one.