Skip to content
Corex

ChallengeSettings

Corex\Security\ChallengeSettings · class · Core layer

The site-wide captcha settings a token is judged against, read from stored configuration and never from the request: the provider in use, the score a reCAPTCHA v3 token must reach, and the hostnames a token may come from (by default this site’s own). Shared by every CoreX form that checks a token, so a form drawn by the forms plugin and one drawn by an add-on are judged alike (spec 071, spec 115).

A provider is chosen and its secret entered: a form needs the provider’s check.

The provider whose widget a protected form shows, or ” when the provider shows none.

The key the provider’s widget is drawn with. It is public by design; the secret is not.

Constrain a score threshold to the provider-supported range.