Trouble with Google Drive API Authentication: Redirect URI Mismatch

Other Questions Google drive
1

I’m struggling to set up the Google Drive API for my application’s file storage. I’m working with a basic Blazor Server app but can’t seem to get past the authentication process. Here’s what I’ve done:

  1. Configured the app on the Google Console.
  2. Downloaded the client_secret.json.
  3. Attempted to authorize using GoogleWebAuthorizationBroker.

However, I keep encountering a ‘redirect_uri_mismatch’ error, and the port number in the error message changes every time I run the app. Is this expected behavior?

Below is a simplified version of my code:

UserCredential cred;

async Task AuthSetup()
{
    var secrets = await GoogleClientSecrets.FromFileAsync("secrets.json");
    cred = await GoogleWebAuthorizationBroker.AuthorizeAsync(
        secrets.Secrets,
        new[] { DriveService.ScopeConstants.DriveFile },
        "user",
        CancellationToken.None);

    var driveService = new DriveService(new BaseClientService.Initializer
    {
        HttpClientInitializer = cred
    });
}

Has anyone encountered this issue? Is there a more effective way to handle Google Drive API authentication in 2024? Any help would be appreciated!

2

hey, been there before. the changing port is normal for blazor. try setting a fixed port in ur settings and use that in ur google console. check that client_secret.json is current-- sometimes google updates stuff.

3

I encountered a similar issue when integrating Google Drive API with a Blazor app. The changing port is indeed expected behavior for Blazor Server.

To resolve this, I’d recommend using a local redirect URI that doesn’t include a port, such as ‘http://localhost/callback’. Configure this in your Google Console project settings.

In your code, you might want to use GoogleAuthorizationCodeFlow instead of GoogleWebAuthorizationBroker. This gives you more control over the auth process.

Also, ensure your secrets.json file is up to date and matches your Google Console settings exactly. Sometimes, discrepancies here can cause unexpected authentication errors.

If you’re still stuck, consider using Fiddler or a similar tool to inspect the auth traffic. This can provide valuable insights into what’s going wrong during the redirect process.

4

I’ve been down this road before, and I feel your pain. The redirect URI mismatch is a common hurdle when setting up Google Drive API authentication, especially with Blazor Server apps.

Here’s what worked for me: instead of relying on the dynamic port, I set up a specific redirect URI in the Google Console. I used something like “http://localhost:5000/signin-google” and made sure to use the same URI in my code.

Also, I found it helpful to use the Google.Apis.Auth.AspNetCore3 package. It simplifies the auth process quite a bit. You might want to look into using the GoogleOpenIdConnectAuthenticationOptions class.

One last tip: double-check that your client_secret.json file is in the right location and that its contents match what’s in the Google Console. Sometimes, the simplest oversights can cause the biggest headaches.

Keep at it - once you get past this hurdle, working with the Google Drive API becomes much smoother!