offline / test (push) Waiting to run

Details

Separate Zapier, web, API, and leaf access planes with NATS authz

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

1.5 KiB

Raw Blame History

`verae-access-authz/client`

Package: verae-access-authz
Source: packages/verae-access-authz/src/client.js
Lines: 39

What this module is

Implementation module in verae-access-authz. The tables below are extracted from the source (signatures + JSDoc).

Exports

authorizeThenRequest, authorizeThenPublish

Types / interfaces / classes

None extracted.

Functions

Name	Parameters	Param types (JSDoc)	Returns	Calls (same file / helpers)
`authorizeThenRequest`	`nc, sc, { plane, subject, principal, payload, timeout = 2000 }`	—	`unknown`	see Call graph
	Call verae.access.authz.check then the internal subject. Fail closed.
`authorizeThenPublish`	`nc, sc, { plane, subject, principal, payload, timeout = 2000 }`	—	`unknown`	see Call graph

What it imports / requires

./subjects.js

Call graph (identifiers invoked)

authorizeThenRequest, request, encode, stringify, parse, decode, authorizeThenPublish, publish

Each identifier is a call site in this file. Follow the import list to see the defining module; open that module’s MD for parameter and return types.

Return values (how to read this)

HTTP route handlers return Express res.json(...) bodies (see route docs).
Zapier perform functions return a single object (creates) or an array (triggers/searches).
Pricing functions return integer cents on Quote.totalCents.

1.5 KiB Raw Blame History Unescape Escape

verae-access-authz/client