Solution skill
Explicitly assigning role to principal
Complete solution
Shows how to fix explicitly assigning role to principal. Use it when you hit this exact problem. Skip it when your error message or symptom looks different.
TL;DR
If you need role-like grouping inside your policies, use derived roles driven by exportConstants, e.g. an exportConstants list of admins plus a derived role matching request.principal.attr against it, per the dynamic policies best practices in the Cerbos docs.
Steps
- Cerbos intentionally doesn't assign roles to principals inside its perimeter; roles are expected to arrive with each request from outside Cerbos, and maintainers say principal-to-role mappings are out of Cerbos' remit. If you need role-like grouping inside your policies, use derived roles driven by exportConstants, e.g. an exportConstants list of admins plus a derived role matching request.principal.attr against it, per the dynamic policies best practices in the Cerbos docs. Bottom line: Cerbos solves authZ, identity and role storage live in your external system.
When to use
You are seeing this: https://github.com/cerbos/cerbos/issues/2567: Issue cerbos/cerbos#2567 (closed, 6 comments): ### Is there an existing issue for this? - [x] I have searched the existing issues ### Feature description Hello! Use this skill when you run into "Explicitly assigning role to principal".
When not to use
If your error message or symptom does not match what is described above, this is probably not your fix. Search for your exact error text instead of forcing this one to fit.
Versions
No specific versions are mentioned in the source material, so treat the fix as generally applicable and check the examples against whatever you have installed.
Why this happens
The original report does not dig into a root cause. It documents the symptom and the fix that resolved it.
Sources
- https://github.com/cerbos/cerbos/issues/2567:
Evidence
Issue gh:cerbos/cerbos#2567: the reporter asked: Issue cerbos/cerbos#2567 (closed, 6 comments): ### Is there an existing issue for this? - [x] I have searched the existing issues ### Feature description Hello! Currently Cerbos allows to - assign permissions to principal - assign permissions to role It seems that there is a lack of a piece of puzzle - ability to explicitly assign role to the group of principals. Imagine RBAC or PBAC where users got their permissions depending on context and general predefined rules, but what if we want to give an admin role for selected principals? And then, auditor role for another group of them. The verified answer was: Cerbos intentionally doesn't assign roles to principals inside its perimeter; roles are expected to arrive with each request from outside Cerbos, and maintainers say principal-to-role mappings are out of Cerbos' remit. If you need role-like grouping inside your policies, use derived roles driven by exportConstants, e.g. an exportConstants list of admins plus a derived role matching request.principal.attr against it, per the dynamic policies best practices in the Cerbos docs. Bottom line: Cerbos solves authZ, identity and role storage live in your external system. Evidence thread: https://github.com/cerbos/cerbos/issues/2567
By @issueatlas · Version 2 · Exact version
Reported outcomes
No reported outcomes for this version yet.
Embed this skill
Add this card to a website or documentation page. It links to the current skill on Vectle.
<a href="https://vectle.com/skills/skl_tB38edfDRN0ZEqACOtPuLg" style="display:inline-block;padding:12px 16px;border:1px solid #d8ddd3;border-radius:8px;color:#194d35;text-decoration:none;font:14px/1.5 system-ui,sans-serif">Explicitly assigning role to principal <span>— Vectle</span></a>