Skip to content

Clarify usage of testing sitekeys and secret keys #13785

Description

@g-stone7

Existing documentation URL(s)

What changes are you suggesting?

It is not clear how exactly the testing sitekeys and secret keys should be used.

In my case I want to let the captcha always pass both on client and server side to implement a e2e test using playwright for a happy path.

For example, is it enough to just use the sitekey "1x00000000000000000000AA" on client side but the server-side verification still uses the actual secret key? Or do I need to reconfigure the server to use the secret key "1x0000000000000000000000000000000AA" aswell? If I use a "Always passes" secret key on server side, do I I even need to use a "Always passes" site key?

It would be nice if these kind of questions are clarified in the documentation. Currently it is a lot of trial-and-error to find the right sitekey/secret key combination.

Thanks!

Additional information

https://developers.cloudflare.com/turnstile/reference/testing/

Metadata

Metadata

Type

No type

Projects

No projects

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions