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

Command icon 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:

Comments

anruether created an issue. See original summary.

arno_vgh’s picture

Enabling 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?

robindh made their first commit to this issue’s fork.

robindh changed the visibility of the branch 3562106-fallback-to-widget to hidden.

robindh’s picture

Status: Active » Needs work

Almost 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

robindh’s picture

Status: Needs work » Needs review

Fixed - test was incompatible with gitlab CI. Moving to review

  • robindh committed 1eec6695 on 1.0.x
    feat: #3562106 Fallback to widget if sentinel server is not available...
robindh’s picture

Status: Needs review » Fixed

Merged into the development branch - will create a new release soon-ish

Now that this issue is closed, review the contribution record.

As a contributor, attribute any organization that helped you, or if you volunteered your own time.

Maintainers, credit people who helped resolve this issue.

Status: Fixed » Closed (fixed)

Automatically closed - issue fixed for 2 weeks with no activity.