Click HERE to see how Saviynt Intelligence is transforming the industry. |
06/03/2023 06:57 AM - edited 06/03/2023 06:59 AM
Hi Everyone
Need your help with connection JSON. We have an application, which we want to onboard however it has a different type of authorization. it has a hardcode authorization value which needs to enter in the HTTP header. i am attaching a screenshot of Postman. I tried to build the connection JSON but looks like it is not working
Connection JSON
Solved! Go to Solution.
06/04/2023 05:34 AM
Please try with below:
{
"authentications":
{
"acctAuth":
{
"authType": "Basic",
"httpHeaders":
{
"x-api-key": "<enter api here>",
"contentType": "application/json"
},
"authError":
[
"InvalidAuthenticationToken",
"AuthenticationFailed"
],
"errorPath": "error",
"retryFailureStatusCode": [401],
"maxRefreshTryCount": 5
}
}
}
************************************************************************************
{
"accountParams": {
"connection": "acctAuth",
"processingType": "SequentialAndIterative",
"statusAndThresholdConfig": {
"accountThresholdValue": 3000,
"correlateInactiveAccounts": true,
"inactivateAccountsNotInFile": false
},
"call": {
"call1": {
"callOrder": 0,
"stageNumber": 0,
"connection": "acctAuth",
"makeProcessingStatus": false,
"disableDeletedAccounts": false,
"http": {
"url": "url here",
"httpMethod": "GET",
"httpContentType": "application/json",
"httpHeaders": {
"x-api-key": "<enter api key here>",
"Accept": "application/json"
}
},
"listField": "users",
"keyField": "accountID",
"colsToPropsMap": {
"accountID": "userId~#~char",
"name": "userId~#~char",
"displayName": "userId~#~char",
"customproperty1": "isActive~#~char",
"customproperty31": "STORE#ACC#ENT#MAPPINGINFO~#~char"
}
}
},
"acctEntMappings": {
"Role": {
"listPath": "userRoles",
"idPath": "role",
"keyField": "entitlementID"
}
}
}
}
06/04/2023 08:19 AM - edited 06/04/2023 08:28 AM
Hi Nimitdave,
thankyou for helping with it and sorry to ask lots of questions and help. Since I started learning therefore still i am understanding the rest connection function and their JSON
I am getting errors while running the job. could you please suggest, what I am doing wrong?
Here is AccountImport JSON , I am using it
{
"accountParams": {
"connection": "acctAuth",
"processingType": "SequentialAndIterative",
"statusAndThresholdConfig": {
"inactivateAccountsNotInFile": false
},
"call": {
"call1": {
"callOrder": 0,
"stageNumber": 0,
"http": {
"url": "https://rc-ctlm-sbx-aapi.us1.controlm.com/automation-api/config/authorization/users",
"httpHeaders": {
"x-api-key": "<I entered API key>",
"Accept": "application/json",
"Content-Type": "application/json"
},
"httpContentType": "application/json",
"httpMethod": "GET"
},
"listField": "result",
"keyField": "accountID",
"colsToPropsMap": {
"accountID": "name~#~char",
"name": "name~#~char",
"status": "status~#~char",
"customproperty1": "name~#~char",
"customproperty2": "status~#~char",
"customproperty3": "memberof~#~char",
"customproperty31": "STORE#ACC#ENT#MAPPINGINFO~#~char"
}
}
},
"acctEntMappings": {
"Role": {
"importAsEntitlement": false,
"listPath": "",
"idPath": "roleId",
"keyField": "entitlementID"
}
}
},
"entitlementParams": {
"connection": "acctAuth",
"processingType": "SequentialAndIterative",
"entTypes": {
"Role": {
"entTypeOrder": 0,
"call": {
"call1": {
"callOrder": 0,
"stageNumber": 0,
"http": {
"url": "https://rc-ctlm-sbx-aapi.us1.controlm.com/automation-api/config/authorization/roles",
"httpHeaders": {
"x-api-key": "<I entered API key>",
"Accept": "application/json",
"Content-Type": "application/json"
},
"httpContentType": "application/json",
"httpMethod": "GET"
},
"listField": "",
"keyField": "entitlementID",
"colsToPropsMap": {
"entitlementID": "name~#~char",
"entitlement_value": "name~#~char",
"Description": "Description~#~char"
},
"disableDeletedEntitlements": "true"
}
}
}
}
},
"acctEntParams": {
"entTypes": {
"Role": {
"call": {
"call1": {
"processingType": "acctToEntMapping"
}
}
}
}
}
}
here is POSTMAN response body, where you can see, the path is not there. then what listField" should in Accountimport JSON
06/08/2023 09:15 AM
@navneetv this is done right. I remember replying on another forum ticket
06/08/2023 09:11 PM - edited 06/08/2023 09:40 PM
Hi Saviynt Team,
Thank you Nimit for helping with it. You fixed almost everything. I posted another thing and it was resolved too. You guys are awesome