PIRM task failure - LCM request scan failed on request 0000323244 with exception java.lang.IllegalArgumentException: nativeIdentity was null. A non-null native identity is required

IdentityIQ (IIQ) IIQ Discussion and Questions
1

Which IIQ version are you inquiring about?

8.3

Please share any other relevant files that may be required (for example, logs).

Failed Identity Request.txt (16.2 KB)

Share all details about your problem, including any error messages you may have received.

Hi everyone,

I am facing an issue with the Perform Identity Request Maintenance (PIRM) task.

We have an identity request that originally failed due to an SQL grammar error. Please see attached. The current status of the identity request is:

  • completionStatus: Failure

  • executionStatus: Completed

However, whenever the PRIM task runs, it still processes this identity request and fails with the following error:

LCM request scan failed on request 0000323244 with exception: java.lang.IllegalArgumentException: nativeIdentity was null. A non-null native identity is required.

I am trying to understand:

  1. Why is the PRIM task still processing this identity request even though its executionStatus is Completed?

  2. What is the recommended way to resolve this issue so that the PRIM task no longer fails on this request?

Has anyone encountered a similar issue or knows the root cause? Any insights or suggestions would be greatly appreciated.

Thanks,
Pragati

2

@r_pragati In your request verified field is missing. So request was picked by PIRM task. Add verified field with timestamp manually, if you want to skip processing it.

image
image1211×146 9.09 KB

3

@r_pragati Please check this thread if it helps: https://community.sailpoint.com/t5/IdentityIQ-Forum/Perform-Identity-Request-Maintenance-fail/m-p/278947#M199373

<entry key= "disablePreRefresh" value = "true"/>

Try adding this key to the PIRM task definition and see if it works or not.

4

@neel193 - It looks like there is a misunderstanding. He was referring to the PRIM task failure, whereas you are referring to the PRIM task definition. @r_pragati Prim task is it own application?

5

The request has failed with a NullPointerException. You must either update the request’s completion status manually or delete the request entirely. Because the task is unable to update the status automatically, please manually update both the request status and the provisioning status.

6

Hi @narayanag - There was typo in my original post. I was referring to the “Perform Identity Request Maintenance Task”.

7

@neel193 - Thank you for your response. Since this is production environment, I want to understand if there are any downsides of adding <entry key= "disablePreRefresh" value = "true"/> option to the PIRM task definition.

8

I will try the suggested options and update here. Thank you everyone!

9

@r_pragati This was recommended by Teresa in the mentioned link. This basically skips validating task results during PIRM evaluation. Here is what she mentioned:

"As a quick way to get past most failures in PIRM which may be caused by the initial refresh which it performs, you may add the below entry to the TaskDefinition xml to disable the refresh.

<entry key= "disablePreRefresh" value = "true"/>

That way the task will bypass any refresh errors and continue to the verification of the requests. You can verify by locating the stack trace for those errors to see if it has Identitizer class in it."