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

Error loading env file #222

Closed
blucompassai opened this issue Jun 28, 2019 · 4 comments
Closed

Error loading env file #222

blucompassai opened this issue Jun 28, 2019 · 4 comments
Assignees

Comments

@blucompassai
Copy link

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):

  • OS: Ubuntu
@tarpdalton
Copy link

tarpdalton commented Jul 1, 2019

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. image: buzzfeed/sso:v1.2.0

@Jusshersmith
Copy link
Contributor

Hi @blucompassai.

How did you get on with @tarpdalton's (thank you @tarpdalton!) suggestion?

Also, just so you're aware; version 2.0.0 has now been released (https://github.com/buzzfeed/sso/releases/tag/v2.0.0) which includes a lot of configuration changes (including the one that was causing what you saw). Please let us know if you have any issues with the new setup.

@Jusshersmith Jusshersmith self-assigned this Aug 6, 2019
@tl-alexandre-kaskasoli
Copy link

tl-alexandre-kaskasoli commented Jan 1, 2020

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.

@algoth
Copy link

algoth commented Aug 27, 2021

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?

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

5 participants