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

@ -68,6 +68,7 @@ Markdown indexes: https://zapier.georgelambert.org/index-md.html
modules/zappier/statement
modules/zappier/upstream
modules/zappier/usage
modules/zappier/verae-bind
modules/verae-zapier-middleware/app
modules/verae-zapier-middleware/clients/veraeClient
modules/verae-zapier-middleware/config
@ -79,6 +80,7 @@ Markdown indexes: https://zapier.georgelambert.org/index-md.html
modules/verae-zapier-middleware/debug/trace
modules/verae-zapier-middleware/errors
modules/verae-zapier-middleware/index
modules/verae-zapier-middleware/lib/identity
modules/verae-zapier-middleware/lib/receiptPdf
modules/verae-zapier-middleware/lib/tokens
modules/verae-zapier-middleware/middleware/authenticate
@ -107,6 +109,7 @@ Markdown indexes: https://zapier.georgelambert.org/index-md.html
modules/verae-zapier-middleware/store/db
modules/verae-zapier-middleware/store/jobWatchers
modules/verae-zapier-middleware/store/tenants
modules/verae-zapier-middleware/store/tokenRefs
modules/verae-zapier-middleware/store/usage
modules/verae-zapier-middleware/store/webhooks
modules/verae-zapier-middleware/workers/inProcessJobPoller