HTTP Operations

On the HTTP Operations screen, you can add, edit, delete, and reorder HTTP operations.

The connector supports the following HTTP operations:

  • Test Connection

  • Account Aggregation

  • Account Delta Aggregation

  • Group Aggregation

  • Get Object

  • Get Object-Group

  • Create Account

  • Update Account

  • Delete Account (using a Before provisioning rule)

  • Enable Account

  • Disable Account

  • Unlock Account

  • Change Password

  • Add Entitlement

  • Remove Entitlement

  • Pass-through Authentication

  • Custom Authentication

  • Get Partitions

  • Partitioned Account Aggregation

Note

  • The Web Services source supports the Before Provisioning rule, which enables you to delete an account using a rule. For example, you can change the provisioning plan’s account operation from disable to delete. The UI fields are the same and applicable to all the operations that you choose to configure.

  • For Entitlement Aggregation, you need to configure the schema manually using the SailPoint APIs. Contact SailPoint Support / Expert Services for assistance.

  • For the Web Services source, you can configure the native identity in the provisioning plan using a placeholder such as $plan.planNativeIdentity$.

Support for Cookies

The Web Services source supports cookies for HTTP requests.

The Web Services source supports cookies for multiple endpoints configuration. The source manages the cookies internally for the endpoints configured for the same operation. Cookies from the previous endpoints can be used in all the subsequent endpoints of same operation type.

The Web Services source supports the JSON array as a top element in the HTTP requests.

By default, the Web Services Source supports cookies. Cookies can be disabled by adding the disableCookies attribute key with true as a value. This is not applicable for the authentication API call operation.