This plugin adds support for Google One Tap sign-in and sign-up to Discourse. When this plugin is installed and configured, anonymous users will see a prompt that looks like this:
From that prompt, they can use any Google account theyâre currently logged-in to signup or login (if they already have an account on your site with the same email address) to your Discourse instance.
Configuration
Make sure the google_one_tap_enabled setting is enabled
Thanks for the great plugin, however there seems to bug, where the plugin creates an invisible div, making it impossible to interact with any element below it.
It also creates extra space on the left side of the page on mobile.
Mobile:
Hello Yeah, this plugin definitely need some I tested it yesterday and experienced the same. It seems the google iframe on login/signup modal also has issues. It seems the alignment and styling isnât the same as other social buttons and if I open the login modal than switch it to signup the google button isnât render.
There could be a lot of reasons for this; one for example is the âexponential cool downâ Google added:
There may potentially be some way we can detect that this was not loaded correctly â but at least in chrome the element with âSign in to localhost with google.comâ is not even an element on the page. Maybe we can use this?
Thanks for a great plugin, itâs exactly what I was looking for.
But is the plugin also compatible with the latest changes âChrome third-party cookie deprecation starts Q1 2024â. Hereâs more information on the FedCM required and its migration.
The functionality is very similar, could it be combined with the native Google login that Discourse already has, so that the login screen doesnât have two âLogin with Googleâ boxes?
I believe the main difference between this and the native google auth support is this triggers when someone hits a page rather than a user finding their way to the login/signup prompt.
Yes agreed, or make it an option in core. This is a pretty well recognized way to increase registrations and lower onboarding friction - users are familiar with this experience.
That solution has (or had) some issues that made login actually more difficult, and it looked messy on mobiles. Sorry, that is really useless answer, because I canât remember any more what were those issues why I disabled it â even when majority is using Gmail here on Finland.