Hi Experts, We are currently experiencing the following issue in our production-sandbox environment. We have attempted to resolve it through Expert Service and CSD, but have not received a satisfactory solution. If anyone has resolved similar issues, your assistance would be greatly appreciated. O…

I think you can do a few things then. 1\ Raise an Idea with SailPoint to improve the connector to have record locking logic implemented out-of-the-box 2\ Try with a sleep time like mentioned above, which may work for 80% of the time… in addition with configuring the retryProvisioning methods like …

I have some more questions for this one… On step 3, what account gets locked? The user’s account or the service account with which you’re provisioning? On step 4, how did they come to a timeout issue? Can you share what’s being sent towards the connector after the access request? (In the event y…

Hi @tysremi In Step 3: 1st request: The interface account (IF_SAILPOINT) locks the target account (권세진) while adding the entitlement. 2nd request: The interface account (IF_SAILPOINT) attempts to add the entitlement but cannot because of the interface lock. This issue continues with subsequent r…

Hi @Anshu_Kunal I already added that option in source configuration. but it doesn’t works. [image]

We have added a delay in a connector rule for a web service connector as below which had similar concurrency issue int numberOfSecondsToSleep = (int)(maxDelayInSeconds * (java.lang.Math.random())); TimeUnit.SECONDS.sleep(numberOfSecondsToSleep); Try above logic in before operation rule (conn…

Ok, I understand. So the “user record” in SAP is in a locked state due to a previous operation and cannot be updated at that time. Including a sleep period somewhere in the process might help, but is not a guarantee as the record might still be locked after your attempts run out. Is this an out-o…

@tysremi I use SAP Direct Connector in this case. Thanks,

@tysremi I agree it should be combination of provisioning retry, delay script and some automated monitoring for any failure to source owner/admin

Are you connectioning to ECC. I would have your SAP security folks turn on trace and trace it… from the message it may be an authorization issue with the service account not the connector itself. We have found the SAP authorization on the service account to be quite tricky to configure… but once w…

Hi @derb , The customer is currently using an S/4HANA database, not ECC. I hadn’t considered whether the service account might have insufficient permissions. However, the account was granted authority equivalent to admin rights, and aside from the user lock issue, I didn’t feel that the service…

Resolving Concurrency Issues with SAP Connector

Identity Security Cloud (ISC) ISC Discussion and Questions

Anshu_Kunal (Anshu Kunal) July 29, 2024, 8:08am 4

@jwshin

Please explore provisioning retry option on your source to capture this error and retry after sometime once object is unlocked.

2 Likes

Topic		Replies	Views
SAP Connectivity Failed ISC Discussion and Questions identity-security-cloud	3	52	February 16, 2026
SAP Direct connector Entitlements are not provisioned when User Account is created on SAP side first IIQ Discussion and Questions identityiq , provisioning	5	128	January 6, 2026
Entra SaaS connector provisioning issue ISC Discussion and Questions identity-security-cloud , connectors	35	822	January 12, 2026
SAP GRC Connector - Access Management integration mode - Sleep interrupted error IIQ Discussion and Questions identityiq	5	281	July 4, 2024
SailPoint is sending same approval multiple times to SAP ISC Discussion and Questions identity-security-cloud , provisioning , access-requests	3	127	July 9, 2024

Resolving Concurrency Issues with SAP Connector

Related topics