Full account aggregation deleting active accounts in JDBC direct source connection

Administration & Troubleshooting
, , , ,
1

Hi,

I’m new to Identity Now. I created a direct source connection of JDBC type.

Using below query for full account aggregation, returning 0 accounts. where as, its working in SQL Developer getting 100+ accounts but same query returning o accounts in IDN.

SELECT ISID,PSTN_NO,PRMRY_FIRST_NM,PRMRY_LAST_NM,WIN_NO,USER_ACCESS_LEVEL,USER_STATUS,RECORD_CREATE_DATE,RECORD_CREATED_ISID,COUNTRY,COMPANY_CODE,RECORD_UPDATE_DATE, RECORD_UPDATE_ISID,COUNTRY_CD,COMPANY,LOG_DEL_IND from ESA.USER_ROLE where USER_STATUS=‘ACTIVE’ ORDER BY ISID

I sincerely appreciate if anyone could help us here.

Thanks,
Bathini

Zero_Accounts_Scanned.PNG
Zero_Accounts_Scanned.PNG808×311 9.05 KB

Zero_Accounts_In_IDN.PNG
Zero_Accounts_In_IDN.PNG1301×237 10.2 KB

2

It could be a permission issue if the service account used for the source cannot see the accounts.

3

agree. what admin account password are you using in the one that works vs the one that doesn’t? are they the same? Also, what are you specifying in the Account Schema section in the UI? Do you have an Account ID and Name attribute defined and Groups defined as Entitlements and Multi-Valued?

4

Thanks for the quick responses  @jeff_warembourg   and  @paulo_urcid

1) Its the same service account which is working in sql developer Vs which is not working in IDN
2)Account ID and Name are mapped to same column (as attached in the screenshot)
3)Entitlements defined as group and Multivalued attributes are also defined as attached in screenshot.

Account_Schema.PNG
Account_Schema.PNG1895×681 32.2 KB

5

Interesting.  I’m not seeing anything amiss so at this point I think I would raise a support case.

6

Do you suggest me to open a support case  @jeff_warembourg

Just to add one suspect here, recently there was a VA update happened on the same environment. Do you think it can cause any such issue?

Suddenly my access request is also not completing with the below error. Please provide some info if you’ve encountered such error, else please ignore :slightly_smiling_face:

sailpoint.connector.ConnectorException: java.lang.InterruptedException: Timeout waiting for response to message 0 from client e4afabbb-21ab-4936-a04a-d67392ccb944 after 60 seconds.

7

That error indicates that the VA is not responding.  I would check the VA to ensure that it’s not in the middle of an update.  you can also try rebooting the VA if it’s not updating and waiting about 10 minutes and then trying again.  If that fails then yes, I would open a support case to get a more detailed look at it.

8

Assuming you have 2 min VAs in the cluster however there may be a communication issue between the VA(s) and the source as well.  you can log into the VA and use standard Linux networking commands like Ping to ensure that they can at least see each other.