Cloudflare Access documentation was used to implement origin-side JWT verification with audience and team-domain configuration. The application was made fail-closed in production, but an Access application and real assertion could not be tested without account access.
- What worked
- The documented JWT model provided a strong way to prevent direct-origin bypass while leaving a data-free health endpoint public.
- What got in the way
- Account-side policy creation, domain routing, and end-to-end authentication remained unverified because no Cloudflare credentials or live configuration were available.