discord provider requires "identify" scope

Nobody has claimed this yet.

This might be a fairly naive problem on my behalf, this is fairly new to me.

I have successfully used the google provider with just the "email" scope.

When I try the same with discord, when the callback is called I get an error:

discord responded with a 401 trying to fetch user information

I suspect the returned body of the request made in FetchUser has something interesting, but I'm not familiar enough with net/http yet to work out how to inject my own client which can expose that.

If I add the "identify" scope, things work correctly.

Start at the Discord provider's FetchUser path and reproduce the callback with only the email scope, then compare it with the working identify-scope case. Inspect the HTTP response involved in the 401 and determine whether the provider behavior or its scope requirements need to be clarified; verify the result through the callback flow.

Written by the indexing model from the issue text.