:wave: Hi there!
We are currently using Descope to...
# ask-a-descopern
narrow-action-32367
06/21/2023, 4:45 PM👋 Hi there!
We are currently using Descope to implement SSO sign-up/sign-in functionality in our Chrome extension. However, we are facing an issue with the UI provided by the react sdk specifically when building a chrome extension. (the react app builds and works just fine). We're getting an eval error when the extension try to show the sign in UI (will provide stack trace soon)
❓ If you could provide guidance on how to properly manage the SSO implementation specifically for Chrome extensions that'd be great! thank you!
b
breezy-evening-56597
06/21/2023, 5:11 PM
@dazzling-oyster-96577 can you please have a look?
d
dazzling-oyster-96577
06/21/2023, 5:13 PMHi @narrow-action-32367, nice to meet you! Yes the stack trace would definitely be helpful, also if you would like to look into this and debug live over zoom we can do that as well.
dazzling-oyster-96577
06/21/2023, 5:14 PMBecause you mentioned
eval()dazzling-oyster-96577
06/21/2023, 5:16 PMCheck this out: https://developer.chrome.com/docs/extensions/mv3/sandboxingEval/
n
narrow-action-32367
06/22/2023, 1:20 PMHi Kevin, thank you for the answer! Is this means that we would need to run descope on a sandboxed file in order for it to work?
If we take this route and login the user within a sandboxed file, would we still have access to the current session, descope's hooks etc in the chrome extension?
narrow-action-32367
06/22/2023, 1:21 PMThis is the stack trace btw:
narrow-action-32367
06/22/2023, 1:25 PMwe think the issue is with this line within the web component: https://github.com/descope/descope-js/blob/main/packages/web-component/src/lib/descope-wc/DescopeWc.ts#L494-L554C4.
narrow-action-32367
06/22/2023, 1:28 PMlooping @numerous-businessperson-6660 from our team.
n
numerous-businessperson-6660
06/22/2023, 1:30 PMHey @dazzling-oyster-96577, @narrow-action-32367 sent the stacktrace here are some screenshots of what we see in the console as well.
d
dazzling-oyster-96577
06/22/2023, 8:43 PMYep I'm pretty sure it's a cross-site restriction that Chrome imposes on its extensions. In the web-js sdk function, we're fetching content from an API and there in lies the problem it looks like. Would you like to get on a call and we can discuss a workaround for this issue?
n
numerous-businessperson-6660
06/22/2023, 9:07 PMyup. I'm available!
numerous-businessperson-6660
06/22/2023, 9:07 PM@narrow-action-32367 is available too.
d
dazzling-oyster-96577
06/22/2023, 9:09 PMdazzling-oyster-96577
06/22/2023, 9:17 PMdazzling-oyster-96577
06/22/2023, 9:18 PM Copy code
"content_security_policy": "script-src 'self' 'unsafe-eval'; object-src 'self'",dazzling-oyster-96577
06/27/2023, 6:56 PMHi @narrow-action-32367, just wanted to give you an update. I'm still working on this with manifest v3. I was sick since Friday and wasn't able to finish it. I will give you an update when it is complete, and send you a link to my sample app.
n
narrow-action-32367
06/27/2023, 7:17 PMthanks for the update, @dazzling-oyster-96577!