Webservices - Provisioning performs GetObject instead of Create

Hi team!

I’m experiencing a strange issue with the Web Services Connector. Provisioning operations were working fine, but now, when I try to perform a ‘Create Account’ operation, the connector performs a ‘Get Object’ operation instead (which fails because the account hasn’t been created yet).

‘CreateAccount’ and ‘GetObject’ are configured as intended:

I also tried deleting both operations. I can see from the events and VA logs that it is still attempting to send a ‘Get Object’ request to the identity.

Do you know why this might be happening?

This might help you to understand the sequencing for the create account operation from the connector documentation.


Where does this document come from?

It would be helpful if you could share the document link or the complete document for reference.

I have ‘createAccountWithEntReq’ set to true in order to add the entitlement in a single create operation. The document says that the Get Object should be triggered after the account creation, but in my case it is being triggered before the creation.

Do you have a link to this document?

This may be useful

https://community.sailpoint.com/t5/IdentityNow-Connectors/Web-Services-Source-Configuration-Reference-Guide/ta-p/78511

Regards
Ankush

Hi @MattUribe

The screen shots are from the connector guide for iiq. Same details are there for the ISC connector as well. https://community.sailpoint.com/t5/IdentityNow-Connectors/Web-Services-Source-Configuration-Reference-Guide/ta-p/78511

Regards
Ankush

1 Like

Hi Ariel, have you already configured ‘Get Object’ to read from a single account? if not then then add try once.

-Ganesh

hi @ArielM even after you delete both the operation if SailPoint is still referring then you have to extract the source once from postman and validate it once. Sometimes the changes done from UI will not take effect. After you see it is deleted validate if your get object operation is working fine by fetching the a single account when you add get object operation first. Then proceed with create account operation.

Hi everyone.

I found what was causing the problem. In the creation provisioning policy, the “usernameGenerator” transform had the ‘sourceCheck’ option set to true. This caused a “getObject” to be sent prior to creation.

The transform was working fine previously, but I guess there was some change in its behavior. By removing that option, the connector now creates accounts normally.

Thanks!

1 Like

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