You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I assume each app instance has its own secureLS instance with its own salt, such that one SecureLS can't decrypt a token set by another SecureLS. I get that that is a big point of security, but my use case is logging in via an API call to the backend using LS to set the token into LS using Cypress for E2E testing. If Cypress runtime uses one secure-ls import and Vue uses another, is it even possible for these to talk, with the right configuration or is that an impossibility? We're getting a could not parse JSON error in Cypress's console from secure-ls.js:256 and that would make sense if this is not possible to decrypt
The text was updated successfully, but these errors were encountered:
I assume each app instance has its own secureLS instance with its own salt, such that one SecureLS can't decrypt a token set by another SecureLS. I get that that is a big point of security, but my use case is logging in via an API call to the backend using LS to set the token into LS using Cypress for E2E testing. If Cypress runtime uses one secure-ls import and Vue uses another, is it even possible for these to talk, with the right configuration or is that an impossibility? We're getting a could not parse JSON error in Cypress's console from secure-ls.js:256 and that would make sense if this is not possible to decrypt
The text was updated successfully, but these errors were encountered: