Before this change the self-service confirmation and the openbaar register showed different identifiers, so a citizen could not look their registration back up (#78). Now both surface the same reference:
domain → ACL (write): the domain registrationId is set as the zaak's identificatie on POST /zaken.
event-subscriber → ACL (read): the subscriber reads the zaak's identificatie back through the ACL (§8.1 — only the ACL talks to ZGW) via a new POST /zaken/reference, and stores it on the projection row and the processed_notifications replay log.
BFF + openbaar: the public view exposes id/status/reference (never bsn/naam) and searches by id or reference; the register's "Referentie" column shows the reference.
Storing the reference in the replay log keeps ADR-0008's rebuild-is-log-only invariant intact — /admin/rebuild reproduces the reference without re-reading the ACL.
## What & why
Before this change the self-service confirmation and the openbaar register showed **different** identifiers, so a citizen could not look their registration back up (#78). Now both surface the same **reference**:
- **domain → ACL (write):** the domain `registrationId` is set as the zaak's `identificatie` on `POST /zaken`.
- **event-subscriber → ACL (read):** the subscriber reads the zaak's `identificatie` back through the ACL (§8.1 — only the ACL talks to ZGW) via a new `POST /zaken/reference`, and stores it on the projection row **and** the `processed_notifications` replay log.
- **BFF + openbaar:** the public view exposes `id/status/reference` (never bsn/naam) and searches by id or reference; the register's "Referentie" column shows the reference.
Storing the reference in the replay log keeps ADR-0008's **rebuild-is-log-only** invariant intact — `/admin/rebuild` reproduces the reference without re-reading the ACL.
Decision recorded in **ADR-0012**.
## Definition of Done
- [x] Linked issue: #78
- [x] Tests written first; red → green per layer
- [x] Unit + acceptance green (`make unit`): domain 49, acl 27, bff 20, event-subscriber 19, acceptance 7
- [x] Frontend lint + test green (`nx run-many -t lint test`)
- [x] Mutation ≥ break(90): acl 100%, event-subscriber 100%, bff 100%, domain 98.41% (pre-existing FlowableWorkflowClient baseline, untouched)
- [x] e2e extended: confirmation reference == register reference
- [x] openapi.json + api-client regenerated (drift guard green)
- [x] ADR-0012 added; demo-script note appended
- [x] `Acl__BaseUrl` wired for the subscriber in compose
closes #78
The ACL now writes the domain registrationId as the zaak's identificatie on
POST /zaken, and exposes GET-through POST /zaken/reference to read a zaak's
identificatie back. Only the ACL touches ZGW (§8.1); the reference is the single
value shown on both the self-service confirmation and the openbaar register.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
OpenZaakWorker forwards registration.Id to IAclClient.OpenZaakAsync so the zaak's
identificatie equals the reference the citizen sees on the submit confirmation.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
On each notification the subscriber reads the zaak's reference (identificatie)
through the ACL — the only code allowed to talk to ZGW (§8.1) — and persists it on
the register_projection row and in the processed_notifications replay log. Storing
it in the log keeps rebuild log-only (ADR-0008): no ACL/ZGW access on rebuild.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
The BFF's public view exposes id/status/reference (never bsn/naam) and searches by
id or reference; the openbaar register's Referentie column and search now show the
reference the citizen saw on submit. api-client + openapi.json regenerated.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
Records the domain->ACL (write) and event-subscriber->ACL (read) boundary for the
single citizen reference, wires Acl__BaseUrl into the subscriber in compose, extends
the e2e happy path to assert confirmation reference == register reference, and adds
the demo note.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
The verify stack is shared: earlier verify-projection/verify-domain checks leave
INGEDIEND rows in the register before the e2e submits. A status-only poll
short-circuited on a stale row, then the reference assertion ran against a
not-yet-reloaded page and timed out. Poll (with reload) on this submission's
reference cell instead — stronger, and it directly proves the #78 correlation.
Scope the INGEDIEND/INGESCHREVEN status checks to that reference row too.
Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
not
merged commit 9997da8beb into main2026-07-14 14:01:51 +00:00
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
What & why
Before this change the self-service confirmation and the openbaar register showed different identifiers, so a citizen could not look their registration back up (#78). Now both surface the same reference:
registrationIdis set as the zaak'sidentificatieonPOST /zaken.identificatieback through the ACL (§8.1 — only the ACL talks to ZGW) via a newPOST /zaken/reference, and stores it on the projection row and theprocessed_notificationsreplay log.id/status/reference(never bsn/naam) and searches by id or reference; the register's "Referentie" column shows the reference.Storing the reference in the replay log keeps ADR-0008's rebuild-is-log-only invariant intact —
/admin/rebuildreproduces the reference without re-reading the ACL.Decision recorded in ADR-0012.
Definition of Done
make unit): domain 49, acl 27, bff 20, event-subscriber 19, acceptance 7nx run-many -t lint test)Acl__BaseUrlwired for the subscriber in composecloses #78