Problem/Motivation
If we configure sentinel and the server goes down, validation is not possible: Verification failed. Try again later.
It would be good, if we fallback to Altcha widget in that case.
Steps to reproduce
Proposed resolution
Remaining tasks
User interface changes
API changes
Data model changes
Issue fork altcha-3562106
Show commands
Start within a Git clone of the project using the version control instructions.
Or, if you do not have SSH keys set up on git.drupalcode.org:
- 1.0.x
changes, plain diff MR !10
- 3562106-fallback-to-widget
compare
Comments
Comment #2
arno_vghEnabling a fallback to the Altcha widget when the Sentinel server is unavailable could introduce some (minor) security implications, as it may lower the protection level.
If implemented, it could be an opt-in configuration so site owners can consciously decide whether to use the fallback in that case or not.
Any other thoughts?
Comment #6
robindh commentedAlmost done - the fallback feature can be enabled on the ALTCHA configuration page (/admin/config/people/captcha/altcha).
When a sentinel error is detected, the widget challenge url is swapped to self-hosted. When the user clicks the checkbox again,
a new challenge is fetched from the self-hosted drupal instance, and the challenge solution will later be validated on form submit.
Moving to needs work since there is a test failure on drupal CI
Comment #7
robindh commentedFixed - test was incompatible with gitlab CI. Moving to review
Comment #9
robindh commentedMerged into the development branch - will create a new release soon-ish