WaspW
Wasp10mo ago
13 replies
NEROX

API auth with a Chrome Extension (third party)

I'm building a Chrome extension which makes Auth calls to my app's API.

What this extension does is to access the local storage to get the wasp:sessionId and with it make the API calls.

The problem I have is that I need to have the app page open to access the wasp:sessionId.

Isn't it unsafe to store this sessionId in the extension? For that reason before making a call, I access the value in local storage.

Maybe this approach is not the right one.

Maybe this is not related with Wasp
Was this page helpful?