Skip to content

docs(rbac): role-routing migration plan (closes #409)#415

Open
rubenvdlinde wants to merge 1 commit into
developmentfrom
feature/migrate-role-routing-to-or-rbac
Open

docs(rbac): role-routing migration plan (closes #409)#415
rubenvdlinde wants to merge 1 commit into
developmentfrom
feature/migrate-role-routing-to-or-rbac

Conversation

@rubenvdlinde
Copy link
Copy Markdown
Contributor

Adoption-only. No parallel permission code exists in procest; the violation flagged by consume-or-rbac-fleet-wide is the ABSENCE of OR-RBAC enforcement on routed steps. Per ADR-023 enforcement work is bound to the parafering approval migration. Closes #409.

…proval

Implements migrate-role-routing-to-or-rbac — adoption-only scope.

Investigation: no Role*Service, no RoleMutationListener, no per-app
permission tables in procest. Role assignment is from NC groups; frontend
maps roleType UUIDs to labels for display only — no server-side
enforcement layer exists.

The umbrella's violation is the ABSENCE of OR-RBAC enforcement on routed
steps, not parallel code. Follow-up work (ncGroupId on roleType + step
enforcement) is bound to the parafering approval migration sequence.

Closes #409
@rubenvdlinde rubenvdlinde requested a review from Rem-Dam as a code owner May 11, 2026 21:58
@github-actions
Copy link
Copy Markdown
Contributor

Quality Report — ConductionNL/procest @ 5c00abb

Check PHP Vue Security License Tests
lint
phpcs
phpmd
psalm
phpstan
phpmetrics
eslint
stylelint
composer ✅ 100/100
npm ✅ 419/419
PHPUnit ⏭️
Newman ⏭️
Playwright

Spec coverage: 5% (21 tests / 456 specs)


Quality workflow — 2026-05-11 22:11 UTC

Download the full PDF report from the workflow artifacts.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant