Mapping Roles With APIs
Roles define the permissions of a user to perform a group of tasks. The tasks are created as API calls to do certain actions when a request for those calls is sent by the system. For example, the key tasks for a Trade License application include initiate/apply, forward, approve or payment. For Trade License initiate two API calls, “create” and “update” is required. Create API creates and saves the application in the database and returns an application number. Update API saves the required attached documents in the file store and returns the success acknowledgement message of the application created. These create and update API access permission is granted to the roles named Citizen and TL counter employee.
Access permission is granted by mapping roles with APIs. Users assigned with the citizen or TL counter employee roles can initiate/apply the Trade License application.
Before proceeding with the configuration, make sure the following pre-requisites are met -
- Knowledge of DIGIT applications is required.
- Users should be aware of transactional steps in the DIGIT application.
- Knowledge of json and how to write a json is required.
- Knowledge of MDMS is required.
- User with permission to edit the git repository where MDMS data is configured.
In mapping roles with APIs, permission to perform a certain task can be restricted based on the requirement. For example, only the user with Role TL Counter Employee or Citizen can initiate the Trade License applications.
After mapping roles with APIs, the MDMS service needs to be restarted to read the newly added data.
APIs are added in actions-test.json and termed as action. In MDMS, file actions-test.json, under ACCESSCONTROL-ACTIONS-TEST folder APIs are added. API Sample:
"id": 1685, //<Unique identifier>
"name": "Create TradeLicense",
"url": "/tl-services/v1/_create", //<url of the feature>
"displayName": "Create TradeLicense",
"name": "Update TradeLicense",
"displayName": "Update TradeLicense",
APIs are added as action array elements with the request URL and other required details for the array "actions-test"
Each action is defined as a key-value pair:
A unique id that identifies an action.
A short narration provided to the action.
It is the request URL of API call.
It is the display name.
To enable or disable display in UI.
Code of the service to which API belongs.
Roles are added in roles.json In MDMS, file roles.json, under ACCESSCONTROL-ROLES folder roles are added. More about roles can be checked in the below link: Adding roles to System
Mapping of roles and APIs/actions is added in roleactions.json, under the folder ACCESSCONTROL-ROLEACTIONS. Sample mapping:
Role and API/action mapping is added as an array element under array roleactions. Each mapping is defined with key-value pairs. keys are rolecode, actionid, actioncode and tenantId.
The unique code of the role which is defined in roles.json and which required mapping for API.
The unique id of the API/action which is defined in actions-test.json and which is required to be mapped with the role.
The code of the API/action which is defined in actions-test.json and which is required to be mapped with the role.
tenant id of state.
Sample roleactions.json Roles APIs mapping
All content on this page by eGov Foundation is licensed under a Creative Commons Attribution 4.0 International License.