AD Group aggregation task error

IdentityIQ (IIQ) IIQ Discussion and Questions
,
1

Hi,

We are encountering an exception during the AD group full aggregation task. Does anyone have any ideas on how to resolve this?

Error:

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

Thanks!

Santhosh B

2

Hi @bhoyars_1,

are you using some rule during the group aggrergation? Like a customization rule

3

@bhoyars_1

The error you’re experiencing during the Active Directory (AD) group full aggregation task in SailPoint IdentityIQ is a Hibernate exception related to lazy initialization:
Reason: failed to lazily initialize a collection of role: sailpoint.object.Rule.referencedRules; could not initialize proxy - no session.

Possible Cause: Customization Logic

One common reason for this error is custom logic implemented within your IdentityIQ environment—such as a Group Refresh Rule or other custom rules associated with your AD application. If you have any custom code that interacts with rules or references the referencedRules collection, it might be accessing this data outside of an active Hibernate session, causing the lazy initialization exception.

Recommended Actions:

Review Custom Code and Rules:

  • Identify Customizations: Check if you have implemented any custom logic like a Group Refresh Rule or other custom rules for the AD application.
  • Analyze the Code: If such customizations exist, please review the code to identify any access to the referencedRules property of Rule objects.

Thanks

1 Like
5

Hi @bhoyars_1 the error is coming from a rule related to the groups either from the AD application like customization rule OR another rule like Aggregation Rule.

6

Yeah we are using group refresh rule but for Delta group aggregation task is not failing, its failing only for Full-group aggregation.
Same rule configure in lower instances but there is no issue with that.

Thanks,
Santhosh

7

Yeah we are using group refresh rule but for Delta group aggregation task is not failing, its failing only for Full-group aggregation.
Same rule configure in lower instances but there is no issue with that.
Here is the logs:

sailpoint.object.Rule.referencedRules, could not initialize proxy - no Session
sailpoint.tools.GeneralException: failed to lazily initialize a collection of role: sailpoint.object.Rule.referencedRules, could not initialize proxy - no Session
at sailpoint.api.Aggregator.getInheritedGroup(Aggregator.java:6598) ~[identityiq.jar:8.3p4 Build 70e6b82a582-20240620-112139]
at sailpoint.api.Aggregator.assignHierarchy(Aggregator.java:6474) ~[identityiq.jar:8.3p4 Build 70e6b82a582-20240620-112139]
at sailpoint.api.Aggregator.refreshAccountGroup(Aggregator.java:6425) ~[identityiq.jar:8.3p4 Build 70e6b82a582-20240620-112139]
at sailpoint.api.Aggregator.aggregateGroup(Aggregator.java:6073) [identityiq.jar:8.3p4 Build 70e6b82a582-20240620-112139]
at sailpoint.api.Aggregator.aggregationPartitionedGroups(Aggregator.java:5795) [identityiq.jar:8.3p4 Build 70e6b82a582-20240620-112139]
at sailpoint.api.Aggregator.aggregateGroups(Aggregator.java:5526) [identityiq.jar:8.3p4 Build 70e6b82a582-20240620-112139]
at sailpoint.api.Aggregator.aggregateApplication(Aggregator.java:2800) [identityiq.jar:8.3p4 Build 70e6b82a582-20240620-112139]
at sailpoint.api.Aggregator.phaseAggregate(Aggregator.java:2681) [identityiq.jar:8.3p4 Build 70e6b82a582-20240620-112139]
at sailpoint.api.Aggregator.execute(Aggregator.java:2290) [identityiq.jar:8.3p4 Build 70e6b82a582-20240620-112139]
at sailpoint.request.AggregationRequestExecutor.execute(AggregationRequestExecutor.java:95) [identityiq.jar:8.3p4 Build 70e6b82a582-20240620-112139]

Thanks,
Santhosh

8

Yes,
We are using Group aggregation rule.

9

Hello,
Did you get any solution for this issue? I am also getting the same but in the access request after approval is completed and in my application configuration I am not using any rules as well.

10

@bhoyars_1 these kind of error generally appear when either you are using complete object and passing the entire object here and there. Or you are using context.saveobject(). there may be other reason but in your case these 2 may be
so to resolve whenever you want to get object for that user project query and first get name or id of object then pass that name and id and get object from context.getObjectByName and use it while saving use context.save(the sameobject)

Also do not commit multiple time you can do commit one time only.

11

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