Short for Role Based Access Control, a type of authorization.
RBAC is a type of authorization of resources to user based on role of the user. Each role might have various attributes associated with them which allow or deny a certain resource on which they want to perform some action.
Resource is defined as the entity viz. a component (e.g. action.download or dashboard.project.list), a page (e.g. dashboard or user_management), etc. that the user want access to.
Action is defined as the type of operation (viz. VIEW, GET, UPDATE, DELETE) that the user want to perform on the given resource.
The permission rule is either allow or deny type.
Resource Type is optional meaning the type of resource (viz. component, page, api, data, etc.) that the user want to access.
If provided, it will be considered while evaluating the permission rule.
You build a nice looking website with authentication for a user and role associated with the user. Now you want the user to be authorized to access various resources across the application. You no longer need to worry any longer trying out various conditional statements with user’s roles and resources they can and cannot access.
With ImpelsysInc/react-rbac, you get more granular control of the resources with easy to use API. After the auth flow,
send a JSON with the response in the format permission.schema.json to the frontend client code.
[
{
"resource": "cart",
"action": "update.all"
},
{
"type": "deny",
"resource": "adminPanel",
"action": [
"get.all",
"update"
]
},
{
"resourceType": "component",
"resource": "users.all",
"action": [
"get",
"create"
]
}
]
You may use https://json-schema-faker.js.org/ to generate sample data for the schema. In website options, select
useExamplesValueand click on “Generate” multiple times to generate sample data.
You may use https://www.jsonschemavalidator.net/ to validate the schema.
npm install --save @impelsysinc/react-rbac
The API exposes a useRBAC hook which optionally takes default permissions.
Or you can setPermissions from useRBACContext hook.
See example Using useRBAC hook.
useRBAC hookuseRBAC hook returns useful methods which can be retrieved from RBACContext in any nested components (click and open accordion to see usage)PrivateComponent will render if resource has read access.
WithPermission will render if resource has read access.
WithPermission HOCWithPermission HOC is a ready-made component to pass the required access privileges (click and open accordion to see usage)useRBAC HookGet a rbac context to pass it to RBACProvider.
RBACProvider Context Providerconst rbac = useRBAC();
<RBACProvider value={rbac}>
{children}
</RBACProvider>
useRBACContext ContextMust be in one of the nested child component of RBACProvider.
| Value | Type | Description |
|---|---|---|
loadingPermissions |
{boolean} |
Async load permission. |
permissions |
{Permission} |
List of permissions. |
permissionError |
{Error} |
Any errors while fetching permissions. |
setPermissions |
(Permission[]) => void |
Manually set the permissions. |
clearPermissions |
{() => void} |
Clear all permissions from state. |
canAccess |
{permission => boolean} |
Is a rule valid i.e. a resource accessible for the loaded permissions. |
// Example 1
const { canAccess } = useRBACContext();
// Example 2
const { setPermissions, clearPermissions, permissions } = useRBACContext();
WithPermission Higher Order ComponentA useful component to wrap any other component which need fine-grained permissions.
| PropKey | Type | Defaults | Description |
|---|---|---|---|
children |
{ReactNode} |
ReactNode children components | |
type |
{string} |
[default=allow] |
Either allow or deny permissive type of the rule. |
action |
{string | string[]} |
The kind of action(s) allowed for the given resource e.g. “get”, “get.all”, “update”, “update.all”, etc. | |
resource |
{string} |
The target resource of the rule e.g. “product.description”, “product.*”, “product”, etc. | |
resourceType |
{string} |
[optional] |
A meta field to specify the type of resource e.g. “menu”, “page”, “component”, “*”, etc. |
record |
{Object} |
[optional] |
Context of the permission i.e. any extra metadata e.g. { userId: 1, groupId: 2 }. |
<WithPermission resource="product.description" action="read">
{children}
</WithPermission>
See Contribute.md
|
Abhisek Pattnaik 🤔 💻 👀 🐛 🚧 ✅ 💬 📢 |
This project follows the all-contributors specification.
Contributions of any kind are welcome!
See contribute.md for more information.
MIT © Impelsys India Pvt. Ltd.