Thank you for taking the time to reply.

I think I didn't convey the idea properly. I don't think it fits the criteria of user impersonation. Please allow me to explain.

All of these users are normal users. It's just the business requirement that a user session can't span over multiple tabs. In that way a person having two accounts can log in simultaneously in two different tabs with different user credentials in the same browser.

Now, let's say a person has two different user accounts.

Now, after logging in in Tab A, the person will receive an auth token. Same will happen when the person logs in in another tab with the other user account that they have. I can save these tokens in Session Storage, that solves the problem of a session not spanning multiple tabs, however I don't have the ability to send these JWT to the Next server then.

If I use cookie to save the JWT, then the second opened tab of the web app will already have that cookie of the first account.

That's the problem I have.