Describe the content issue:
There is a difficulty with session storage that other storage methods do not have, and it would be very helpful to link to best practices for dealing with it: Session storage is tied to each tab and so a webapp that allows multiple tabs to be opened for it has no obvious way of extending the session token of an already-open tab to a new tab nor of syncing the session tokens across all its tabs.
URL page where content issue is:
https://docs.amplify.aws/react/build-a-backend/auth/concepts/tokens-and-credentials/#browser-session-storage
Describe the content issue:
There is a difficulty with session storage that other storage methods do not have, and it would be very helpful to link to best practices for dealing with it: Session storage is tied to each tab and so a webapp that allows multiple tabs to be opened for it has no obvious way of extending the session token of an already-open tab to a new tab nor of syncing the session tokens across all its tabs.
URL page where content issue is:
https://docs.amplify.aws/react/build-a-backend/auth/concepts/tokens-and-credentials/#browser-session-storage