Novell eDirectory connector is failing to aggregate accounts and entitlements from connected source

[Vignesh48 (S Vignesh)]

Hi All,

We are utilizing the Novell eDirectory connector to meet our business needs

The connector was successfully configured in the production environment and functioned as anticipated. However, since last week, it has been unable to aggregate the accounts and entitlements.

We have scheduled the aggregation process to occur daily. However, since last week, the aggregation has been taking significantly longer, approximately 21 hours, and ultimately results in an error. Typically, the account aggregation completes within 2 to 3 hours, but this is no longer the case

Adding the error message below for account aggregation:
This aggregation failed because the currently running aggregation must complete before the next one can start. TaskResult - 7c59981931ab40f3ad0f6d19202aa8cc

The above is one of the new issue we are getting…

Similarly, the entitlement aggregation hardly takes 5 minutes to complete but from last week its getting failed.

Adding the error message below for entitlement aggregation:

1. Exception during aggregation of Object Type group on Application Novell eDirectory [source]. Reason: java.lang.RuntimeException: An error occurred while aggregating Application Novell eDirectory [source] An internal error occurred handling stream response from the server.
2. Exception during aggregation of Object Type group on Application Novell eDirectory [source]. Reason: java.lang.RuntimeException: An error occurred while aggregating Application Novell eDirectory [source]

We manually terminated the Account aggregation since its running foe long time…

Attached the SS for reference…

Any updated happened to this connector recently?? If yes what we have to do to the source??

Any quick help will be much appreciated since we having this issue in PROD…

[Arun-Kumar]

Hi Vignesh,

Are you getting this error on IIQ or ISC? Attatched screenshot refers the ISC.
What is the IIQ version ?

Regards,
Arun

[Vignesh48 (S Vignesh)]

Hi Arun,

We are getting this error in ISC. Not in IIQ…

[dylanfoggan]

Hi @Vignesh48 ,

I would suggest you check the tasks that are still in progress.

https://sailpoint.api.identitynow.com/beta/task-status

The API will check to see the list of task statuses. If there is a task that is pending I would recommend you update it so that it gets set as completed to re-attempt to aggregate the source.

It would help if you used this PATCH API:

https://sailpoint.api.identitynow.com/beta/task-status/:id

Here is the documentation if you need further guidance: update-task-status | SailPoint Developer Community

Thanks,

[Vignesh48 (S Vignesh)]

Hi @dylanfoggan ,

Thanks for the suggestion!

Do we need mark any pending provisioning for this connector as completed or any pending account and entitlement aggregation as completed to reattempt the aggregation?

Could you please clarify it??

[dylanfoggan]

Hi @Vignesh48 ,

If the provisioning task is an access request it should be okay to re-trigger the aggregation task. It may be different for attribute sync.

thanks,

[Vignesh48 (S Vignesh)]

Hi @dylanfoggan ,

Re-triggering the aggregation task manually sometime fixes the issue but not every time (Aggregation fails sometimes and success sometimes).

I’m not sure why its failing on scheduled aggregations and not in manual trigger aggregation?

Do you have any idea?

[dylanfoggan]

Hi @Vignesh48 ,

Just to take a step back quickly. Is it the same issue occurring for you now after these manual triggers? If so, can you confirm that no pending tasks are being executed for this source?

Thanks,

[Vignesh48 (S Vignesh)]

Hi @dylanfoggan ,

The connector is hybrid where account and entitlement aggregation is automated and provisioning is manually (SNow connector with RITM for service desk) handled.

Yes, I can see that there are 151 access request/identity refresh is pending for manual action either approval/grant access.

As far now, two manual trigger is happened, In both cases account aggregation was success.

Curious to know, This 151 pending tasks is creating the problem for account and entitlement aggregation which ending up in error??

[dylanfoggan]

The pending provisioning tasks should not be the issue. The scheduled aggregation tasks should not be affected when there are open access request items.

Thanks,

[Vignesh48 (S Vignesh)]

Understood!

I’m unsure what causing this aggregation issue?. I can’t see this issue happening in UAT, only in PROD.