ADR-0010: BSN resolution inside the PEP¶
- Status: superseded by ADR-0011, which ADR-0033 supersedes in turn
- Date: 2026-08-24 (ported from reference architecture v0.6.2)
- Satisfies: P-04
- Deliberation: Reference architecture v0.6.2, decision 4 (archived and unpublished)
- Implemented in: superseded before implementation
Context and problem statement¶
After the PDP allows a pseudonymous DvTP request, a component must resolve the pseudonym to the BSN. The API of the source requires the BSN.
Decision (superseded)¶
The PEP intercepts the query of the consumer. After the policy decision,
the PEP resolves consent_id → PI → BSNk Transform → BSN. Then it puts the
BSN into the internal query of the bronhouder.
Why it was superseded¶
With this decision, the PEP becomes a middlebox that transforms data. Also, a component with BSN authorization sits in shared infrastructure.
In the implemented design, the PEP (the FSC Inway) only enforces decisions. The source owns the identifier resolution. For this design, see ADR-0011.