google-drive-api | Name : Khwanchai Kaewyos Email : khwanchai @ gmail | Email library

The redirect uri must exactly match the one you have registered in Google developer console

If we look at your image you have the following two redirect uris registered

• http://localhost:60581/
• http://localhost:60581/api/TwilioWP/CallGoogleAPI

This means that Google will accept only those two redirect uris from your application. The test is an exact match.

Now if we look at the error message we can see that your application is sending

• http://127.0.0.1:57628/authorize/

As you can see this does not match the ones you have registered. What you should do is copy that one and add it.

Note if your ide is changing ports you need to set it to a static port or its not going to work. It needs to match exactly

Google OAuth2: How the fix redirect_uri_mismatch error. Part 2 server sided web applications

The tutorial you are following uses GoogleWebAuthorizationBroker.AuthorizeAsync This method is designed for use with an installed application. So in fact the credentials and client type you are using is wrong. If you want to use that code you need to create native or desktop client.

If you try to host this as it is it will attempt to open the web browser on the server. When what you need to do is open the web browser for user consent on the users machine. You should be following web-applications-asp.net-core-3 if you want to be able to authorize a user using your web application.

I offer you my tutorial on Asp .net core 3 and Google login which has a link to the YouTube video on the same topic.

So the real cause of your problem is that you are using code for an installed application which has a default redirect Uri of http://127.0.0.1:{Port}/authorize/ and you are trying to use this for a web application. Which will need to have the host set to that of your web domain.

I have been in touch with the author of the tutorial you are following. I suspect they will be addressing the issue soon. Twitter thread

I think that in your situation, it is required to use get method instead of export method. Because export method is used for Google Docs files (Document, Spreadsheet, Slides and so on). When your script is modified, how about the following modification?

The URI that Google shows isn't even a part of the website, nor is a URI that I supplied to Google, so I have no idea where it's coming from.

The redirect uri is built buy the client library you are using. Your app is set to run http not https its running localhost and not hosted so its 127.0.0.1 the port is also either being randomly generated by your app or something that you have set up statically. the /authorize is attached again by the client library.

The redirect uri is the location your code is prepared to accept the response from the authorization server. This URI needs to be configured in Google cloud console. The easiest solution is to copy it exactly and add it as a redirect uri in Google cloud console. Just make sure that your app is set to use a static port if the port changes its not going to work.

This video will show you how to add it. Google OAuth2: How the fix redirect_uri_mismatch error. Part 2 server sided web applications.

I understand that you have an array of Drive file links, and you want to download them locally using Python. I am assuming that you want to to download files stored on Drive, not Workspace files (i.e. Docs, Sheets…). You can do it very easily by following the Drive API Python quickstart guide. That walkthrough will install all the necessary dependencies and show you an example code. Then, you only have to edit the main function to download the files instead of the sample operations.

To download the Python files you only need to know its id and use the Files.get method. I see that you already know the ids, so you are ready to make the request. To build the request you should introduce the id of the file and set the parameter alt to the value media. If you are using the example from the paragraph above, you can do it just by using the id like this example. If those guides don't work for you, please let me know.

You need to add the X-Goog-Drive-Resource-Keys header in your request. The simplest way to do that in the client libraries is via request interceptors. It's a little clunky, but not actually complicated:

The first problem you are having is that you are using GoogleWebAuthorizationBroker.AuthorizeAsync which is designed to work with installed applications only its not going to work with Asp .net

For asp .net MVC you should be doing the following

There is no issue with your code.

The code you provided matches exactly with what I have used to perform the same test.

There is an account issue with your permission to access that API. If you are unable to find the issue in your settings, I would recommend reaching out directly to Google.

The https://www.googleapis.com/auth/drive.file scope allows you to give a per-file access to files which have been created or opened by your app. Therefore, if the files have been upload manually and not from your app, this scope won't give you the access you require.

As for sharing the files with your application, you might find useful the example listed here in order to prompt a user to share the files wanted.

• Drive API v3 Authenticate Your Users;

• Google Picker API.

You can call @future method from trigger and can call create folder method by using access token and correct parameters. You can refer below code for folder creation.