-
Notifications
You must be signed in to change notification settings - Fork 184
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
Error loading env file #222
Comments
It looks like #213 made the config pretty different. Until the next release you should switch to the stable docker image and it should work. |
Hi @blucompassai. How did you get on with @tarpdalton's (thank you @tarpdalton!) suggestion? Also, just so you're aware; version |
I'm running into this as well. It would be great to have some updated docs for deploying on Kubernetes. The blog post the docs point to is outdated. |
Running into this issue following the steps at https://medium.com/@while1eq1/single-sign-on-for-internal-apps-in-kubernetes-using-google-oauth-sso-2386a34bc433. Is there a fix to this? |
Describe the bug
Followed quickstart guide and when did docker-compose up it , only sso-auth container is not coming up and giving this error :
{"error":"2 error(s) decoding:\n\n* 'client[id]' expected a map, got 'string'\n* 'client[secret]' expected a map, got 'string'","level":"error","msg":"error loading in config from env vars","service":"sso-authenticator","time":"2019-06-28 07:57:42.105"}
To Reproduce
Steps to reproduce the behavior:
Just follow the quickstart guide.
I am on ubuntu
Distributor ID: Debian
Description: Debian GNU/Linux 9.9 (stretch)
Release: 9.9
Codename: stretch
docker version
docker --version
Docker version 18.09.7, build 2d0083d
docker-compose --version
docker-compose version 1.21.2, build a133471
env file
CLIENT_ID=
CLIENT_SECRET=
Expected behavior
Expected sso-auth to come up
Desktop (please complete the following information):
The text was updated successfully, but these errors were encountered: