Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Invalid configuration: missing setting (v2.0.0) #242

Closed
LanceSandino opened this issue Aug 12, 2019 · 2 comments
Closed

Invalid configuration: missing setting (v2.0.0) #242

LanceSandino opened this issue Aug 12, 2019 · 2 comments
Assignees

Comments

@LanceSandino
Copy link

Using kubernetes to deploy sso-proxy, currently on v1.2.0

We changed the image to the latest v2.0.0 and updated the env variables.

We then get the following error:

{"error":"Invalid configuration:\n missing setting: cookie-secret\n missing setting: client-id\n missing setting: client-secret\n missing setting: statsd-host\n missing setting: statsd-port\n Invalid value for COOKIE_SECRET; must decode to 32 or 64 bytes, but decoded to 0 bytes","level":"error","msg":"error validing options","service":"sso-proxy","time":"2019-08-12 15:18:49.820"}

@LanceSandino LanceSandino changed the title Invalid configuration (v2.0.0) Invalid configuration: missing setting (v2.0.0) Aug 12, 2019
@LanceSandino
Copy link
Author

If I re-add COOKIE-SECRET CLIENT-ID CLIENT-SECRET STATSD-HOST and STATSD-PORT it works just fine.

It also seems that v2.0 fixes the issue I had: #228 ?

@Jusshersmith
Copy link
Contributor

Hi @LanceSandino

Apologies for not making this clearer in the release notes, however the majority of configuration variable changes introduced in v2.0.0 only apply to sso_auth (not sso_proxy). It looks like these particular changes were made to the sso_proxy component.

I've updated the release notes to make this clearer. (previously, it would've been mostly evident after looking at the PR referenced in the release notes!)

Similar changes will eventually be made to sso_proxy as well!

Sorry for any inconvenience this caused, and thank you for raising!

@Jusshersmith Jusshersmith self-assigned this Aug 27, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants