#DRIVE SCOPE AUTHORIZATION HOW TO#
#DRIVE SCOPE AUTHORIZATION FULL#
#DRIVE SCOPE AUTHORIZATION CODE#

/ public static readonly string SCOPES = new String / /// The OAuth2.0 scopes required by your project. / public static readonly string CLIENT_SECRET = ' >' / /// The OAuth2.0 Client secret of your project. / public static readonly string CLIENT_ID = ' >' / /// The OAuth2.0 Client ID of your project. For this reason, when the application keys are generated, Google must be told it is forĪn 'installed application' so that it treats communications with a higher level of suspicion.

#DRIVE SCOPE AUTHORIZATION CODE#

NET developers.įor installed applications, the two required keys are kept in the code (see theĬlientCredentials class below) and not really considered to be a secret because the code could be easilyĭecompiled or the JSON intercepted with a proxy tool like Fiddler.

The trick is to get the access token because that part of the process is not very well documented. All of this is done in JSON and is well defined in both Google's APIĭocumentation and other OAuth2.0 documents. It will return an access token to be passed with all of the service calls. Refer to the Authorization section of the Google APIĭocumentation for the service(s) you wish to use.) The authorization service will check to see if the application is authorized to use the requested scopes and if so, ( Note: The authorization scopes, included in the SCOPES array below, are different for each service. Generally speaking, Google's OAuth mechanism requires the application requesting access to presentĪ client ID (which identifies the application to Google) and a client secret to an authorization service endpoint along with the scope(s) the application wishes to access. The authorization mechanisms are based on OAuth 2.0. (For Google Drive Authorization information see the Google Drive Authorization API Docs.) Many Google Services require two types of authentication the user must be authenticated (logged in) and the application must be explicitly authorized by the user. The upside is that the authorization stepsĪre pretty generic and can be applied to just about all of Google's API services which includes Tasks, Calendar, Maps, etc so you can use this projectĪs a basis for accessing many of Google's API Services. To get to a working WPF solution, I had to reverse engineer several Google sample projects. NET sample but it is an ASP MVC application and not real helpful for those of us working in WPF, WinForms,

#DRIVE SCOPE AUTHORIZATION FULL#

Google provides a full application, called Dr. Google's documentation reads like stereo instructions and there are not many examples out there that can be used for guidance. Tokens and use them on subsequent requests.

#DRIVE SCOPE AUTHORIZATION HOW TO#

The complication was in the Authorization sequence and how to cache those The actual upload is very easy as Google provides all of the libraries for you to use.

(Google users can revoke authorizations to their Google Services in their user control panel.) Then silently upload the chosen file from then on provided the application remains authorized. The result is a pretty clean flow which will prompt the user the first time but Where my application differs from the other samples I found is that my application extends the Google sample code to store the authorization tokens and use them in subsequentĪccesses so the user is not prompted to authorize the application every time the program is run. If needed, it will open a browser so you can authorize the access and, provided you OK it, the program will upload the file you picked into your Google Drive. Select a file and the application will attempt to authenticate with Click the buttonĪnd an open-file dialog will prompt you to select a file to upload. The attached source code is a very simple WPF application that, when run, will open a window with a single button.

So I started digging into the problem and when I found a solution, I felt that I should share it here. Although their sample worked, it required explicit authorization each time it was run and it didn't really address how NET beyond a very simple sample providedīy Google. What I discovered was a lack of any documentation or working examples for doing this in. The purpose was to make the data easily accessibleįor later analysis in Excel or some other program. I wanted to have was the ability to store the data that the program logged into a user's Google Drive. When designing my entry into the App Innovation contest (if you are interested, it is called Rev Warrior and can

Drive scope authorization