I'm using web3auth through auth0. My issue is when refreshing the token. When our verifier on our backend deems the token expired, we use the getUserInfo() to get the up to date access token. However this token is the same as the original token that was already deemed expired. The token it get originally after login works fine so there shouldn't be an issue with verifying. Auth0 worked properly on it's own before adding web3auth.
Is there a bug with refreshing, or have we configured our combination of web3auth and auth0 incorrectly? Or is there some other issue?
I'm using web3auth through auth0. My issue is when refreshing the token. When our verifier on our backend deems the token expired, we use the getUserInfo() to get the up to date access token. However this token is the same as the original token that was already deemed expired. The token it get originally after login works fine so there shouldn't be an issue with verifying. Auth0 worked properly on it's own before adding web3auth.
Is there a bug with refreshing, or have we configured our combination of web3auth and auth0 incorrectly? Or is there some other issue?