AD Group aggregation task failing post upgrade to 8.3p4

[bhoyars_1 (Bhoyar Santhosh)]

Hi All,

We upgraded to patch 8.3p4, and after the upgrade, we are facing issues with the AD group aggregation task failing. Is anyone else facing a similar issue.?

Error: Reason: failed to lazily initialize a collection of role: sailpoint.object.Rule.referencedRules, could not initialize proxy - no Session.

Thanks,
Santhosh Bhoyar

[enistri_devo (Emanuele Nistri)]

Hi,

check the configuration of AD, because the communication between IIQ and AD is not working. Something could pass on AD after the upgrade. What version did you update from?

[sunny_tsang]

Check if you have a group customization rule defined in your group aggregation task.

Often times when I’ve encountered that error, i was iterating over a collection of roles and prematurely made a context.decache() call. You could also have code trying to iterate a collection of roles but you never instantiated the object.

[bhoyars_1 (Bhoyar Santhosh)]

Thanks @sunny_tsang
Its working now.

[bhoyars_1 (Bhoyar Santhosh)]

Hello @Sunny Tsang
Task is completed successfully without partitioning enabled, If we enabled the partitioning option its getting failed with the same error.
failed to lazily initialize a collection of role: sailpoint.object.Rule.referencedRules, could not initialize proxy - no Session.

[sunny_tsang]

I think there might be a bug that I never submitted a ticket for. I wrote a comment to myself 5 months ago that enabling partitioning for AD group aggregation causes that error even though my group refresh rule was very simple (making it not requestable). My workaround was to not enable partitioning for now since my use case does not involve making AD groups requestable.

I knew I had seen it before, but wasn’t quite sure until now.