Wagmi callback after Private key retrieval with tKey SDK

When asking for help in this category, please make sure to provide the following details:

  • SDK Version:
    @web3auth/base”: “^7.0.4”,
    @web3auth/ethereum-provider”: “^7.0.4”,
    @web3auth/no-modal”: “^7.1.1”,
    @web3auth/openlogin-adapter”: “^7.0.4”,
    @web3auth/torus-wallet-connector-plugin”: “^7.0.4”,
    @web3auth/web3auth-wagmi-connector”: “^5.0.1”,
    “wagmi”: “1.4.5”

  • Platform: MacOs

  • If the issue is related to Custom Authentication, please include the following information (optional):

    • Verifier Name: Auth0
    • JWKS Endpoint: Would this be Auth0 domain? I’m using https://h3aven.us.auth0.com (H3aven is my company’s name)
    • Sample idToken (JWT): “eyJhbGciOiJSUzI1NiIsInR5cCI6IkpXVCIsImtpZCI6InBuNVpLcnYtZkRCcTFVZWhmNFNBWCJ9.eyJuaWNrbmFtZSI6ImpvYW9oNi5jb3N0YSs0IiwibmFtZSI6ImpvYW9oNi5jb3N0YSs0QGdtYWlsLmNvbSIsInBpY3R1cmUiOiJodHRwczovL3MuZ3JhdmF0YXIuY29tL2F2YXRhci83ZmM1MWU3ZWUzZDg0MDYyNjBhM2U2NzhlZmRiMGRhNj9zPTQ4MCZyPXBnJmQ9aHR0cHMlM0ElMkYlMkZjZG4uYXV0aDAuY29tJTJGYXZhdGFycyUyRmpvLnBuZyIsInVwZGF0ZWRfYXQiOiIyMDI0LTAxLTE3VDAxOjMwOjQzLjYyM1oiLCJlbWFpbCI6ImpvYW9oNi5jb3N0YSs0QGdtYWlsLmNvbSIsImVtYWlsX3ZlcmlmaWVkIjpmYWxzZSwiaXNzIjoiaHR0cHM6Ly9oM2F2ZW4udXMuYXV0aDAuY29tLyIsImF1ZCI6InloemdSM1l6ZGt2MlpJSWc2UndvNUNoMHZqeVpHRU52IiwiaWF0IjoxNzA1NDU1MDUyLCJleHAiOjE3MDU0OTEwNTIsInN1YiI6ImF1dGgwfDY1YTcyZGMzNjhhOThiODQ4MzM3NjI3MCIsImF1dGhfdGltZSI6MTcwNTQ1NTA0MywiYXRfaGFzaCI6Im03ejVlc0MyWGNDOHdqaGE0YkZmc1EiLCJzaWQiOiIxYlRvcmNhRnVaTk9tRVl6WkVFdmlaYkl2OXdaWFh6RiIsIm5vbmNlIjoicG95eWp3bG52MWwifQ.GJsPNDcHJ__ln4emdjHR9bBBcTU7XVG3vhW2_bPXnTCVMhEVBLjWNTMs8d1sI4NjzrrMIpKLlTN_O3K7dFvtQ8SgIYHHC_Ioqy4_yitXVm13Vs71FURBFjrRmnJ594vXgE-NxjsZqnZhHoIVB6j3_5LH2LhbNgllDZa6OL-hi81kGSw89lDxzHlL1iSSpXvSQZB5VtbYgxjAti38IGMPep9V8WW1oP56BRllhot0BtUVbCDrN7m5RtQ8FJZvApFsj68vkfsUnzlmjtv8GNeK8ohS2cnpQjWi8LZEH2rWwvZS_Z3T8HLQFDLlPMy1hqvLnxqoOwS_QAkHIbU80zdSxQ”

Also, kindly provide the Web3Auth initialization and login code snippet below. This will help us better understand your issue and provide you with the necessary assistance.

  const web3AuthInstance = new Web3AuthNoModal({
    clientId,
    chainConfig,
    web3AuthNetwork: networkType,
    enableLogging: true,
  });

  const adapter = new OpenloginAdapter({
    privateKeyProvider,
    adapterSettings: {
      uxMode: 'popup',
      loginConfig: {
        jwt: {
          verifier: auth0.verifier,
          typeOfLogin: 'jwt', // Pass on the login provider of the verifier you've created
          clientId: auth0.clientId, // Pass on the Auth0 `Client ID` here
        },
      },
    },
  });

  web3AuthMicrosoftInstance.configureAdapter(adapter);

 new Web3AuthConnector({
        chains,
        options: {
          web3AuthInstance,
          loginParams: {
             loginProvider: LOGIN_PROVIDER.JWT,
            extraLoginOptions: {
                domain: auth0.domain,
                verifierIdField: 'sub',
                connection: 'Username-Password-Authentication',
                redirect_uri: auth0.redirect_uri,
             },
          },
        },
      }),

It then opens a popup for me to login with Auth0, I do it, and I’m redirected to a cofigured url on my application where I try to get 2/3 shares using tKey SDK.
I’m able to get the shares and retrieve the user’s private key, but I’m stuck after this point. Would like to be redirected back to wagmi and be able to connect with the provider, but I can’t find an example code on this.

@cloud Thanks for your patience.

Your request has been forwarded to our Dev team and we will get back with further updates.

Please check the demo in this demo

This does not help. The only demo that uses Auth 0 integration is using web3auth v6 (I’m using v7), and I’m also not using Rainbowkit.

Please read my full post.

Are you using Web3Auth plug and play no modal sdk or tkey sdk? Our connector doesn’t support tkey sdk directly.

Also from auth0 configuration remove the redirect_uri parameter