Error while enabling account

Identity Security Cloud (ISC) ISC Discussion and Questions
,
1

I am receiving the following error while enabling/disabling the account on a source.

image
image608Ă—266 5.95 KB

There was an error trying to enable the account

An unexpected error occurred: failed to lazily initialize a collection of role: sailpoint.object.Identity.links, could not initialize proxy - no Session

I believe this is the root cause of lifecycle state transaction not going through. Whenever i try to change the lifecycle state, as per the provisioning policy mentioned in identity profiles, it should disable/enable the account. It is not getting triggered. In the account activity i see that the lifecycle state change account activity is pending for ever.

image
image784Ă—673 13.5 KB

2

Hi Nilesh, what kind of account are you trying to initialize?

3

I am trying to enable webservices account.

The issue occurs while I try to manually enable the account or set the lifecycle state to Active.

Regards,

4

Hi Nilesh,
Can you share the screenshot of the configuration done for Disable Account on the Web Service Connector ? Also, have you tested the Disable Operation directly in Postman and it works fine ?

Thanks

5

Yes. the create/disable/enable operations work in Postman. I just now tried to assign a role to a user that should create an account in the source. Got the same error.

image
image883Ă—495 19.1 KB

This was working and suddenly stopped working. Looks like issue with the tenant

6

I too am seeing this below error randomly during access requests which looks more or less similar to yours:

image

And I was not seeing this issue couple of days ago but with the same scenario replicated yesterday, I am seeing this. Any insights would help.

Thanks,
Arshad.

1 Like
7

Is this webservices connector?

8

Yes, this is on webservices connector.

9

This is happenning for Webservices connector and not for other ones. For instance access requests on JDBC connector are working fine

10

I tried recreating the source but no success

11

Same, we tried to clone the source config and re-tried but same issue was observed. We tried to perform a full identity refresh, full system role refresh but no luck. I’m doubtful if this has something to do with issue with Web Services connector behind the scenes.

12

Hi @nileshnikalje,

If you are enabling the account getting the error once do the Account aggregation. The account will be enabled.

Thank you!

13

Here is the latest observation. The account is created in the source. However there is no event generated for Create Account for the identity. This does not trigger “Provisioning completed” event which is used in workflows to send emails. The access request still has the same error.

image
image622Ă—435 12.8 KB

14

Hi,

We also have this issue on our context for different operation (submit request, account creation, disable account).

A ticket has been opened to Sailpoint support.

2 Likes
15

Any update on the ticket?

16

Any update? I have the same issue

17

Please raise a Sailpoint ticket, I raised it two days back. Its been referred to their engineering team. Please mention this topic while raising the ticket to let them know that others are also facing the same issue.

I assume you are getting the same error on Webservices connector.

3 Likes
18

Is this also for Webservices connector?

21

These Lazy Initialization errors are Hibernate errors that were usually caused by an account being decached improperly when they happened in IIQ.

Given that you don’t handle the identity directly in your code, it is likely there is something going on internally that is causing the process to close the session before the identity is done. Do you have a custom Before/After operations on your webservice connector (Assuming this is the DIrect Connector and not SaaS) that you are modifying data?

I would recommend that anyone with this issue create a Support Ticket with SailPoint to get this looked at since it seems to be happening with multiple accounts.

1 Like