Client Authentication Failed Error

[PaulWestenthanner]

When trying to run the example app, I get an Error 302 with the following message:
{"error":"invalid_client","error_description":"Client authentication failed","message":"Client authentication failed"}

I've created my client_id and client_secret and can confirm that they are actually read correctly form the .env file. Any ideas what the problem could be?

[lakinwecker]

Huh, strange, it's no longer working for me either. I'll look into it.

[lakinwecker]

Ah. I think it's because pipenv shell loads the .env file when you first run it. So if you run pipenv shell before you run the app it will use the old values. I'll see if I can fix it, but the work around is to just make sure your .env is setup properly, and then exit your shell and start it again and run pipenv shell a second time.

[paulharris]

I got the same issue.
For me, my server is behind a nginx https forwarding proxy, so my URLs require https:// at the front.
however,
your app.py example has this call:
redirect_uri = url_for("authorize", _external=True)
which generates a http url. Its _external=True so its not using the X-Forwarded-Proto header from nginx to generate the url

So, the solution is to change that line to:
redirect_uri = url_for("authorize", _external=True, _scheme='https')

Problem solved!

[lakinwecker]

@paulharris any chance you'd be willing to make the scheme configurable via the env and then use it ? I'd happily accept a PR for this.

[paulharris]

I've love to but I'm too snowed in, and I'm not that experienced with Python so would be better if you did it the right way the first time...
Big Thanks for the library, its working nicely for me now!

[lakinwecker]

Ok, no worries. I'll see when I can find time