# טיוטה: בדיקת זהות ובידוד קריאה ב־Frankfurt

> טיוטת PR #57 — בדיקת QA מוצעת. מקור: docs/platform/frankfurt-identity-qa.md · 3b5d184.

This opt-in script makes **GET requests only** to the Frankfurt Supabase REST API. It checks two distinct Clerk JWTs, each user's read of their own dedicated synthetic tenant, both cross-tenant reads, and anonymous reads. It requires the exact protected QA origin and exact Frankfurt database origin, rejecting Singapore, the production app origin, aliases, paths and ports. It does not contact the QA web deployment; the QA origin is a configuration guard, not proof that a deployment uses Frankfurt. Supabase verifies the JWT signature: the local payload checks do not.

Do not run this against customer identities or customer tenants. `syntheticTestIdentities` is an operator attestation, not a technical proof. Provision and clean up two dedicated test identities and tenants separately in an isolated environment with a documented cleanup plan. This script never creates, updates or deletes users or records. It does not test write denials, role variations, storage, application routes, Vercel configuration or service-role paths. A passing result is not production approval.

To run later, create a private JSON file outside the repository, owned by the operator and with mode `0600`. It must contain the exact `qaUrl` and `supabaseUrl` literals in the script, `syntheticTestIdentities: true`, the Frankfurt `publishableKey`, and a `users` array of exactly two objects with their synthetic `tenantId` and short-lived Clerk `jwt`. Never use a service-role or secret key. Do not commit, print or share the file, JWTs or output containing credentials; delete the private file after use. Opt in with `LNE_QA_READ_ONLY=1` and point `LNE_QA_CONFIG` to the private file, then run `node scripts/check-frankfurt-identity.mjs`. This script does not obtain JWTs; sign in to each prepared account through an approved secure process first. JWT expiration may require fresh sessions.

Run guard-only checks without cloud access using `node --test scripts/check-frankfurt-identity.test.mjs`. The test JWTs are synthetic, unsigned placeholders used only to exercise input validation; they do not prove authentication.
