"Unable to set storage: okta-shared-token-storage" error when used inside iframe

Questions OAuth/OIDC
1

Hello,
We have 2 react apps , let’s call them App A and App B. App A is an iframe inside App B. Both are using okta-react to log in the users via okta. Users log in to App B (parent app) and navigate to some page, and the page runs App A(child app) inside the iframe. It seems to be working as expected.

However, some users face : “AuthSdkError: unable to set storage: okta-shared-transaction-storage” error. This error is inconsistent, some users face it , some users don’t. When we ask the users to purge application storage and relogin , the issue gets fixed. So , we don’t know how to reproduce this issue. We captured the console logs below from one of the user (not sure if they are relavant though):

“WARN: a saved auth transaction exists in storage. This may indicate another auth flow is already in progress.”
“WARN: This browser doesn’t support localStorage. Switching to sessionStorage.”

Browser: chrome version 126.0.6478.127 (Official Build) (64-bit)

How can we fix this issue without users manually clearing application cache ?

2

Hello @naltun,

Are you using the most updated versions of your SDKs? I see that there were some fixes for this issue implemented in some older versions of our auth library, so if you’re using an older version you might update it.

If you are on the newest version of React, the Sign-in Widget, and Auth-js and you are still experiencing this error I’d encourage you to add to the thread I see on this topic: AuthSdkError: Unable to retrieve OAuth redirect params from storage · Issue #488 · okta/okta-auth-js · GitHub and/or open a new issue if you’re seeing different output than what’s being described there. You can also open a Support case so we can assist you with investigating this issue.

3

Hello @daniel.sanders ,

Thanks for the reply. Yes we are using version 7.5.0 , not the latest but recent version.
The issue seems to happen when there’s not enough space in localStorage. I was able to reproduce the issue by filling localStorage quota and try to login via okta.