Hello All,
we have upgraded IIQ 8.2P3 to 8.3P1.
We are using Active Directory Direct Connector to connect AD.
AD account is unable to disable during leaver process and getting below error.
ERROR Workflow Event Thread 1 sailpoint.api.nativeidentitychange.NativeIdentityChangeUtil:1483 - NativeIdentityChangeEvent has not been completed.
1 Like
Is NCD enabled in your connector? If it is, could you please attempt to disable it and then test your leaver process?
1 Like
@jespaancy
This is not related to Native Change detection, this is because of Native Identity Change Event Enabled by Default when you migrate to 8.3 P1
Please go ahead and disable the configuration if not needed as 8.3 P1 has a know bug related to this.
You can find this configuration under Global settings → Misc
‘Native Identity Change Event propagation’
Unchech this and clean all the existing data in Native Identity change event table
There is an OOTB configuration to prune the NativeIdentityChangeEvents, which should be configured to perform clean up on these objects, similar to pruning task results, or other objects. This would be a global option to delete all objects over a certain age.
In debug Configuration->SystemConfiguration
This value is the number of days to retain the objects. The default is “0”, which would not delete any objects. If you were to set it to “7” and run the prune option below, it would prune all objects older than 7 days, as an example.
In the Perform Maintenance task, there is an option: “Prune Native Identity Change Events”
Delete Native Identity Change Events older than the age specified in the system configuration
In the xml, it would show as below if enabled.
It would be recommended that you add this to your regular execution of the PM task which performs pruning (if you have a separate task for pruning objects, set it in that one).
Please go through below thread for more details on this issue
Active Directory ObjectGUID, move/rename support FAQ - Compass (sailpoint.com)
2 Likes
Thank you Satish. t works after disabled setting in Global setting.
Glad that worked , please mark the solution if this helped to resolve the issue so that can help other folks
This topic was automatically closed 60 days after the last reply. New replies are no longer allowed.