iOS-SDK idToken(jwt) Expired issue

Help - Plug n Play
,
1

Hi, I’m developing an iOS app using Web3Auth to allow users to log in with OAuth and create a wallet for them. I’m also using the web3auth idToken (JWT) for user communication with our backend API as the Authorization token. The issue I’m currently facing is that I followed the SDK-ios-example approach, but users need to log in again after 24 hours, which is causing a poor user experience. I’d like to know how to resolve this issue.

  • I’ve checked the Web3Auth idToken documentation, and it mentions that it has a 24-hour expiration period.
  • I tried switching to Custom Auth to get the oAuthIdToken, but even after 24 hours, I still can’t obtain the Web3Auth.state during SDK initialization. Is this related to SessionID?
  • The SessionManager’s sessionTime can only be set for a maximum of 7 days. Does this mean that users have to log in again every seven days, no matter what?
  • When developing a mobile app using Web3Auth, is it advisable for developers to retrieve the private key after login for future transaction handling? Or is there a solution to avoid users having to log in again every time they use Web3Auth for login?
2

@imjavanchen Welcome Aboard!

Your request has been forwarded to our Dev team and we will get back with further updates once more information becomes available.

In the meantime, you can read this thread Using Auth0 with Web3Auth - #5 by rafael.rodriguez

1 Like
3

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.