# GetObject for JDBC connector

**URL:** <https://developer.sailpoint.com/discuss/t/getobject-for-jdbc-connector/18441>\
**Category:** SHF Discussion and Questions\
**Tags:** identity-security-cloud, aggregation\
**Created:** [October 2, 2023, 5:49am UTC](https://developer.sailpoint.com/discuss/t/getobject-for-jdbc-connector/18441 "2023-10-02T05:49:23Z")\
**Posts on this page:** 8\
**Page:** 1

<div class="post-metadata">

**Author:** ![yunus\_merck](https://avatars.discourse-cdn.com/v4/letter/y/22d042/32.png) [@yunus\_merck](https://developer.sailpoint.com/discuss/u/yunus_merck)\
**Post date:** [October 2, 2023, 5:49am UTC](https://developer.sailpoint.com/discuss/t/getobject-for-jdbc-connector/18441/1 "2023-10-02T05:49:23Z")

</div>

Hi,  
For the JDBC connector in IDN, how the getObject for single identity works automatically. For instance, as soon as the provisioing is done in the target system, it should run single account aggregation automatically and relfect the data on the IDN UI account. Basically the way getObject works for AD.

We have a Single Account Query config in UI but is there any other configuration we need to do to achieve it?

In the connetor doc, The JDBC source retrieves an object after it has been provisioned, when

- the getObjectSQL query is configured.–I have configured the single account query
- the CON\_JDBC\_USE\_GET\_OBJECT\_AFTER\_PROVISION feature flag is enabled. I have set it as true under the connector attributes

Thanks

---

<div class="post-metadata">

**Author:** ![iamnithesh](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/iamnithesh/32/42445_2.png) [@iamnithesh](https://developer.sailpoint.com/discuss/u/iamnithesh)\
**Post date:** [October 2, 2023, 1:39pm UTC](https://developer.sailpoint.com/discuss/t/getobject-for-jdbc-connector/18441/2 "2023-10-02T13:39:09Z")

</div>

> [@yunus\_merck](#):
>
> the getObjectSQL query is configured.–I have configured the single account query

Can you please share the query you have used for Single Object Aggregation?

---

<div class="post-metadata">

**Author:** ![yunus\_merck](https://avatars.discourse-cdn.com/v4/letter/y/22d042/32.png) [@yunus\_merck](https://developer.sailpoint.com/discuss/u/yunus_merck)\
**Post date:** [October 2, 2023, 2:09pm UTC](https://developer.sailpoint.com/discuss/t/getobject-for-jdbc-connector/18441/4 "2023-10-02T14:09:25Z")

</div>

Hi,

The query looks like this-

SELECT firstname, lastname,email, profile FROM “tableName” WHERE id=‘$(identity)’.

The query works fine when i run the aggregate account from UI for that particular record, so there is no issue with the query.

Thanks

---

<div class="post-metadata">

**Author:** ![yunus\_merck](https://avatars.discourse-cdn.com/v4/letter/y/22d042/32.png) [@yunus\_merck](https://developer.sailpoint.com/discuss/u/yunus_merck)\
**Post date:** [October 3, 2023, 9:02am UTC](https://developer.sailpoint.com/discuss/t/getobject-for-jdbc-connector/18441/5 "2023-10-03T09:02:02Z")

</div>

I discussed it with my colleague and he is also facing the same issue. Data is not getting reflected after provisioning until full aggregation runs.

@colin_mckibben - Did something change with respect to the connector from the Sailpoint end which could have caused this?

---

<div class="post-metadata">

**Author:** ![gauravsajwan1](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/gauravsajwan1/32/7856_2.png) [@gauravsajwan1](https://developer.sailpoint.com/discuss/u/gauravsajwan1)\
**Post date:** [October 4, 2023, 12:17pm UTC](https://developer.sailpoint.com/discuss/t/getobject-for-jdbc-connector/18441/6 "2023-10-04T12:17:01Z")

</div>

We’re also seeing this behavior in one of our customers. I checked the SaaS release notes but didn’t find any update related to JDBC source.

@colin_mckibben, just wondering if it would be possible to check with the product/engineering team if something went in past 1-2 weeks for JDBC source that might have caused the issue?

---

<div class="post-metadata">

**Author:** ![colin\_mckibben](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/colin_mckibben/32/37182_2.png) [@colin\_mckibben](https://developer.sailpoint.com/discuss/u/colin_mckibben)\
**Post date:** [October 4, 2023, 2:29pm UTC](https://developer.sailpoint.com/discuss/t/getobject-for-jdbc-connector/18441/7 "2023-10-04T14:29:35Z")

</div>

If this was working until recently then you should open a support ticket. It sounds like a bug or a regression, and support knows how to route these to the right team.

---

<div class="post-metadata">

**Author:** ![RAKGDS](https://sea1.discourse-cdn.com/sailpoint/discuss/user_avatar/developer.sailpoint.com/rakgds/32/2795_2.png) [@RAKGDS](https://developer.sailpoint.com/discuss/u/RAKGDS)\
**Post date:** [October 13, 2023, 4:58am UTC](https://developer.sailpoint.com/discuss/t/getobject-for-jdbc-connector/18441/8 "2023-10-13T04:58:01Z")

</div>

There was a change in the way the connector works. Please add the below in the source and let us know if the issue gets fixed.

Patch : https://{{tenant}}.api.identitynow.com/v3/sources/:id  
Body:

```json
[
  {
    "op": "add",
    "path": "/connectorAttributes/getObjectAfterProvision",
    "value": true
  }
]

```

---

<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:** [December 12, 2023, 4:58am UTC](https://developer.sailpoint.com/discuss/t/getobject-for-jdbc-connector/18441/9 "2023-12-12T04:58:55Z")

</div>

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