John Howard e583eb5eba
authorization: add new Require mode (#1223)
`Deny` mode is a bad API with a useful goal: to ensure that policies
MUST match the rule, essentialy adding AND semantics on top of the ALLOW
policies OR semantics.

Deny is trick, because you often end up having double negatives.

For example `deny: !(port in [443, 8443])`. Or worse, somethign like
`deny: jwt.group != 'eng'`; if the jwt doesn't have a `group` this rule
will not deny.

Instead, this proposes adding a new Require mode which is like deny but
inverted.

The above rules would be `require: port in [443, 8443]` or `require:
jwt.group == 'eng'`.

These are useful for admin level rules that apply on top of user level
rules like `require: source.address not in [banned country cidr ranges]`
etc
2026-03-26 09:15:39 -07:00
..
2026-02-09 16:20:45 -08:00