# \[Archive\] Using Web3Auth with Auth0, initializing wallet after login

**URL:** <https://builder.metamask.io/t/archive-using-web3auth-with-auth0-initializing-wallet-after-login/2074>\
**Category:** Embedded Wallets (Web3Auth)\
**Created:** [February 10, 2023, 5:45am UTC](https://builder.metamask.io/t/archive-using-web3auth-with-auth0-initializing-wallet-after-login/2074 "2023-02-10T05:45:57Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![githubdiscussions](https://avatars.discourse-cdn.com/v4/letter/g/13edae/32.png) [@githubdiscussions](https://builder.metamask.io/u/githubdiscussions)\
**Post date:** [February 10, 2023, 5:45am UTC](https://builder.metamask.io/t/archive-using-web3auth-with-auth0-initializing-wallet-after-login/2074/1 "2023-02-10T05:45:57Z")

</div>

> **🏛 Archived Content from Web3Auth Community**
> 
> This topic was originally posted by **githubdiscussions** on 2/10/2023.  
> This content has been migrated from our previous community forum to preserve valuable discussions.

* * *

The docs have [this guide](https://web3auth.io/docs/guides/auth0#additional-reading-setup-custom-authentication-using-auth0-rwa) and [this documentation](https://marketplace.auth0.com/integrations/web3auth) on Auth0's website that outline the Web3Auth + Auth0 login model where the Auth0 login is tied directly to the Web3Auth wallet generation (see step 4 in the diagram below - the token flows directly from Auth0). This seems to be the case in both openlogin-adapter usage and with self-host.

Instead, is it possible to initialize the Web3Auth wallet **after** a user logs in via Auth0, by having my app pass the JWT back to Web3Auth? For context, we are trying to decouple the "login to our platform" and "create wallet" flows in our platform. Basically I want my app to be able to request the JWT back from Auth0 for the authenticated user and send to Web3Auth to initialize the wallet at some point in the user flow beyond login.

[![image](https://canada1.discourse-cdn.com/flex011/uploads/metamaskbuilderhub/original/2X/e/e0a1a0e1e381fc3007ae69366d0ac360214e055d.jpeg)](https://user-images.githubusercontent.com/10749551/218010883-566dd017-ad46-4088-aef2-1e6ea59fbc6b.png)

  
   
 Originally posted by: [cfern18](https://github.com/cfern18)  
   
 Check the discussion at: [https://github.com/orgs/Web3Auth/discussions/1310](https://github.com/orgs/Web3Auth/discussions/1310)

---

<div class="post-metadata">

**Author:** ![githubdiscussions](https://avatars.discourse-cdn.com/v4/letter/g/13edae/32.png) [@githubdiscussions](https://builder.metamask.io/u/githubdiscussions)\
**Post date:** [February 10, 2023, 11:57am UTC](https://builder.metamask.io/t/archive-using-web3auth-with-auth0-initializing-wallet-after-login/2074/2 "2023-02-10T11:57:34Z")

</div>

Step 4 mentioned is just passing idToken to web3auth sdk.  
there is no software code tied between except passing in idToken

You however would need to configure the Auth0 at the dashboard ( configuration for authenticating Auth0 token)

  
   
 Originally posted by: [ieow](https://github.com/ieow)

---

<div class="post-metadata">

**Author:** ![githubdiscussions](https://avatars.discourse-cdn.com/v4/letter/g/13edae/32.png) [@githubdiscussions](https://builder.metamask.io/u/githubdiscussions)\
**Post date:** [February 20, 2023, 2:02am UTC](https://builder.metamask.io/t/archive-using-web3auth-with-auth0-initializing-wallet-after-login/2074/3 "2023-02-20T02:02:47Z")

</div>

Sure, you will have to refer self-host solution here  
[https://web3auth.io/docs/self-hosting](https://web3auth.io/docs/self-hosting)

  
   
 Originally posted by: [ieow](https://github.com/ieow)