Account are getting scanned but not getting created : JDBC

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

Hello Everyone,

We are facing some issue in one of the JDBC type source. Account aggregation is successful and its scanning the number of accounts. But the issue is, accounts are not populating in accounts page. Its just showing 0 accounts.

Please consider addressing the following when creating your topic:

  • What have you tried?

  • Did unoptimized aggregation.

  • Source/account reset.

  • Query is returning the results.

  • Checked with peek-resource object api call. And its returning accounts.

  • What errors did you face (share screenshots)?

image
image639Ă—761 10 KB

  • What is the result you are getting and what were you expecting?
    Accounts are getting scanned, but not populating in accounts page.
1 Like
2

@pooja_7
Can you check in the account schema for the source, if the account id and name are set.
Please make sure that the account id is present then only the account will be created. Also account id should be unique.

Letme know if still with the account ID you are facing issues.

3

Yes, account ID and name are set.
Account id is unique.

4

@pooja_7 … There seems to be issue with your account schema. Can you check that and run unoptimized aggregation.

1 Like
5

ok and does all the records that you are trying to pull has that value?

6

Hi @pooja_7,

If your schema is correct then, You may reset the source and try to do full aggregation.

-Vasanth

7

@pooja_7
Are you able to get user with account aggregation before provisioning ?if no then first fix the schema configuration or correlation which ever is failing this.
if yes,

  1. How the Native Identity is getting set ? is it application side or from schema of sailpoint , if this is in application side then update then create one of configuration for create and then check your getobject query
  2. if this is set in schema then make sure your correlation fine and get object query able to fetch proper data.
1 Like
8

Hello @pooja_7 ,

Try to validate the column names from Query and schema in IDN also try to validate the “mergeRows” connector attribute .

If there is multivalued attribute with the same values then you can remove the column from query(if possible).

Thanks,
Prasad

1 Like
9

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