...
5. Mapping of Roles and APIs/action are added in roleactions.json, under folder
ACCESSCONTROL-ROLEACTIONS.
Sample mapping:
| Code Block |
|---|
{
"tenantId": "uk",
"moduleName": "ACCESSCONTROL-ROLEACTIONS",
"roleactions": [
{
"rolecode": "TL_CEMP",
"actionid": 1685,
"actioncode": "",
"tenantId": "uk"
},
{
"rolecode": "CITIZEN",
"actionid": 1685,
"actioncode": "",
"tenantId": "uk"
}
]
} |
6. Role and API/action mapping is added as an array element under array roleactions.
7. Each mapping is defined with key-value pairs. keys are rolecode, actionid, actioncode and tenantId.
Sr. No. | key | Is Mandatory? | Definition/ Description |
|---|---|---|---|
1 | rolecode | Yes | The unique code of the role which is defined in roles.json and which required mapping for API. |
2 | actionid | Yes | The unique id of the API/action which is defined in actions-test.json and which is required to be mapped with the role. |
3 | actioncode | No | The code of the API/action which is defined in actions-test.json and which is required to be mapped with the role. |
4 | tenantid | Yes | tenant id of state. |
Reference Docs
Doc Links
Title | Link |
Sample actions-test.json | |
Sample roles.json | https://github.com/egovernments/ukd-mdms-data/blob/SDC/data/uk/ACCESSCONTROL-ROLES/roles.json |
Sample roleactions.json |