Description of problem

Keycloak is enabled by default . I was doing some testing after disabling Keycloak.
When I re-enabled Keycloak , I found that I was unable to do anything on the MTA web console after logging in.

Version-Release number of selected component (if applicable)

MTA 6.2 stage

How reproducible

Always

Steps to Reproduce

1. Disable Keycloak by adding this to the Tackle CR yaml
feature_auth_required: "false"
2. Re-enable Keycloak by removing this line from the Tackle CR Yaml
feature_auth_required: "false"

Actual results

This breaks MTA. This message is seen after logging into the web console.
"Unable to connect"

Expected results

 MTA web console should be usable when Keycloak is re-enabled after being disabled.

Additional info