marchon/master-zapier-plan-draft
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 1
28 commits 2 branches 0 tags 93 MiB
Commit graph

2 commits

Author SHA1 Message Date
George Lambert
345aeeead9 Bind each customer to a Verae userId for hop tracing
Some checks are pending
offline / test (push) Waiting to run
Details 
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.
 2026-09-11 16:18:06 -04:00
George Lambert
1b199ca4d4 Separate Zapier, web, API, and leaf access planes with NATS authz
Some checks are pending
offline / test (push) Waiting to run
Details 
Zapier is one ingress. Direct web, customer API, and S2S leaf nodes are their own services. Every hop to an internal subject must pass verae.access.authz.check (default deny by plane).
 2026-09-11 16:05:05 -04:00