How to Map response attributes after we make API call in NERM?

Identity Security Cloud (ISC) ISC Discussion and Questions
,
1

Hi,
Need guidance on how to map response to the attributes after we make REST API action in NERM Workflow.
I am mapping the status code to one of the attribute and mapping other things and sending all of these details in an email notification.

I am getting status code as 200, rest everything is coming up as “-”

Not sure how to do the response mapping, I have tried everything that I can think of…

any insights are appreciated…

Edit

My json response is like below

[
{
    "Key1":"Value1",
    "Key2":"Value2",
    "attributes":{
                    "Key3":"Value3"
}
},

{
    "Key1":"Value4",
    "Key2":"Value5",
    "attributes":{
                    "Key3":"Value6"
}
}
]

I want to get 1st record’s some of the key values. I do not require all the data from the response.

Thanks,
Vaibhav

2

Hi Vaibhav - for your given response, I believe the mapping should be like element number > key

So, for Key1 in the first record, that would be 0 > Key1

For an attribute, that would be 0 > attributes > Key3

For the second record, it would be 1 > attributes> K3

1 Like
3

If your JSON has an “array” as shown in your example by the square brackets () then you need to use “positional referencing” which is ZERO based. Unlike many API based query tools, NERM just needs a number entered in without any quotes, brackets, etc.

If you export the workflow and look for “class_name”: “ApiConfigurationAttribute” you’ll have a corresponding “value_path” that looks like the following (extreme example from an integration with Experian)
“value_path”: “clientResponsePayload|decisionElements|0|otherData|json|fraudSolutions|response|products|preciseIDServer|kba|questionSet|0|questionSelect|questionChoice|2”

1 Like
4

The ui of attribute mapping was so confusing, I got how to map the attributes after the architect showed me in a AAA call.

Closing the discussion.

Thanks @ZackTarantino-Woolson , @edmarks
Vaibhav

1 Like
5

I agree with the UI being confusing and VERY cumbersome.

As a side note - If / when you have a lot of these to include that are similar you can put placeholder attributes in the configuration without the API path. Then export the workflow and manually copy/paste/edit the needed API mappings (ie I had to add ~50 once with 10+ levels).

6

I did not understand that Ed :slight_smile: but thats okay.. I will work with what I have understood.

1 Like
7

@vdivakar My apologies, but very hard to explain in text.

1 Like