Chrome Add On v.s. API Token

Platform API
1

Hi,

We have a button in our own application to initiate a call. Where are using Token Implicit Grant for the token.

I am testing the Chrome Add-on, works great. But If I am logged in with the Chrome Add-on and I press the button I still need to login for the token. Is there a way to use the login/token from the Chrome Add-on?

2

If there's a session cookie available, the login will use it. If you've very recently logged in to the web page and the chrome add-on is still prompting for a login, I'm guessing that Chrome isolates the add-on for security and basically makes it run like it's in incognito mode. This would prevent it from having access to the session cookie.

I've only had minimal experience developing chrome add-ons and extensions, but I'm wondering if your add-on needs permissions to access the cookie. That could totally be a red herring; just an idea.

edit: I think the cookies and host permissions are worth looking into. From the page (emphasis mine):

To use the cookies API, you must declare the "cookies" permission in your manifest, along with host permissions for any hosts whose cookies you want to access.

3

Hi Tim,

In my case

  • First the user logs in with the Chrome App
  • User set his/her status on queue
  • When using the button for the first time user gets the prompting for a login.

I have 100+ seats that are going to use Chrome App and our own build 'buttons/call control'. Last thing I want is that all users must login twice...

I will check with development "declare the cookies"

4