SAP GRC provisioning failures

[ShashankNoolvi]

Hey Everyone, we’ve been seeing an usual error from long time, whenever there’s term requests or deprovisioning of access for SAP GRC source, we often see the error stated "
[ ConnectorException ] [ Error details ] Field First Name is mandatory".

Any idea why we’d be seeing these, because identity record already hold the value first name and even the GRACUSER table. Besides I think we use user ID to de-provision.

Any inputs on why we’re seeing this or if there’s a way to fix this, are highly appreciated.

Thanks

[ipobeidi (Ivan Obeidi)]

try to affirm in the rule that you’re sending the first name.

That may be it.

[ShashankNoolvi]

At present we don’t have any cloud rules, we’re just totally using the OOTB capabilities. And these errors fix themselves upon retrying manually. It’s a mystery.

Also, do you know if there’s a way to add retriable errors to SAP GRC OOTB connector like how we do to web services connector?

Thanks

[varshini303 (VARSHINI SANKAR)]

Hi @ShashankNoolvi,

Not sure about retryableErrors in SAP GRC, but you can add/ increase numberOfRetries and set retryWaitTime in the source connector attributes.

[ShashankNoolvi]

Hi @varshini303 , thanks for your input. I did see that before however I wasn’t sure if it retries time out errors as well because from what I saw on the documentation it seemed like its mainly for errors stating “Invalid request no”

Please confirm if these can fix timeout errors as well. And thanks again for your response

[varshini303 (VARSHINI SANKAR)]

Specifying this should/will start polling for any retries as described in the document (including provisioning timeout errors hopefully) more than just addressing the “Invalid request no” problem.

Thanks!