NathanHans (Customer) to rsaSFDCadmin (RSA): asked a question.
Uneven values found for JsonPath
We have a rest API that is collecting CyberArk Safe information. When I go to
pull it in I'm getting the attached error.
I think this is because on some CyberArk Safes we have an "IGL_Application"
Field filled in like the first entry in the sample below. The second entry
doesn't have this. What I've found is if I pull a group of safes where NONE of
them have that field, the attached error gets displayed and the collection
fails. The workaround so far is to ensure we are pulling enough entries to get
at least 1 with the "IGL_Application" field.
I'm wondering if anyone knows of a different fix/workaround.
Sample JSON Results
{
"categoryModificationTime": 496,
"id": "194_10",
"name": "Application-xxxx",
"address": "xxxx",
"userName": "USERNAME",
"platformId": "xxxx",
"safeName": "SAFENAME",
"secretType": "password",
"platformAccountProperties": {
"IGL_Application": "VALUE"
},
"createdTime": 1607099765
},
{
"categoryModificationTime": 496,
"id": "194_14",
"name": "NAME",
"address": "ASSET",
"userName": "USERNAME",
"platformId": "XXXX",
"safeName": "SAFENAME",
"secretType": "password",
"platformAccountProperties": {},
"createdTime": 1626292018
}
pull it in I'm getting the attached error.
I think this is because on some CyberArk Safes we have an "IGL_Application"
Field filled in like the first entry in the sample below. The second entry
doesn't have this. What I've found is if I pull a group of safes where NONE of
them have that field, the attached error gets displayed and the collection
fails. The workaround so far is to ensure we are pulling enough entries to get
at least 1 with the "IGL_Application" field.
I'm wondering if anyone knows of a different fix/workaround.
Sample JSON Results
{
"categoryModificationTime": 496,
"id": "194_10",
"name": "Application-xxxx",
"address": "xxxx",
"userName": "USERNAME",
"platformId": "xxxx",
"safeName": "SAFENAME",
"secretType": "password",
"platformAccountProperties": {
"IGL_Application": "VALUE"
},
"createdTime": 1607099765
},
{
"categoryModificationTime": 496,
"id": "194_14",
"name": "NAME",
"address": "ASSET",
"userName": "USERNAME",
"platformId": "XXXX",
"safeName": "SAFENAME",
"secretType": "password",
"platformAccountProperties": {},
"createdTime": 1626292018
}
have collected accounts and related safes in 7.5.2 without issues.
RSA G&L 7.2.1 is end of life this month and hence you may think about
upgrading to 7.5.2 soon.