marchon/master-zapier-plan-draft
1
0
Fork 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions 1
master-zapier-plan-draft/docs/sphinx/modules/verae-access-authz
History
George Lambert 345aeeead9
Some checks are pending
offline / test (push) Waiting to run
Details
Bind each customer to a Verae userId for hop tracing 
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
..
client.md Separate Zapier, web, API, and leaf access planes with NATS authz 2026-09-11 16:05:05 -04:00
client.rst Separate Zapier, web, API, and leaf access planes with NATS authz 2026-09-11 16:05:05 -04:00
policy.md Bind each customer to a Verae userId for hop tracing 2026-09-11 16:18:06 -04:00
policy.rst Separate Zapier, web, API, and leaf access planes with NATS authz 2026-09-11 16:05:05 -04:00
server.md Separate Zapier, web, API, and leaf access planes with NATS authz 2026-09-11 16:05:05 -04:00
server.rst Separate Zapier, web, API, and leaf access planes with NATS authz 2026-09-11 16:05:05 -04:00
subjects.md Separate Zapier, web, API, and leaf access planes with NATS authz 2026-09-11 16:05:05 -04:00
subjects.rst Separate Zapier, web, API, and leaf access planes with NATS authz 2026-09-11 16:05:05 -04:00