<iframe src="https://www.googletagmanager.com/ns.html?id=GTM-M74D8PB" height="0" width="0" style="display:none;visibility:hidden">
Loading
Skip to NavigationSkip to Main Content
0D51Y00008peJ3ISAUOkta Classic EngineIntegrationsAnswered2020-08-19T23:37:48.000Z2020-07-05T18:03:01.000Z2020-08-19T23:37:48.000Z

GarryC.05733 (Customer) asked a question.

Chrome extension Auth

I am creating a chrome extension and look to authenticate a user.

 

When they first install the extension and click it we redirect them to the main site (in this case it localhost:3000)

 

- once they sign in and are given the ?code= we send them to the /oauth2/default/v1/token endpoint to grab the accessToken and IdToken.

 

this all works perfectly but the Cookies are not set as the chrome extension domain is chrome-extension://imoloeebnehinfjpmeegpcdkhbnlomhg and not localhost:3000.

 

Is there a way to get the cookie moved over to the to chrome extension so when I need to refresh the token it can be done with no prompt?


  • Hi Gary,

    The cookies will be set on the domain that initiated the request, hence it is set on localhost. There is no way that I know of to move the cookie to chrome extension.

    Thanks

This question is closed.
Loading
Chrome extension Auth