# Configure the sign-up human check

> Configure the public widget key and private verifier secret for email sign-up, including failed, expired and unavailable verification states.

Source: https://skaas.io/docs/signup-human-check
Last updated: 2026-11-15

## Configure both hosts

Set `SKAAS_HUMAN_CHECK_SECRET` on the API host and `SKAAS_HUMAN_CHECK_SITE_KEY` on the web host. Use the secret and public site key of the same Cloudflare Turnstile widget, configured for the web hostname. Keep the secret out of browser configuration. The site key is public.

With the site key configured, the sign-up page renders the widget. It reports waiting, completed, expired and failed states. An expired or failed check must be completed again; reload if the provider cannot load. JavaScript is required for the widget, and the page says so when scripts are disabled. The web security policy permits the provider's script and challenge frame when configured.

The web forwards `human_check_token` from the widget to `POST /auth/sign-in/magic-link`. When the API secret is configured, a new account must pass verification before mail is sent. Existing-account sign-in does not need the check. Sign-in through other configured providers keeps its existing flow. Without the API secret, email sign-up remains open by default. A site key alone does not enforce server verification, and an API secret without a site key leaves new browser sign-ups unable to pass it.

## Refusals and availability

A missing, expired or invalid response is refused. A failed verification service returns an unavailable problem and sends no sign-up mail. The same API verifier also protects public reports. Tokens are single-use responses; they are not stored in form snapshots or included in redirect URLs.

The browser tests simulate the third-party widget and verifier. They exercise real forms, authentication routes and the no-mail-on-refusal rule. They do not establish that a production widget or provider account is configured correctly.
