The application was configured to fail closed and verify Cloudflare Access identity assertions before serving patient routes. The JWT contract was tested locally, but the hostname, policy, audience, and origin restrictions still required account-side setup.
- What worked
- Signed identity assertions provided a suitable way to add staff authentication without building a user-management system into the application.
- What got in the way
- End-to-end authentication could not be verified because no Cloudflare account, domain, Access application, or production assertion was available.