Cannot get property 'connection' on null object

[ejeong]

when trying to import application list from okta. 

I am seeing following error. Anyone seen this error?

Here is JSON I made

{
"accountParams": {
"connection": "acctAuth",
"processingType": "SequentialAndIterative",
"call": {
"call1": {
"callOrder": 0,
"stageNumber": 0,
"http": {
"url":
"httpHeaders": {
"Authorization":
},
"httpContentType": "application/x-www-form-urlencoded",
"httpMethod": "GET"
},
"listField": "",
"keyField": "accountID",
"colsToPropsMap": {
"customproperty1": "profile.login~#~char",
"name": "profile.login~#~char",
"lastlogondate": "lastLogin~#~millisec",
"accountID": "id~#~char",
"customproperty2": "profile.email~#~char",
"customproperty18": "profile.mobilePhone~#~char",
"customproperty6": "profile.firstName~#~char",
"customproperty9": "profile.lastName~#~char",
"displayname": "profile.displayName~#~char",
"customproperty15": "profile.employeeType~#~char",
"customproperty27": "lastLogin~#~char"
},
"pagination": {
"nextUrl": {
"nextUrlPath": "${(headers.Link?.contains(','))? headers.Link?.split(',')[1].replace('<', '').replace('>; rel=\"next\"','').trim() : ''}"
}
}
}
}
},
"entitlementParams": {
"connection": "acctAuth",
"processingType": "SequentialAndIterative",
"entTypes": {
"Group": {
"entTypeOrder": 0,
"call": {
"call1": {
"callOrder": 0,
"stageNumber": 0,
"http": {
"url": "",
"httpHeaders": {
"Authorization": "",
"Accept": "application/json"
},
"httpContentType": "application/json",
"httpMethod": "GET"
},
"listField": "",
"keyField": "entitlementID",
"colsToPropsMap": {
"entitlementID": "id~#~char",
"entitlement_value": "profile.name~#~char",
"displayname": "profile.description~#~char~#~char"
},
"pagination": {
"nextUrl": {
"nextUrlPath": "${(headers.Link?.contains(','))? headers.Link?.split(',')[1].replace('<', '').replace('>; rel=\"next\"','').trim() : ''}"
},
"disableDeletedEntitlements": true
}
}
}
},
"Applications": {
"entTypeOrder": 0,
"call": {
"call1": {
"callOrder": 0,
"stageNumber": 0,
"http": {
"url": "",
"httpHeaders": {
"Authorization": ,
"Accept": "application/json"
},
"httpContentType": "application/json",
"httpMethod": "GET"
},
"listField": "",
"keyField": "entitlementID",
"colsToPropsMap": {
"entitlementID": "id~#~char",
"entitlement_value": "name~#~char",
"displayname": "label~#~char"
},
"pagination": {
"nextUrl": {
"nextUrlPath": "${(headers.Link?.contains(','))? headers.Link?.split(',')[1].replace('<', '').replace('>; rel=\"next\"','').trim() : ''}"
},
"disableDeletedEntitlements": true
}
}
}
}
}
}
}

[rushikeshvartak]

Your connection name in json and connection json must be different 

[ejeong]

I suspected that... but it is same.. even I applied new connectionJSON yesterday..

[ejeong]

[naveenss]

@ejeong  looks like in your importJson acceEntParams is missing. please add a blank parameter like below and try once.

"acctEntParams":{}

[ejeong]

ah ok. let me try that

[ejeong]

@naveenss Thanks. that's fixed! 

I have one more question. can you please let me know why this import is not calling next page? 

This is may access import JSON

"Applications": {
"entTypeOrder": 0,
"call": {
"call1": {
"callOrder": 0,
"stageNumber": 1,
"http": {
"url": "https://URL/api/v1/apps?limit=200",
"httpHeaders": {
"Authorization": "",
"Accept": "application/json"
},
"httpContentType": "application/json",
"httpMethod": "GET"
},
"listField": "",
"keyField": "entitlementID",
"colsToPropsMap": {
"entitlementID": "id~#~char",
"entitlement_value": "name~#~char",
"displayname": "label~#~char",
"description": "label~#~char"
},
"pagination": {
"nextUrl": {
"nextUrlPath": "${(headers.Link?.contains(','))? headers.Link?.split(',')[1].replace('<', '').replace('>; rel=\"next\"','').trim() : ''}"
}

This is Header. I don't know why Saviynt is not caling next url and finish it without error

we have more than 800 active apps in OKTA so I am expecting all of them should be imported..

[naveenss]

Hi @ejeong  I dont see any problem with the pagination expression. Do you see any findings in the logs? Are you comfortable sharing the logs for me to debug further?

[ejeong]

@naveenss 

Since job went success, I don't see any error in the log...