zeekay 8cab81b83d A standalone edge acts in the subject's org, never the application's ...

EdgeAuth set X-Org-Id, and pinned the billing subject, from the `owner`
claim: the org of the application a person signed in through. Every
self-serve user of the brand app therefore acted in and billed to the
brand's org at a standalone commerce (COMMERCE_EDGE_AUTH=true).

tenancy now resolves a verified token as cloud's SanitizeIdentity does:
the home org is orgs[0], the acting org is the client's selection
(X-Org-Id, or ?org on a billing path) when the signed set admits it,
else the default (authz.Claims.EffectiveOrg). A program is its
application's org and selects nothing; a person's token without a
membership set acts in no org. The billing subject follows the acting
org, and X-User-IsOrgAdmin is asked of it.

orgAdminHomeMatches compared home and acting org with EqualFold; it
compares them verbatim.

2026-10-20 07:49:25 -07:00

..

authz_test.go

Hanzo Commerce

2026-09-23 21:52:16 -07:00

claims_test.go

SuperAdmin is the identity edge's verdict, and commerce compares no org

2026-10-18 22:08:47 -07:00

iammiddleware.go

A standalone edge acts in the subject's org, never the application's

2026-10-20 07:49:25 -07:00

live_test.go

Hanzo Commerce

2026-09-23 21:52:16 -07:00

orgadmin_test.go

A standalone edge acts in the subject's org, never the application's

2026-10-20 07:49:25 -07:00

sudo_test.go

SuperAdmin is the identity edge's verdict, and commerce compares no org

2026-10-18 22:08:47 -07:00