We are currently using the Web3Auth SDK version 8.12.3 under the Growth Plan and are facing difficulties in accessing user data such as email addresses and public keys. This limitation is preventing us from managing NFT transactions effectively as we cannot identify wallet addresses and other user details. Could you provide guidance on how to resolve this issue to access the required information?
Hello fixtix.info@gmail.com,
Thanks for reaching out! I understand you are having issues retrieving user data such as email addresses and public keys using the Web3Auth SDK version 8.12.3. Let me gather some additional information to assist you better:
- Initialisation & Login Code Snippets: Can you please share the code snippets of how you are initializing Web3Auth and handling the login process?
- Browser Console Screenshots: If there are any error messages or logs in the browser console, please provide screenshots.
- Custom Authentication Details (if applicable): Are you using any custom authentication providers? If so, please provide details such as the verifier name and method of login.
- Your Auth Details (if applicable): If you are using your authentication method, please share:
- JWKS Endpoint
- Sample idToken (JWT)
These details will help us understand the problem better and provide you with a precise solution.
This response was generated by the Web3Auth Bot. A member of the Web3Auth team will review your query and provide a detailed response soon.
Hey @fixtix.info, welcome to the community!
Could you please share the relevant Web3Auth-related code snippet you’re using? Also, let us know what error you’re encountering when trying to retrieve the wallet address and user information like email addresses or public keys. This will help us better understand the issue and guide you accordingly.
Hello Maharshi,
Thank you for your continued support. Here are the details regarding our implementation and the issue we are encountering:
-
Web3Auth Initialization and Login Code Snippets:
We initialize Web3Auth and handle the login process as follows:Initialization:
javascript
const web3auth = new Web3Auth({
clientId,
uiConfig: {
appName: “Fixtix”,
mode: “dark”,
logoLight: logow,
logoDark: logow,
defaultLanguage: “en”,
loginGridCol: 3,
primaryButton: “externalLogin”,
loginMethodsOrder: [
“google”, “github”, “twitter”, “farcaster”, “discord”, “twitch”, “facebook”
],
},
web3AuthNetwork: WEB3AUTH_NETWORK.SAPPHIRE_MAINNET,
privateKeyProvider,
});const openloginAdapter = new OpenloginAdapter({
loginSettings: { mfaLevel: “none” },
adapterSettings: {
whiteLabel: {
appName: “Fixtix”,
logoLight: logow,
logoDark: logow,
defaultLanguage: “en”,
mode: “dark”,
},
…
},
});web3auth.configureAdapter(openloginAdapter);
const walletServicesPlugin = new WalletServicesPlugin({
wsEmbedOpts: {},
walletInitOptions: { whiteLabel: { showWidgetButton: true } },
});web3auth.addPlugin(walletServicesPlugin);
await web3auth.initModal();Login Process:
javascript
const login = async () => {
if (!web3auth) {
console.error(“Web3Auth not initialized”);
return;
}
try {
const web3authProvider = await web3auth.connect();
setProvider(web3authProvider);
setLoggedIn(true);
} catch (error) {
console.error(“Error during login:”, error);
}
}; -
Browser Console Error:
- Custom Authentication Details:
We are using custom authentication providers such as Google, GitHub, Facebook, etc. Here are some details for two of these:- Google:
- Verifier Name: aggregate-sapphire
- Type of Login: OAuth
- Client ID: 519228911939-cri01h55lsjbsia1k7ll6qpalrus75ps.apps.googleusercontent.com
- GitHub:
- Verifier Name: aggregate-sapphire
- Type of Login: OAuth
- Client ID: hiLqaop0amgzCC0AXo4w0rrG9abuJTdu
- Google:
We had earlier discussed enabling the NFT checkout functionality, which seems to be impacted by this error. Could you please help us resolve this issue so we can proceed with the NFT checkout as planned?
Thank you
Email address is part of the UserInfo
object that can be obtained using the code example provided here: UserInfo Example.
The Ethereum wallet address can be retrieved from this code snippet.
This topic was automatically closed 14 days after the last reply. New replies are no longer allowed.