Request structure
A request consists of base metadata, actions, authorizers and/or implementers and request attributes. Through the lifetime of the request this data is stored/modified in Bravura Identity 's backend SQL tables. The below sections detail these SQL tables along with some of their more important columns.
Base metadata
Base metadata refers to information about the request itself. Some notable items are:
Request ID: This is a unique guid assigned to each request.
In the Requests UI, when choosing a request, this guid can be seen in the URL bar.
This unique identifier is useful for troubleshooting exercises as:
It can be used to trace request execution in the idmsuite logging.
It can be used to pull information on the request from the backend SQL tables.
Request Name: This is a unique readable name assigned to the request.
In the Requests UI, when choosing a request, this will show in right pane under Details and will be formatted YYYYMMDD-X.
Request Status: This is current operational status of the request.
The status will clearly state if the request is "Processing", "Calculating Authorizers", "Approved, performing requested operations", "Processed".
In the Requests UI, when choosing a request, this will show in the right pane under Details.
Requester: Who initiated the request.
Recipient: Who the request is for.
PDR ID: From which PDR the request was generated.
The base metadata for a request is stored in the reqbatch table.
Request attributes
Attributes can be added to a request at submission time and can be modified further via custom request rewrite scripts or component-utilized policy tables. These attributes can be used by custom or default component logic to execute their designated tasks.
In reqinfo the attribute's name and value can be found in addition to the request those request attribute's belong to.
The attributes for a request are stored in the reqinfo table.
Request actions
A "Request Action" comprises of a resource and an operation.
The resource is the object / entitlement that will be modified by the Operation. Examples of resources are profiles, accounts and groups.
An operation is executed against a resource. Examples of operations are account additions/deletions, group additions / deletions, role additions / deletions. As the operation executes its "status" (for example approved/canceled) and "result" (for example failed/successful) will be recorded.
Request ACTIONS for a request are stored in the reqacct table.
Authorizer and Implementers (stored in authreq table)
An authorizer is a user who is assigned to approve/deny a request action. An Implementer is a user who is assigned to a request action which requires manual execution of tasks in target systems.
For each request, Bravura Identity records / modifies the status of implementer and authorizer activities. It also records / modifies the assignment of authorizers and implementers to a request action.
Authorizer and Implementer activity is stored in the authreq table.