Bind each customer to a Verae userId for hop tracing
Some checks are pending
offline / test (push) Waiting to run

Signup registers/binds a Verae central user and stores veraeUserId. Public access stays the zappier API key. Chain JWTs stay server-side behind tokenRef. Authz, billing, and jobs.watch carry veraeUserId.
This commit is contained in:
George Lambert 2026-09-11 16:18:06 -04:00
parent 1b199ca4d4
commit 345aeeead9
79 changed files with 703 additions and 95 deletions

View file

@ -44,6 +44,8 @@ describe('tenancy', () => {
const body = await res.json();
assert.equal(body.tenant.plan, 'free');
assert.ok(body.apiKey.startsWith('zmw_'));
assert.match(body.tenant.veraeUserId, /^vu_[0-9a-f]{16}$/);
assert.doesNotMatch(JSON.stringify(body), /mock-jwt|eyJhbGci/);
});
it('enterprise without contract rejected', async () => {