Issue with response mapping

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

We are currently facing issue with response mapping in our web services source during account creation. Although the accounts are being successfully created, the response mapping is not functioning as expected.

The target response from the application after account creation is:

{
  "CSODCreationid": 78731
}

we attempted to map the CSODCreationid attribute to verify the response, but it is consistently coming back as blank in IdentityNow.

I have also attached the following for reference:

The response mapping configuration

image
image994×404 11.5 KB

image
image800×355 50.9 KB

The account schema used for validation

image
image1066×343 12.4 KB

I would appreciate any guidance on potential misconfigurations or necessary changes to ensure the response mapping works correctly.

Looking forward to your support.

2

hi need some clarity please:
“Although the accounts are being successfully created, the response mapping is not functioning as expected”

you mean account is created but ISC is unable to fetch userid?

are you sure root path is correctly defined? I suggest to check root path (use json path validator tool to check correct root path)

3

Hi @karishma_shaik2,

What is your account schema like? Is userId marked as Account ID and Account Name? If not give it a try please.

4

hi based on the screenshots that you have shared the configuration looks fine. But can you validate once by pulling the source from postman also. As Amar mentioned this should be atleast Account ID (nativeIdentity) if all of your endpoints rely on this userId.
If still this does not work you can validate by attaching AfterOperationRule and if required make a get call and return your response to return all the attributes for the account along with userId.

1 Like
5

userId is not account id for us. we have unique account number which is marked as Account Id

6

Hi Shaik,

As I understand, SailPoint ISC expects an account with all mandatory account attributes(account ID and name) to be returned after a create account operation.

If your API response do not return these required values until a manual action from end-user like accept the invitation, you may try returning empty strings for the account ID and name in Response Mapping and wait for account aggregation to fix the empty account.

If your API response can return these required values immediately, I believe @udayputta’s suggestion above to run a Web Services After Operation Rule | SailPoint Developer Community would be a solid solution.

Good luck.