I’m having trouble styling the Google authentication consent screen. When users attempt to log in, they see “connect to web3auth.io,” which causes confusion since it doesn’t match our app’s domain. As a result, many users are hesitant to proceed because they don’t recognize the domain.
Additionally, I’ve already configured the Terms of Service (ToS), Privacy Policy, and our logo in the Google Auth Console for this client. However, none of this information appears on the consent screen.
Does anyone know how to properly configure the consent screen to address these issues? Any help would be appreciated!
Thanks for reaching out! It sounds like you’re experiencing some difficulties with the Google authentication consent screen through Web3Auth. It can be tricky to get everything aligned with your branding.
Here’s a summary of the details you’ve provided for the support team:
SDK Details: Plug n Play
Issue: Customizing Google Auth Consent Screen
Details: Users see “connect to web3auth.io” which leads to confusion and lower trust as it doesn’t match your app’s domain. You’ve configured the Terms of Service, Privacy Policy, and logo in the Google Auth Console, but they are not reflecting on the consent screen.
You’ve also shared some images, which we’ll review to gain further insight into your issue.
Proposed Solutions:
Verify Google Auth Settings: Ensure that all settings, including your domain and branding assets, are correctly set up in the Google Cloud Console.
Check API Configuration: Confirm that you are using the correct OAuth 2.0 client ID for your app as it should be linked to the domain you want to show.
It seems like getting these settings right in the Google developer console is crucial here. If the issue persists after checking these, please consider reaching out directly in forums specific to Google authentication for more tailored help.
Feel free to ask if you need more assistance, and good luck with your integration!
Note: This response was generated by an AI bot and may require further verification. The Web3Auth support team has tracked this issue and will be responding as soon as possible.
