You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When requesting a token from a broken provider (e.g. www.googleapis.com), if there is a client_id but not a client_secret, the client_id isn't included in the request generated by the oauth2 library, leading to a 400 response. This seems to have been introduced in 4464e78, and is contrary to the change description, so was presumably unintended.
The attached test program illustrates the bug, giving
Error: oauth2: cannot fetch token: 400 Bad Request
Response: {
"error" : "invalid_request",
"error_description" : "Could not determine client ID from request."
}
with top of tree.
The patch below fixes it for me, but I'm not an oauth expert, so don't know if this is the appropriate fix.
When requesting a token from a broken provider (e.g. www.googleapis.com), if there is a client_id but not a client_secret, the client_id isn't included in the request generated by the oauth2 library, leading to a 400 response. This seems to have been introduced in 4464e78, and is contrary to the change description, so was presumably unintended.
The attached test program illustrates the bug, giving
with top of tree.
The patch below fixes it for me, but I'm not an oauth expert, so don't know if this is the appropriate fix.
Test case:
oauth.go.txt
The text was updated successfully, but these errors were encountered: