Access Control
Last updated
Was this helpful?
Last updated
Was this helpful?
Get the list of actions based on the input parameters.
/access/v1/actions/_search
The list of role codes.
The list of feature id's.
unique API ID
API version
response timestamp YYYY-MM-DDThh:mm:ss+/-nn:nn (timezone defaulted to +5.30)
api action like GET/POST/PUT/DELETE in case of http calls
device UUID from which API is called
API key (dynamic)
unique request message id, UUID, for handling API idempotency
UserId of the user calling
//session/jwt/saml token/oauth token
To create new action(s) in the system. An action entry is required for each and every path to authenticate the access based on the assigned role of an user.
/access/v1/actions/_create
RequestInfo should be used to carry meta information about the requests to the server as described in the fields below. All eGov APIs will use requestinfo as a part of the request body to carry this meta information. Some of this information will be returned back from the server as part of the ResponseInfo in the response body to ensure correlation.
action master
if enabled or not
left icon
url for navigating
right icon
Unique Identifier of the tenant, Like AP, AP.Kurnool etc.
unique id for feature
codes specifying role
To update the existing action(s) in the system.
/access/v1/actions/_update
RequestInfo should be used to carry meta information about the requests to the server as described in the fields below. All eGov APIs will use requestinfo as a part of the request body to carry this meta information. Some of this information will be returned back from the server as part of the ResponseInfo in the response body to ensure correlation.
action master
if enabled or not
left icon
url for navigating
right icon
Unique Identifier of the tenant, Like AP, AP.Kurnool etc.
unique id for feature
codes specifying role
Validate a particular action for a given tenant and roles of the tenant.
/access/v1/actions/_validate
RequestInfo should be used to carry meta information about the requests to the server as described in the fields below. All eGov APIs will use requestinfo as a part of the request body to carry this meta information. Some of this information will be returned back from the server as part of the ResponseInfo in the response body to ensure correlation.
Create mapping for feature and role.
/access/v1/feature-role/_create
List of Role Id to be provided for mapping it to feature.
Unique Identifier of the tenant, Like AP, AP.Kurnool etc.
Get the list of roles based on role codes in the input parameters.
/access/v1/roles/_search
The list of comma separated codes to filter Roles against. No providing any would end up in all Roles as there is nothing to filter against
RequestInfo should be used to carry meta information about the requests to the server as described in the fields below. All eGov APIs will use requestinfo as a part of the request body to carry this meta information. Some of this information will be returned back from the server as part of the ResponseInfo in the response body to ensure correlation.
To create new Role(s) in the system.
/access/v1/roles/_create
RequestInfo should be used to carry meta information about the requests to the server as described in the fields below. All eGov APIs will use requestinfo as a part of the request body to carry this meta information. Some of this information will be returned back from the server as part of the ResponseInfo in the response body to ensure correlation.
To update the existing role(s) in the system.
/access/v1/roles/_update
RequestInfo should be used to carry meta information about the requests to the server as described in the fields below. All eGov APIs will use requestinfo as a part of the request body to carry this meta information. Some of this information will be returned back from the server as part of the ResponseInfo in the response body to ensure correlation.
Create mapping for role and action(s).
/access/v1/role-actions/_create
RequestInfo should be used to carry meta information about the requests to the server as described in the fields below. All eGov APIs will use requestinfo as a part of the request body to carry this meta information. Some of this information will be returned back from the server as part of the ResponseInfo in the response body to ensure correlation.
minimal representation of the Roles in the system to be carried along in UserInfo with RequestInfo meta data. Actual authorization service to extend this to have more role related attributes
Unique Identifier of the tenant, Like AP, AP.Kurnool etc.