Additional Settings

Additional Settings has options for provisioning and common configuration for HTTP errors.

Provisioning Settings

The Web Services SaaS connector supports the following provisioning features.

  • Create Account With "Ent" Request

    The Create Account operation executes with entitlement attributes. If the Create Account operation response contains the required attributes, including the identity attribute, the account object is created and the account link displays under the identity from whom the account creation was triggered.

  • Update Attributes with Change Password

    Include a password change and an attribute change in a single request. The Change Password operation is used for changing the password on the managed system. If the provisioning plan contains no attribute request with the name "password", the update operation type endpoint is invoked. Enabling this attribute does not include requests for add or remove entitlement operations. Those requests are executed independently.

  • Add or Remove Entitlements in a Single Request

    Enable Add or Remove Entitlements in a Single Request to send multiple entitlement requests at once to the managed system as opposed to separately.

  • Skip getObject Call during Create Provisioning

    Enable Skip getObject Call during Create Provisioning to skip the getObject call during initial object creation in provisioning operations.

Common Configurations for Errors

Configure the following common Web Services settings:

HTTP Errors

You can manually configure HTTP error codes and messages for times when an API endpoint in the Web Services source sends unexpected error codes to flag failure conditions. Manually configuring these codes enables the connector to properly handle them. Configure the source with all possible HTTP error codes and messages that the API endpoint may return. Enter the HTTP Error Keys and their respective HTTP Enter Values. This is not applicable to the child endpoints.

Note
For error codes add errorCodes as HTTP Error Keys, and for error messages add errorMessages as HTTP Error .

For example:

  • The Web Services source returns the HTTP status code: 200, but the response payload contains an error. Without the manually entered HTTP error, the source won't know that it must fail the request.

  • During OAuth token generation, the source needs to regenerate a token to replace an invalid or expired token. You can configure an HTTP error code or message to specify an invalid/expiry token error in this event. The source regenerates and saves the token for OAuth2 authentication, then retries the operation with the newly generated access token.

Object Not Found Error Messages

Enter the error message that the connector displays when it can't find objects or fails to make connections.

For example:

404 - Object Not Found

Disable Cookies – The Web Services SaaS source can disable cookies while executing HTTP requests. You can disable cookies for all the operations performed except for the authentication API.