playermaio.blogg.se

Here is a more in depth walkthrough in order to get OAuth working within a Chrome Extension:Įssentially you need to upload your extension as a draft in the Chrome Developer Dashboard. As long as you use your Google account in the extension you shouldn't need to go through the verification process. I would also make sure to configure your consent screen to add Google Drive which will be a sensitive permission. This can then be added to the manifest.json. The article then states you need to remove the packed extension and load your unpacked dev extension.įor the client_id you need to create a new OAuth Client ID (Web Application) and add a redirect URI in the following structure:

Copy the key value and add it to your extension.

Navigating in windows file explorer to C:\Users\\AppData\Local\Google\Chrome\User Data\Default\Extensions\\.

I would recommend the Google's method since it's a lot less configuration, but to get the property values its noting you can do the following: It's an extension not an application so I guess I am in the wrong place. Is the google developer's console the correct place to generate the client_id for a chrome extension? There's a warning that says "To protect you and your users, your consent screen and application need to be verified by Google". I can then go to Library/Application Support/Google/Chrome/Default/Extensions/'

This suggests that the key can be found by looking at the "id" field of the extension in chrome://extensions. I tried the instructions in this article: I haven't published the extension so far and am struggling to work out what the value of the key and the client_id should be in the manifest. I am trying to get a google extension to use the Google Drive api.