[Auth] Decide: opaque constraints vs IConstraintPolicy; shared JWT/refresh helper #20
Reference in New Issue
Block a user
Delete Branch "%!s()"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Two open design decisions in the Auth component: (1) whether authorization constraints stay an opaque object? or get a small IConstraintPolicy (shared-contract Q3); (2) whether to ship a shared JWT/refresh helper (GAP #7). Neither has a second consumer asking yet — decide (or explicitly park) when one appears. (A3, the shared dev base DN, is done: dc=zb,dc=local.)
Source: components/auth/GAPS.md, Decisions still open.