Identity attribute not found on GetObject Webservices

IdentityIQ (IIQ) IIQ Discussion and Questions
,
1

Which IIQ version are you inquiring about?

Version 8.X

Please share any images or screenshots, if relevant.

Share all details related to your problem, including any error messages you may have received.

Hello ,

We are doing a WebService connector, and we got an error when mapping attributes in getObject operation :
’ Caused by: org.apache.bsf.BSFException: The application script threw an exception: sailpoint.connector.ConnectorException: Identity attribute [URLID] was not found.’

and it’s configured on the app schema :

But when removing the mapping on Response Attribute Mapping
it works

We want to map the response but we get the error as mentionned as mentioned before
any idea where probleme is ?

NB : we checked the account an the identities

2

Hi Massinissa,
It would be great if you could share schema and operation response mappings for accounts aggregation so we could take a look if there are no errors. (Perfect would be whole app xml after anonymizing).

3

Hi @massinissa

Can you provide the screenshot of the Get Object response mapping, from your error it is mostly misconfiguration of response mapping.

Have you configured the account attribute in response mapping with same case, i.e., URLID with all capitals?

Regards,
Uday

4

Hi
yes i checked all the configurations , adding to that the account aggregration is working,

Regards

5

Can you can share the context URL configured and the response mapping of Get Object, it would help us to suggest better.

Regards,
Uday Kilambi

7

Hi @massinissa,

is the attribute path correct and context url correct?
attribute path has any extensions. maybe share the postman response on get users to see how the response comes.

8

Do not see any issues with your sample script, ofcourse you could also test the same from UI, performing single account aggregation on the identity. As Vinod mentioned, share the response body from postman to validate if the path given is correct.

9

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