Open stigi opened 11 years ago
I encountered the same issue, and authentication failed when I had a long set of parameters that were encoded as multipart/form data, from a dictionary to JSON to data. But I manually converted the httpbody parameters into form-urlencoded data as a string like "client_id=...&client_data=...", it was still sent in the httpbody but now with Content-Type = application/x-www-form-urlencoded, and it worked. Perhaps there could be a toggle to send data that way instead? This is in
According to #72 and others there are APIs that do no accept the token request parameters in the POST form body. Such APIs are
It might be possible to add a configuration for such APIs that sends the parameters in the query string. But let's discuss this first, as those APIs are clearly not implementing the OAuth2 standard correctly. See the spec for more info: