The AriadNext connector also provides an endpoint to retrieve card information (for example an endpoint that is used by INverify). When called, it starts a card process in Identity Manager Operator to provide the requested information. Optionally, the response from Identity Manager, in the form of a data map used by the process, can be converted into a custom JSON format.
- Configure the card endpoint in config/idm-operator.yaml. There you will also find a detailed description of all settings.
The settings cover:
- The URL that will start an Identity Manager Operator process, for example:
ws/processes/<processId>/startGetDataAndExecute/<taskId>?tenantId=1&maxAttempts=10&interval=2000
To get card information, use the Identity Manager REST API request "startGetDataAndExecute" since it starts the process and waits until the task "taskId" is executed and retrieves the data map. See Identity Manager Process REST API for more information.
- The list of parameters that will be passed to the process.
- A custom transformation of the process data from XML to custom JSON format.
- A mapping of process execution API responses into custom http response codes.
ReST call configuration:
1. The HTTP method must be GET.
2. URL:
http://{ariad-next-connector-host}:{ariad-next-connector-port}/api/card?param=value
3. Query parameters: An optional list of parameters will be passed to Identity Manager Operator and added to the process map when the process is started.
4. Authentication as described in config/idm-operator.yaml
5. Define the JSON Format to transform the response body. See config/idm-operator.yaml for details.
6. Define a mapping of responses to custom response codes. See config/idm-operator.yaml for details.