alknet/tasks/architecture/adr-031-forwarding-policy.md at 5c820a41e90fb5a6b9038644d428d4145284f27a

Files

glm-5.1 5c820a41e9 tasks: decompose Phase 0a ADR foundation and mark prior tasks completed

Add 10 new tasks under tasks/architecture/ for Phase 0a (ADR writing):
- 9 ADR tasks (026-034) with dependency-ordered structure
- 1 review checkpoint task before Phase 0b spec writing

ADR dependency graph (3 generations):
  Gen 1 (parallel): 026, 029, 030, 031, 032, 034
  Gen 2 (depends on 029): 027, 028
  Gen 3 (depends on 027+028): 033
  Gen 4: review checkpoint

Also mark all 34 prior implementation tasks as completed — they
were finished but still showing as pending in the taskgraph.

2026-06-07 08:55:33 +00:00

2.3 KiB

Raw Blame History

id, name, status, depends_on, scope, risk, impact, level

name

status

depends_on

scope

risk

impact

level

architecture/adr-031-forwarding-policy

Write ADR-031 — Forwarding policy

pending

narrow

low

phase

implementation

Description

Write ADR-031 establishing the forwarding policy model for channel_open_direct_tcpip access control.

Currently any authenticated client can open a channel to any destination. This ADR defines ForwardingPolicy, ForwardingRule, and TargetPattern as part of DynamicConfig (reloadable without restart).

Key design decisions from the research:

Default-allow for migration compatibility (preserves current behavior)
Default-deny is recommended for production
Rules are evaluated per-channel-open, matched against the authenticated Identity from IdentityProvider
TransportKind match in rules enables transport-specific restrictions (e.g., WebTransport clients restricted to alknet-* channels)
OQ-12 resolved: start with global rules + principal matching from Identity.scopes; per-user scope from peer_credentials.metadata.scopes via IdentityProvider
OQ-16 resolved: add TransportKind match in ForwardingRule; WebTransport clients can be scoped
OQ-18 resolved: IdentityProvider owns scopes, ForwardingPolicy consumes them

Acceptance Criteria

docs/architecture/decisions/031-forwarding-policy.md exists
ADR follows established format
Context explains the security gap: any authenticated client gets unrestricted access
Decision states: ForwardingPolicy with allow/deny rules, TargetPattern matching, default-allow for migration, TransportKind-aware rules, ForwardingPolicy is part of DynamicConfig (reloadable), Identity.scopes consumed by policy
Includes ForwardingRule and TargetPattern type signatures
Consequences: operators can restrict access per identity, per destination, per transport; default-allow preserves backward compatibility
Resolves OQ-12, OQ-16, OQ-18 (reference in ADR)
References: research/configuration.md, auth.md, open-questions.md

References

docs/research/configuration.md — ForwardingPolicy section
docs/architecture/auth.md — Identity.scopes and IdentityProvider
docs/architecture/open-questions.md — OQ-12, OQ-16, OQ-18
docs/research/integration-plan.md — ADR 031 entry, Phase 1.3

Notes

To be filled by implementation agent

Summary

To be filled on completion

2.3 KiB Raw Blame History