Vague Authentication failure
See original GitHub issueI’m getting a vague authentication failure from GetApplicationDefaultAsync()
.
{“Error reading credential file from location C:\ArtofShell\Google\Vision\GoogleCred.json: Bad Data.\r\n\nPlease check the value of the Environment Variable GOOGLE_APPLICATION_CREDENTIALS”}
Here’s my code:
Environment.SetEnvironmentVariable("GOOGLE_APPLICATION_CREDENTIALS", @"C:\ArtofShell\Google\Vision\GoogleCred.json");
var credential = await GoogleCredential.GetApplicationDefaultAsync();
Repro steps:
- I created a Service Account
- I downloaded the credential file
- I set the environment variable to the path of the credential file
- Attempted to call GetApplicationDefaultAsync()
Cheers, Trevor Sullivan Microsoft MVP: Cloud & Data Center Management https://trevorsullivan.net https://twitter.com/pcgeek86
Issue Analytics
- State:
- Created 7 years ago
- Comments:23 (1 by maintainers)
Top Results From Across the Web
tightvnc - VNC authentication failure
VNC uses a separate password system. It does not check passwords against /etc/passwd but rather against ~/.vnc/passwd, which contains a ...
Read more >AUTHENTICATION-FAILED( ) method
This authentication failure signifies that the application or database user identity in the registered domain is not authentic.
Read more >Authentication Failures - 21745 Information Needed
the Authenticate failure came in because of insufficient access to the user creds which was input for credential based scanning.
Read more >Horizon Client authentication failure
Client cert inspection fails when a certificate is not received or the certificate received does not pass validation. Maybe the middle ware for...
Read more >User name not found or incorrect password error message ...
The reason would be security: it prevents finding out which user names exist based on failed attempts. This should be balanced with the...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
Our mistake – we thought we saw a pattern of failures after the latest release, but it turned out to be a problem in our own code. Please excuse the false alarm.
Hooray - glad it’s sorted. Chris’s recent change means that from 1.32.2 onwards, you won’t need to go to all the extra effort to get at the original exception. It’ll just be in the InnerException.