I hope this message finds you well. I have been using web3auth in conjunction with Firebase for Google account authentication. The login and logout functionality seems to be working fine. However, upon inspecting the browser’s localStorage after logging out, I noticed that the id_token of the previously logged-in user is still present. This means that personal information such as the user’s name and email address can still be retrieved from the id_token, which I believe is a concern for applications handling sensitive user data.
I have thoroughly checked the web3auth documentation but couldn’t find any information regarding the removal of these user details after logout. Is there a way provided by web3auth to delete this information after a user logs out?
It appears that you are currently utilizing an outdated version of our SDK. However, I’m pleased to inform you that the latest SDK has already resolved this problem. To resolve this issue, kindly upgrade to v6.1.1.
I upgraded my Web3Auth version to 6.1.1 and tried it.
As a result, the only thing that changed was the location where it was stored from the last time.
I was able to retrieve the personal information of the person who logged in last time after logging out.