Gateway landing page not reflecting the correct Authentication service state

[taban03]

Describe the bug
If there is a wrong configuration of the authentication provider, the Authentication Service label present in the GW landing page is shown as UP (green colour).
Steps to Reproduce

1. Start the GW with the auth provider set to zosmf, either without starting the mockZosmf or with a wrong configuration of the real zosmf
2. Navigate to the GW landing page and check the Authentication Service label, which will be set to Available even if it's not.

Expected behavior
A clear and concise description of what you expected to happen.

Screenshots
If applicable, add screenshots to help explain your problem.

Logs
If applicable, add server logs collected at the time of your problem.

Details

• Version and build number: [e.g. 0.4.4-SNAPSHOT build # 155]
• Test environment: [either defined Zowe test environment: Marist (1, 2, 3), River, or your own environment: z/OS version and z/OSMF version]

API Catalog Web UI (in case of API Catalog issue):

• OS: [e.g. macOS, Windows]
• Browser [e.g. Chrome, Safari]
• Version [e.g. 71.0.3578.98]

REST API client (in case of REST API issue):

• Technology: [e.g. Spring Boot, Node.js]
• OS: [e.g. Windows 10]

Additional context
Add any other context about the problem here.

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

[taban03]

The issue is still there. In case of misspelling of the auth provider, the GW won't start giving a clear message:

2021-07-27 08:15:44.683 <ZWEAGW1:main:7667> at670475 WARN  (o.z.a.g.s.c.CompoundAuthProvider) ZWEAG107W Incorrect value: apiml.security.auth.provider = 'dum'. The authentication provider is not set correctly. The default 'zosmf' authentication provider is being used.

However, in case of using zosmf provider, if mockzosmf is used in the config but is not started, the GW landing page still states it is UP.