# Idenitity attribute not foung on GetObject Webservices

**URL:** <https://developer.sailpoint.com/discuss/t/idenitity-attribute-not-foung-on-getobject-webservices/71767>\
**Category:** IIQ Discussion and Questions\
**Tags:** webservice-connector, identityiq\
**Created:** [July 10, 2024, 1:00pm UTC](https://developer.sailpoint.com/discuss/t/idenitity-attribute-not-foung-on-getobject-webservices/71767 "2024-07-10T13:00:37Z")\
**Posts on this page:** 5\
**Page:** 1

<div class="post-metadata">

**Author:** ![massinissa](https://avatars.discourse-cdn.com/v4/letter/m/e19b73/32.png) [@massinissa](https://developer.sailpoint.com/discuss/u/massinissa)\
**Post date:** [July 10, 2024, 1:00pm UTC](https://developer.sailpoint.com/discuss/t/idenitity-attribute-not-foung-on-getobject-webservices/71767/1 "2024-07-10T13:00:37Z")

</div>

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 :

 ![image](https://global.discourse-cdn.com/sailpoint/original/2X/8/88b41777605434e10667563629de7ba214614604.png)

But when removing the mapping on Response Attribute Mapping  
it works

 ![image](https://global.discourse-cdn.com/sailpoint/original/2X/c/c200b4bb8a3a230be6c28656f3517a219e28905b.png)

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

---

<div class="post-metadata">

**Author:** ![enistriminsait](https://avatars.discourse-cdn.com/v4/letter/e/58f4c7/32.png) [@enistriminsait](https://developer.sailpoint.com/discuss/u/enistriminsait)\
**Post date:** [July 10, 2024, 1:12pm UTC](https://developer.sailpoint.com/discuss/t/idenitity-attribute-not-foung-on-getobject-webservices/71767/2 "2024-07-10T13:12:36Z")

</div>

Hi @massinissa,

getObject is launched after a provisioning or in the manage account page.  
I this you have this error after a creation or an update because in your response provPlan is not present this attribute.

If you can print the the plan in after rule of creation or update and share the logs

---

<div class="post-metadata">

**Author:** ![dylanfoggan](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/dylanfoggan/32/13658_2.png) [@dylanfoggan](https://developer.sailpoint.com/discuss/u/dylanfoggan)\
**Post date:** [July 10, 2024, 1:34pm UTC](https://developer.sailpoint.com/discuss/t/idenitity-attribute-not-foung-on-getobject-webservices/71767/3 "2024-07-10T13:34:13Z")

</div>

Hi @massinissa ,

I would suggest you confirm how the response is presented from the API request.

For Example:

```auto
{
   "URLID": "12345",
   "NAME": "testing"
}

```

The response mapping will be **$**. If you attempt to access the value through an array it should be represented as \* and not $.

Please let me know if this helps.

---

<div class="post-metadata">

**Author:** ![enistriminsait](https://avatars.discourse-cdn.com/v4/letter/e/58f4c7/32.png) [@enistriminsait](https://developer.sailpoint.com/discuss/u/enistriminsait)\
**Post date:** [July 10, 2024, 3:15pm UTC](https://developer.sailpoint.com/discuss/t/idenitity-attribute-not-foung-on-getobject-webservices/71767/5 "2024-07-10T15:15:48Z")

</div>

🧐 you can configure the getObject for account and getObject-group for entitlement and those are alaunche automatically after a provisioning.

Try to configure it without launch in the after rule.  
Also, in after rule print the plan so you can see if you the identifier in the plan

---

<div class="post-metadata">

**Author:** ![system](https://global.discourse-cdn.com/sailpoint/original/2X/f/f2136700ed5e3703e0b85e02f6be799dacca7735.png) [@system](https://developer.sailpoint.com/discuss/u/system)\
**Post date:** [September 8, 2024, 3:16pm UTC](https://developer.sailpoint.com/discuss/t/idenitity-attribute-not-foung-on-getobject-webservices/71767/6 "2024-09-08T15:16:07Z")

</div>

Closed on September 8, 2024, 3:16pm UTC

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