Web Service Connector

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

Hi Team,

This is regarding Web Service VA Based connector.

Test Connection, Account Aggregation and Group Aggregation is working fine.

Issue:

I am facing issue in “Create Account” operation.

Request Body:

{
“firstName”: “$plan.firstName$”,
“lastName”: “$plan.lastName$”,
“division”: {
“href”: " https://tf-pca/782473"
},
“@Email”: “$plan.email$”,
“@AID”: “$plan.A_ID$”,
“@Program Code”: “$plan.Program_Code$”,
“@Academic Plan Code”: “$plan.academic_plan_code$”,
“@Faculty”: “$plan.faculty$”,
“@School”: " $plan.school$",
“@School Code”: “$plan.school_Code$”,
“@Course Code”: “$plan.course_Code$”,
“@Person”: “$plan.Person$”,
“accessGroups”: [
{
“accessGroups”: {
“href”: “https://gmail/1234”

        }
    }
]

}

Response is in Headers: (there is no response in body)
Here is the response:

Location: https://tw-fty2.uatad.toroid.ed.af:8944/api/simholder/6780898

so the requirement is to add the 6780898 as the native identity.

image
image1600×496 23.3 KB

Kindly suggest me the solution to fix it.

2

Hi @RAkhauri ,

Could you please tell us whether are you able to make the same call through postMan or any other API tool?

Also I would advise to print the plan before you make a API call.

3

I am trying to make the call via curl command on VA.

I do have the Provisioning plan which is captured while doing the provision on the target application.

<\/Map> <\/List> <\/value> <\/entry> <\/Map>
4

Are you able to make a call through curl command? Also post executing command are you seeing any successful response?

Can you capture the provisioningPlan? Looks like the above Map is completely empty.

5

Hi Ritu,

As discussed he best approach would be to write a before operation rule in Create operation, pass these parameters using the restClient in the rule and get the ID from the response and finally modify/update the requestendpoint containing headers and body. This will take care of the native identity issue.

6

Hi Ritu,

FYI

It’s not creation rule. It’s a before operation rule. For every HTTP API call we are allowed to write before/after rule. But in your case you have to write before operation rule and post you wrote it. Don’t forget to patch it to your source. We have a particular API for the same.

IHTH :slightly_smiling_face:

7

Hi Ritu. I think you are needing to invoke your url like

https://tw-fty2.uatad.toroid.ed.af:8944/api/simholder/ID

where ID is the attribute marked as account id on your schema. If that is your need, you can simply put this in your operation url:

https://tw-fty2.uatad.toroid.ed.af:8944/api/simholder/$plan.nativeIdentity$

(the same way you put $plan.X$ in your body).

8

This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.