Repository navigation
[Turnstile] Add interactive challenge sitekey to testing scenarios - #34179
Open
neelakolkar-cf wants to merge 1 commit into
Open
neelakolkar-cf wants to merge 1 commit into
neelakolkar-cf wants to merge 1 commit into
Conversation
neelakolkar-cf
requested review from
a team,
marinaelmore and
migueldemoura
as code owners
October 10, 2026 16:46
Contributor
AI Review✅ Reviewed Commands
|
Contributor
Review coverage🟡 1 ownership area needs approval. Suggested reviewers: @marinaelmore
CODEOWNERS mappings for displayed areas (1)
|
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
1 participant
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.
Summary
Closes #31088.
The Testing scenarios table on the Turnstile testing page covered the always-pass, always-fail, and
timeout-or-duplicatecases, but did not include the3x00000000000000000000FFsitekey that forces an interactive challenge. That sitekey is already listed in the Test sitekeys table on the same page.This PR adds a row pairing it with the always-pass test secret key:
3x00000000000000000000FF1x0000000000000000000000000000000AAThe existing third row (
1x00000000000000000000AAwith the3x0000000000000000000000000000000AAsecret key) is correct. That secret key returns the "token already spent" (timeout-or-duplicate) error, as listed in the Test secret keys table, so it is left unchanged.This reopens #31605, which made the same change but was closed as stale without being merged.
Documentation checklist