-
Notifications
You must be signed in to change notification settings - Fork 217
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
Issue when working with Hydra #44
Comments
It appears Google are quite naughty here... https://tools.ietf.org/html/rfc6749#section-2.3.1
|
It appears google does have a setting to use headers:
That's in the constructor of OAuth2WebServerFlow. |
While that's in the constructor, it looks like we're using flow_from_clientsecrets to create the instance, which doesn't provide an option to specify the code in the header. |
I've managed to get it working by monkey patching _flow_for_request:
The code is similar to _get_token_info. I did have to change the following line:
by adding a decode('utf-8') at the end. Otherwise the string was coming out as "Basic b'encoded value'". (e.g. with the b and single quotes around it). I'm wondering if the line in _get_token_info needs the decode('utf-8') bit as well. I'll submit a PR with the change to _flow_for_request. |
I'm looking to use this with Hydra. When handling oidc_callback, I get an error:
On the hydra logs, I see this:
It appears hydra wants "code" to be in the Authorization Header. ory/hydra#174 would suggest as much. Is there a way around this? It appears the (now deprecated) oauth client is putting the code in the POST body.
The text was updated successfully, but these errors were encountered: