You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
The getAppAuthMode function does not evaluate the configuration. It only checks if the configuration is defined. This causes wrong evaluation if values are set but set to false.
So if I define KC_ENABLED=false, the service starts up with OIDC configuration enabled. Since I do not have OIDC configuration values, the pod dies saying Configuration property \"keycloak.clientId\" is not defined
To Reproduce
Steps to reproduce the behavior:
Deploy service with KC_ENABLED=false set but do not set any other KC vars
See error at startup saying keycloak.clientId is not defined.
Expected behavior
If I configured KC_ENABLED=false, it should not expect keycloak configuration to be defined.
Screenshots
Desktop (please complete the following information):
OS: [e.g. iOS]
Browser [e.g. chrome, safari]
Version [e.g. 22]
Smartphone (please complete the following information):
Device: [e.g. iPhone6]
OS: [e.g. iOS8.1]
Browser [e.g. stock browser, safari]
Version [e.g. 22]
Additional context
The text was updated successfully, but these errors were encountered:
You make a good point.. and it's a usability issue we want to resolve.
currently, the config values are parsed as strings. so "false" = true`
it appears recent versions of the node-config library allow us to parse booleans.
We're going to look into this. but I expect it will be a v.0.5 change.
Describe the bug
The getAppAuthMode function does not evaluate the configuration. It only checks if the configuration is defined. This causes wrong evaluation if values are set but set to
false
.common-object-management-service/app/src/components/utils.js
Lines 40 to 48 in a32d4a8
In the above function, the code tests if a config value exists instead of getting config.
So if I define KC_ENABLED=false, the service starts up with OIDC configuration enabled. Since I do not have OIDC configuration values, the pod dies saying
Configuration property \"keycloak.clientId\" is not defined
To Reproduce
Steps to reproduce the behavior:
Expected behavior
If I configured KC_ENABLED=false, it should not expect keycloak configuration to be defined.
Screenshots
Desktop (please complete the following information):
Smartphone (please complete the following information):
Additional context
The text was updated successfully, but these errors were encountered: