New GET /beoordeling/{id} shows one aanvraag's status, linked documents, and a
canBesluiten decision flag, gated by the same CanBeoordelen capability as the
werkvoorraad list. Reads through IZaakSource.ListCases rather than a new seam
method (WP-66 needs one anyway for the real write); owner BSN is masked.

Fixes a real gap found while wiring this up: the behandelportal's login was still
WP-61's copied citizen/BSN DigiD flow, so nothing ever sent X-Medewerker and the
werkvoorraad screen (WP-64) always denied in a real browser. A dev-only
medewerkerInterceptor (mirrors the existing ?role= stand-in as ?rollen=) fixes that.

WP-65's own Risks note authorized splitting read from write across sessions given
its size; this is the read half. The decision-recording mutation is next (65b).

Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>

2026-08-03 09:01:09 +02:00

5.2 KiB

Raw Blame History

Roles & access (ABAC) — quick reference

A short, practical reference for which roles exist, how to switch between them, and what each unlocks. For the full design and rationale see PRD-0002 — Attribute-Based Access Control.

Login is faked. This POC has one hardcoded, stubbed DigiD user (a 9-digit BSN); there is no real identity provider and you do not pick a role when you log in.

The acting role is a separate, dev-only stand-in for the coarse role a real AD/OIDC identity would carry. It is orthogonal to the login user — you log in as the one faked user, then choose an acting role to exercise the drafter/approver/admin flows.

The three roles

drafter (default) · approver · admin — defined by the Role type in src/app/shared/domain/role.ts.

How to switch role (dev only)

Both are wired only under isDevMode() — they do not exist in a production build.

Dev switcher (easiest): open the ⚙ state panel (bottom-right in a dev build) and pick a role from the role dropdown. The page reloads with the new role.
?role= query param: append ?role=drafter, ?role=approver, or ?role=admin to any URL. The value is sticky for the browser tab (sessionStorage), so it survives navigation that drops the query param. An unknown value falls back to drafter; open a fresh tab or set ?role=drafter to reset.

Mechanism: src/app/shared/infrastructure/role.ts reads the role and the HTTP interceptor stamps it as an X-Role header on role-aware requests; the backend resolves it into a Principal.

Actor kinds (backend, WP-62)

X-Role/Principal above is a coarse role that applies to either of two actor kinds the backend now models (ADR-0002 §3): a zorgverlener (the SSP's citizen — has a BSN) or a medewerker (backoffice employee — no BSN, has Rollen). StubIdentityProvider picks the medewerker kind from a dev header, X-Medewerker (+ X-Rollen), mirroring X-Role/X-Subject above. The SSP's FE never sends either header — it has no medewerker screens. The behandelportal does: apps/behandelportal/src/app/auth/infrastructure/medewerker.interceptor.ts stamps every request as one fixed stand-in medewerker (dev-only, same isDevMode() gate as roleInterceptor), since this app has no real employee-SSO login yet (ADR-0002 §3 — the two apps' login flows are expected to diverge, and this stand-in is that flow's placeholder). ?rollen= (sticky per tab, mirroring ?role=) picks the medewerker's rollen — ?rollen=geen exercises the deny path; the default is behandelaar. Authz.CanBeoordelen(caller) is the first medewerker capability — a rol-based decision flag (MedewerkerRol.Behandelaar), surfaced on GET /me as aanvraag:beoordelen (appended alongside RoleCapabilities's role-derived set, since that switch is keyed on Principal and can't see the actor kind) — gates the behandelportal's /dashboard werkvoorraad queue (WP-64) and its /aanvraag/:id beoordeling detail (WP-65).

What each role unlocks

Capabilities are resolved server-side (backend/src/BigRegister.Api/Domain/Authorization/Authz.cs, RoleCapabilities) and returned by GET /me.

Role	Capabilities (`/me`)	Reaches
`drafter`	(none of the admin capabilities)	Composes letters; the only role that may reveal a BSN
`approver`	`brief:approve`, `brief:reject`, `brief:send`	Reviews/approves letters (four-eyes: approver ≠ drafter)
`admin`	`orgtemplate:edit`, `stamdata:edit`, `cases:manage`	Huisstijl `/brief/huisstijl`, Stamdata `/beheer/stamdata`, Aanvragen `/beheer/zaken`

The admin pages appear in the header nav and in the dashboard "Beheer" section whenever the matching capability is present — otherwise they are reachable only by URL (and the route guard redirects a user who lacks the capability back to /dashboard).

The one principle

Identity (AD/OIDC, faked here) supplies coarse roles; the app owns a fine-grained capability model on top. The same Authz check both emits a capability (on GET /me, consumed by AccessStore in src/app/shared/application/access.store.ts) and enforces the endpoint — one source of truth, so the two can't drift. The UI only renders decisions; it never derives access from a role. Anything tied to a specific resource's live state (e.g. may-I-edit this letter, reveal this BSN) rides that screen's decision DTO rather than /me.

5.2 KiB Raw Blame History