4

Looking to implement Oauth2 in my Chrome extension

I have been researching how to implement oauth2 on a chrome extension. I have been stuck for quite some time. I eventually got information to use chrome.identity in my background.ts file.

Here is my manifest.json

...
"permissions": [
    "identity"
],
"oauth2": {
    "client_id": "855289137547-bd37ghe68neqevqs47esitvc99rb5f8d.apps.googleusercontent.com",
    "scopes":["https://www.googleapis.com/auth/userinfo.email"]
  },
  
"background": {
    "scripts": [
        "background.js",
        "runtime.js"
    ]
},
...

Call the chrome.identity API

There is a method on the API that is called getAuthToken which I am trying to call. When I try to call this method I get the following:

// background.ts
chrome.identity.getAuthToken({ interactive: true }, (token)  => {
  // store token here
});

Error

Unchecked runtime.lastError: OAuth2 request failed: Service responded with error: 'bad client id: 855289137522-bd37ggg68neqevqs47esitvc99rb5f8d.apps.googleusercontent.com'.

I checked multiple times and I can confirm that that the id is the same as I my console developer credentials.

Maybe it needs a key in the manifest

I was assuming that I have to have a key in my manifest.json. So, I followed the documentation at the following link where it says to follow the steps:

  1. At the Developer Dashboard, click Add new item.
  2. Click Choose file and select the .zip extension directory and upload it.
  3. Without filling in additional fields, select Save Draft and return to dashboard.

Find the extension under Your Listings and click on more info. From the popup, copy the public key and add it to the manifest inside the unzipped directory under the "key" field.

However, I looked everywhere but could not find the "more info" link or any other info leading me to a key.

wOxxOm
  • 65,848
  • 11
  • 132
  • 136
jwize
  • 4,230
  • 1
  • 33
  • 51
  • 2
    The Developer Dashboard has 2 versions: old (chrome.google.com/webstore/developer/dashboard) and new (chrome.google.com/webstore/devconsole). You can access the "More info" link only on the old version. In the new version page, on the bottom left, you can click on "Show More" and then on "opt out" to access the old version. – Iván Nokonoko May 04 '20 at 10:07
  • Thank you for the help! Obviously, the documentation needs an update. I couldn't actually find the more info in the old link but the show more did lead me to the answer. However, I still haven't gotten the auth token but I will keep on trying. – jwize May 04 '20 at 20:08
  • Also, do I need to add the key header and footer in the key property? – jwize May 04 '20 at 20:17

2 Answers2

2

Key is available in the new UI --> Package on left side menu --> Public Key

hydroweaver
  • 109
  • 9
1

At of time of my post (August 2020), if you go to the Developer Dashboard, you will always be directed to the new UI, which doesn't contain the More Information section, which means you can't find the public key.

AFAIK there is no other way to get the public key. You can't substitute your application ID because it is a hashed version of the public key,

Look for the Welcome popup on the bottom left corner of the screen and click on opt out link in tiny font to revert to the legacy interface.

bytrangle
  • 979
  • 11
  • 9