When you need this
You need this when your site is protected by a Cloudflare Access application and you see one of:- A Cloudflare Access login screen instead of your app.
- HTTP
401,403, or a Cloudflare-branded block page on the deployment host. - Tests pass locally with your own browser session but fail in TesterArmy at the very first navigation.
- HTTP Basic Auth - use HTTP Basic Auth.
- App-level login (your own login form) - use Test Credentials.
Pick a bypass method
Cloudflare supports two ways to let an automated client through Access. Either works with TesterArmy.Option A - Service tokens (recommended)
A service token is a Client ID + Client Secret pair generated in the Cloudflare dashboard. Your Access policy must include a Service Auth rule that allows this token.- In Cloudflare: Zero Trust → Access → Service Auth → Service Tokens → Create Service Token. Set a name and a duration.
- Copy the Client ID and Client Secret. The secret is shown only once.
- Open the Access application that protects your site: Access → Applications → <your app> → Policies → Add policy.
- Set Action: Service Auth and add an Include rule of type Service Token matching the token you just created. Save.
Option B - Bypass policy with a custom header
Use this if you cannot create a service token (for example, you only manage one Access application and prefer a single shared secret).- In Cloudflare: open the Access application → Policies → Add policy.
- Set Action: Bypass.
- Add an Include rule of type HTTP header with a header name and value of your choice - e.g.
X-Tester-Army-Bypassequals a long random secret. Save.
Save the headers in TesterArmy
- Go to Project Settings → Integrations → Site Protection.
- Click Set up on the Cloudflare Zero Trust card.
- Enter the header pair(s):
- Service tokens: fill
CF-Access-Client-IdandCF-Access-Client-Secretin the two default rows. - Bypass policy: leave the default service-token rows blank and add your header name and value as a custom header.
- Service tokens: fill
- Click Save headers.