We’re experiencing an intermittent issue where the okta-token-storage
value in session storage gets replaced by a string (the key) instead of the session information in JSON format. This causes a JSON parsing error, breaking the application.
We are not manually setting the session storage; rather, it’s being handled by the function passed to the OktaAuth
constructor in tokenManager.storage
, which is responsible for setting session storage items.
Lib used:
“@okta/okta-auth-js”: “^4.2.0”,
“@okta/okta-react”: “^4.0.0”,
React:
“react”: “^18.2.0”,