Publish Chrome Extension with my oAuth Client ID

[Shajia Abidi]

Hello, 

I am building a chrome extension that writes to google sheets and it is working as expected. Currently, I am using my clientID in the manifest.json, but I am wondering how would it work when I publish the chrome extension. I want the user to use their own clientID instead of mine.

Is there a way to update manifest.json with the user's clientID so they don't use mine? Or is there a way to add clientID elsewhere in my script? Or is there another way to write to google sheets without using clientID?

I'm using chrome.identity.getAuthToken every time the user makes the request to google sheets, but I also need the clientID to make it work. 

I'd love any help on it.

Thanks,

Shajia Abidi

[T S]

Maybe I'm missing something - they're meant to use yours.  The clientID is an identifier for your application, it signifies that when they perform the oauth flow they are giving your code the permission to act on their behalf.  A typical end user isn't going to want to set up their own OAuth client to use an extension. 

[Shajia Abidi]

Thank you for your response. I am a little confused here. Doesn't that also mean that every time they click on a submit button to make an API request, they will be using my API quota? SInce I am using the clientID from my google dashboard. 

[Deco]

Yes that's correct - it's how oAuth quotas work. What you are attempting to do in your original post is not possible.

Cheers,

Decklin 

--
You received this message because you are subscribed to the Google Groups "Chromium Extensions" group.
To unsubscribe from this group and stop receiving emails from it, send an email to chromium-extens...@chromium.org.
To view this discussion on the web visit https://groups.google.com/a/chromium.org/d/msgid/chromium-extensions/991d21e1-6add-4ebd-9054-2fde7755ab95n%40chromium.org.

[Shajia Abidi]

Thank you for clarifying that.