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
It seems that the auth crate doesn't properly parse response errors when the authentication configuration is invalid.
I was trying to use GKE Workload Identity as the auth method behind the with_auth() function, and the crate just returned a decode error (probably because the response wasn't what the decoder expected), which made debugging my configuration more difficult.
What do you think about returning a clearer error message for client auth errors? Does that make sense?
I’d be happy to open a PR with this suggestion if you're open to it.
I agree with including the request URL and bytes of the response body in the error, as it is difficult to investigate whether that error actually occurred.
Hello,
It seems that the auth crate doesn't properly parse response errors when the authentication configuration is invalid.
I was trying to use GKE Workload Identity as the auth method behind the with_auth() function, and the crate just returned a decode error (probably because the response wasn't what the decoder expected), which made debugging my configuration more difficult.
What do you think about returning a clearer error message for client auth errors? Does that make sense?
I’d be happy to open a PR with this suggestion if you're open to it.
Just to clarify, Workload Identity on GKE works fine, this suggestion is only about improving the clarity of error messages in such cases.
The text was updated successfully, but these errors were encountered: