JDBCProvision Native Identity Issue

Identity Security Cloud (ISC) ISC Discussion and Questions
1

Hi everyone,

I am using account.getNativeIdentity() in a JDBCProvision rule in SailPoint ISC. Instead of getting the actual native identity value (e.g., EI013), I am receiving a UUID-like value (e.g., cecdb085cd1545059d2f23fae878d7).

I have attached screenshots showing:

  1. The account page where Native Identity (EI013) are visible.

    image
    image1439×259 17.3 KB

    2.The value I am getting in my rule.

    image
    image1424×294 16.1 KB

    Thank you.

2

Hi @vsuddala

From my understanding account.getNativeIdentity() is returning internal UUID, not the source account’s native Identity.

Can you try to use accountRequest.getNativeIdentity() or ProvisioningPlan.getAccountRequest(applicationName).getNativeIdentity();

Please see if t works

Thanks

3

Hi @Tursun

Thanks for the help. Like in IIQ, is there any way to write a test rule and run it somewhere?

Thank you.

4

Hi @vsuddala
You’re welcome.

I use RDK. Bellow I’ve attached the reference links

5

Hi @vsuddala ,

Can you try

Plan.getNativeIdentity();

See that helps

Thanks in advance
Avinash Mulpuru

6

Hi @amulpuru

Previous Logs

<AccountRequest application="Sample JDBC [source]"
                nativeIdentity="cecdb085cd1545059d2f0f23fae878d7"
                op="Create" />

But now, without changing my rule code, it is correctly showing the expected value:

<AccountRequest application="Sample JDBC [source]"
                nativeIdentity="EI013"
                op="Create" />

I did not change the rule logic, so I am trying to understand.

  1. What could cause this behavior to change automatically

  2. Does ISC cache native identity mappings and refresh them after aggregation or schema updates?

Any insights would be appreciated. Thanks!

7

Hi @vsuddala ,

Just want to know if you changed something in the account schema, like account ID.

regards,

Rohit