-
Bug
-
Resolution: Duplicate
-
Major
-
None
-
None
-
None
In automatic registration, if user for example does not provide SSO_REALM then proper configuration is still done (with master as default) on eap pod, but it won't manage to register client on sso side and eap will start without errors. Following log is printed:
ERROR: Unable to connect to SSO/Keycloak at https://sso-pdrobek.apps.devel.xpaas/auth for user mgmtuser and realm . SSO Clients *not* created
Missing SSO_REALM. Defaulting to master realm
Log "SSO Clients not created" creates feeling that no configuration was done at all.
Either no configuration should appear in that case or warning about partial configuration and information that registration is needed to be done manually should be thrown. In latter case user would have to be provided with several information about configuration to be able finish configuration by himself. (Secret for confidential apps, resource name)
- is related to
-
CLOUD-1206 [EAP6] Improve the error message when the POD fails to create the SSO clients.
-
- Closed
-