Supported Features
The Web Services Source supports the features listed below.
-
Test Connection
-
Account Aggregation
-
Account Delta Aggregation
-
Create, Update, Delete Accounts
Note
Delete Account is possible using a Before Operation rule. For example, you can change the provisioning plan’s account operation from disable to delete. For more information, refer to Web Services Before Operation Rule. -
Enable, Disable Accounts
-
Get Object
-
Entitlement Aggregation
-
Add/ Remove Entitlement
-
Add entitlements when enabling accounts
-
Remove entitlements when disabling accounts
-
Change Password
-
Passthrough Authentication
-
Unlock Account: The schema attribute is Account Lock Status.
-
Authentication: For the Web Services source, credentials are required to connect to the managed system. Following are the supported Authentication Methods:
-
Basic Authentication
-
OAuth2 Authentication
-
API Token (This source does not generate OAuth tokens based on a client ID and client secret key. You need to provide an access token - API token).
-
No/ Custom Authentication
The Web Services Source for the XML format supports the Basic Authentication using username and password.
Note
For the API endpoints with SSL, provide the client certificate details, refer to Client Certificate Authentication. -
-
Supports a rate limit mechanism which handles as prescribed by the IETF implementation. For more information, refer to RateLimit Header Fields for HTTP.
The rate limiting mechanism is engaged after receiving the 429 status code in the response. An exponential back-off depending upon the Retry-After response header occurs before attempting the re-trigger of the request. At maximum, the API request re-trigger is attempted at, twice, after receiving the first 429 response. The URL is encoded regardless of the
throttleEnabled
flag value. -
Multiple Group Objects
The Web Services source supports the multiple group objects. For more information, refer to Multiple Group Objects.
-
Application layer proxy
Important
The Web Services Source manages the request for multiple operations performed sequentially. For more information on features, refer to SailPoint Source Features.