Friendly captcha - #6546
Open
ukutaht wants to merge 12 commits into
Open
Conversation
Switch the registration and password-reset bot protection from hCaptcha to Friendly Captcha v2 for its privacy-first, adaptive (Smart mode) challenge model that lets legitimate users pass without interaction. - Verify solutions server-side against the global siteverify endpoint using X-API-Key header auth and a JSON body. - Configure via FRIENDLY_CAPTCHA_SITEKEY and FRIENDLY_CAPTCHA_API_KEY. - Gate the form submit button until the widget completes (re-disabling on error/expire), as recommended by Friendly Captcha.
Drop the per-form attribution slot and render a single shared attribution inside the widget component, simplifying both call sites.
|
ukutaht
marked this pull request as ready for review
July 28, 2026 09:36
cnkk
reviewed
Jul 28, 2026
cnkk
reviewed
Aug 3, 2026
RobertJoonas
reviewed
Aug 4, 2026
Comment on lines
246
to
+247
| if not PlausibleWeb.Captcha.enabled?() or | ||
| PlausibleWeb.Captcha.verify(params["h-captcha-response"]) do | ||
| PlausibleWeb.Captcha.verify(params["frc-captcha-response"]) do |
Contributor
There was a problem hiding this comment.
Nitpick: We could omit the not PlausibleWeb.Captcha.enabled?() check here (as password reset does). verify returns true if not enabled anyway.
Same goes for line 262 in this file (non-invitation register event handler).
Comment on lines
+144
to
+153
| <.button | ||
| id="register" | ||
| type="submit" | ||
| class="w-full" | ||
| mt?={false} | ||
| x-data={"{ captchaReady: #{not PlausibleWeb.Captcha.enabled?()} }"} | ||
| x-on:frc-captcha-ready.window="captchaReady = true" | ||
| x-on:frc-captcha-reset.window="captchaReady = false" | ||
| x-bind:disabled={"!captchaReady || #{@disable_submit}"} | ||
| > |
Contributor
There was a problem hiding this comment.
Currently, a failed submit (for whatever reason, e.g. email already exists) will use up the one-time token and the next submit is guaranteed to fail with a "Please complete the captcha" error. Only a page refresh will fix that, meaning that the user needs to fill out all the fields again.
In LiveViews, when a form submit failure comes back from the server, we should make sure to reset the captcha automatically.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
4 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Changes
Replaces hCaptcha with invisible Friendly Captcha. Due to the 'invisible' part, some frontend complexity is necessarily added.
NB⚠️ Do not merge. Requires Friendly Captcha credentials to be set up on prod before deploying.
Tests
This part is manually tested.
Changelog
Documentation
Dark mode