Improve Logout Behavior and Session Management

[gkatrakazas]

Currently, the logout function in SessionContext is called on user logout. However, in certain cases, such as:

• User inactivity leading to automatic logout
• Login/Signup from a different user in any tab leading to automatic logout the other users tabs.

The SessionStorage from api/index.ts is not cleaned up, leading to potential issues.
Additionally, it would be beneficial to set sessionStorage.setItem('freshLogin', 'true'); during the logout process. This ensures any login/signup from each logout tab will be login with clean url

[emlun]

PR #483 resolves part of this, but the issue with logging in to the wrong user is slightly different. The cause is that after successfully logging in and unlocking the keystore, this code runs to update the cached users (to copy the prfKeys from the logged-in user's privateData to the matching cached user):

wallet-frontend/src/services/LocalStorageKeystore.ts

Lines 118 to 134 in 6e8ebfe

	if (privateData && userHandleB64u && (userHandleB64u === globalUserHandleB64u)) {
	// When PRF keys are added, deleted or edited in any tab,
	// propagate changes to cached users
	setCachedUsers((cachedUsers) => cachedUsers.map((cu) => {
	if (cu.userHandleB64u === userHandleB64u) {
	return {
	...cu,
	prfKeys: privateData.prfKeys.map((keyInfo) => ({
	credentialId: keyInfo.credentialId,
	transports: keyInfo.transports,
	prfSalt: keyInfo.prfSalt,
	})),
	};
	} else {
	return cu;
	}
	}));

But when there are two tabs open simultaneously, that code runs simultaneously in both tabs, and the globalUserHandleB64u is different between the two tabs. The user1 tab has globalUserHandleB64u set to the user handle of user1, and the user2 tab has globalUserHandleB64u set to the user handle of user2. So the result is that both cached users get updated with user2's prfKeys. I'm looking into this too, but this is a bit trickier to solve.

[gkatrakazas]

This issue was fixed in PR #488.