What is the significance of getObject operation in a Webservice Application

Hi all,

What is the significance of getObject operation in a Webservice Application? Can I perform a create operation on a Web service app without the getObject operation?

Thanks in advance.

1 Like

GetObject operation is used as a validator.

I think it is essential to add the GetObject operation for the web service connector.

The getObject operation is used as a target aggregation to pull info about one record. This is can be called in several account operations (create, enable, disable) if configured.

It’s not explicitly required, however if the target system supports it would recommend configuring it. Link to the docs for more info here

1 Like

get object is kind of single account aggregation, if you request anything and to verify teh request , if get object is configured , perform identity maintannece task call this operation and verify the request and make it as completed.Otherwise , the request will be waited for next account aggregation to be run to verify the request.So best approach is to have get obejct operation to verify the request sytematically.

The Simple technical Answer for your query is yes, You can perform a create operation on a webservice app without the get object operation.

The getobject operation is configured basically to check a single user, if you want to check if the user exists at target application, before you perform a create/modify operation.

use case could be, there could be scenario, where user account was created at the target directly, and it was not aggregated back in sailpoint. So when the user raised the request, it will be treated as create but it should be modify, and the provisioning failed due to this . When you have this operation configured, you can write a before provisioning rule and call the getobject to check if the user exist and switch operation.

1 Like