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
We aim to use structured logging throughout sso, but its use for reporting configuration errors that prevent successful startup actually makes the errors much harder to read and diagnose. Here's an example:
In cases where invalid/incomplete configuration is provided, we should instead exit with a more readable error message.
Additionally, the error message above refers to settings as, e.g., provider-url, which is a holdover from the days of CLI options. These configuration error messages should be in terms of env vars (i.e. PROVIDER_URL in this example), given that env vars are the standard/preferred method of configuring sso.
This affects both sso-auth and sso-proxy.
The text was updated successfully, but these errors were encountered:
We aim to use structured logging throughout sso, but its use for reporting configuration errors that prevent successful startup actually makes the errors much harder to read and diagnose. Here's an example:
In cases where invalid/incomplete configuration is provided, we should instead exit with a more readable error message.
Additionally, the error message above refers to settings as, e.g.,
provider-url
, which is a holdover from the days of CLI options. These configuration error messages should be in terms of env vars (i.e.PROVIDER_URL
in this example), given that env vars are the standard/preferred method of configuring sso.This affects both
sso-auth
andsso-proxy
.The text was updated successfully, but these errors were encountered: