Refresh Errors - SysLog Overrun

Which IIQ version are you inquiring about?

8.4sp2

Issue Summary

We are trying to troubleshoot the source of this log error. It is an error related to a bad lookup when IdentityIQ tries to resolve an Identity Cube for the manager attribute. We have an identity attribute source rule that pulls the manager from our HR application. We want to suppress this log error:
image

Note that we even set a custom rule that would return NULL instead of “00000000” for the manager cube username. It still doesn’t suppress this. As a final resort, I set the rule to return a static ID that would resolve to a valid Identity Cube. However, there is still something within the Refresh task that still tries to resolve that bad manager. This error is not useful to us because we know that our HR app puts in “00000000” for users that don’t have a manager.

What are other places to look?

Hi @acrumley ,

Review Identity Attribute Mapping:

Navigate to Identity Mappings > Manager.

Ensure the manager attribute is mapped only through the identity attribute source rule.

Verify that no default or fallback logic is assigning “00000000” when no manager exists.

Check Mapping in HR Application:

Go to Application > [HR App] > Schema > Identity Attributes.

Confirm whether the manager field (e.g., supervisorId) is being directly pulled from the source system.

If the value “00000000” is coming from the HR system, update the mapping or use a rule to override it.

Prefer using a Identity Attribute Rule to return null when no valid manager is present.

3 Likes

We had to change our manager rule for our authoritative HR application. When the id was “000000000”, we simply returned null on the manager. Changing the application level rule fixed this issue.

1 Like

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