Some parameters generate invalid HTTP request for UserInfo

[fogzot]

Specifing some parameters like ClientId or ClientSecret in UserInfoRequest result in a GET HTTP request with a body. This is wrong and is a problem, especially for applications hosted on services like Google Cloud that refuse to route GET/DELETE HTTP requests with a body.

Calling GetUserInfoAsync() with extra parameters should probably ingore them or throw an exception.

[leastprivilege]

Will look into it for v5. Why are you setting those parameters?

[fogzot]

Sorry for the late response. It was an error in my code and I lost a lot of time before discovering that the generated request was "invalid". There is no real reason for calling GetUserInfoAsync() with extra parameters, that's why I suggested to ignore them or return an error.

[leastprivilege]

feel free to PR

[brockallen]

What's our status on this request?

[josephdecock]

I had some feedback on the linked PR, and then it was closed by the submitter.

[josephdecock]

As to what we do with this now, I'm not sure, but I don't think this is a high priority. Maybe keep the issue around in case someone wants to take another crack at it?