[CLOUD-3199] - added warn message in case of SSO_SECRET is empty

[ricardozanini]

Signed-off-by: Ricardo Zanini zanini@redhat.com

Please see:
https://issues.jboss.org/browse/CLOUD-3199

[ricardozanini]

@luck3y I decided to keep the same "warn logic" like the others warns in the script file. This warn is just a help message for users that don't link the keycloak subsystem error message with the SSO_SECRET parameter.

[luck3y]

@ricardozanini Thanks.

@iankko Jan, this look OK to you? We're wondering if just logging a warn is OK here. The server boot will probably fail due to the invalid subsytem config.

[ricardozanini]

@luck3y @iankko the server will boot and pod won't fail, but this WARN will be there intermittently:

16:15:58,005 WARN  [org.keycloak.adapters.authentication.ClientIdAndSecretCredentialsProvider] (pool-25-thread-1) Client 'root' doesn't have secret available
16:15:58,013 ERROR [org.keycloak.adapters.NodesRegistrationManagement] (pool-25-thread-1) failed to register node to keycloak
16:15:58,013 ERROR [org.keycloak.adapters.NodesRegistrationManagement] (pool-25-thread-1) status from server: 400
16:15:58,013 ERROR [org.keycloak.adapters.NodesRegistrationManagement] (pool-25-thread-1)    {"error":"unauthorized_client","error_description":"INVALID_CREDENTIALS: Invalid client credentials"}

The integration won't work until the user generates a secret in the RH-SSO console and then set this secret to the SSO_SECRET parameter in the deploymentconfig/container ENV.