Use this API to implement and customize source functionality.
With source functionality in place, organizations can use Identity Security Cloud to connect their various sources and user data sets and manage access across all those different sources in a secure, scalable way.
Sources refer to the Identity Security Cloud representations for external applications, databases, and directory management systems that maintain their own sets of users, like Dropbox, GitHub, and Workday, for example.
Organizations may use hundreds, if not thousands, of different source systems, and any one employee within an organization likely has a different user record on each source, often with different permissions on many of those records.
Connecting these sources to Identity Security Cloud makes it possible to manage user access across them all.
Then, if a new hire starts at an organization, Identity Security Cloud can grant the new hire access to all the sources they need.
If an employee moves to a new department and needs access to new sources but no longer needs access to others, Identity Security Cloud can grant the necessary access and revoke the unnecessary access for all the employee's various sources.
If an employee leaves the company, Identity Security Cloud can revoke access to all the employee's various source accounts immediately.
These are just a few examples of the many ways that source functionality makes identity governance easier, more efficient, and more secure.
In Identity Security Cloud, administrators can create configure, manage, and edit sources, and they can designate other users as source admins to be able to do so.
They can also designate users as source sub-admins, who can perform the same source actions but only on sources associated with their governance groups.
Admins go to Connections > Sources to see a list of the existing source representations in their organizations.
They can create new sources or select existing ones.
To create a new source, the following must be specified: Source Name, Description, Source Owner, and Connection Type.
Refer to Configuring a Source for more information about the source configuration process.
Identity Security Cloud connects with its sources either by a direct communication with the source server (connection information specific to the source must be provided) or a flat file feed, a CSV file containing all the relevant information about the accounts to be loaded in.
Different sources use different connectors to share data with Identity Security Cloud, and each connector's setup process is specific to that connector.
SailPoint has built a number of connectors to come out of the box and connect to the most common sources, and SailPoint actively maintains these connectors.
Refer to Identity Security Cloud Connectors for more information about these SailPoint supported connectors.
Refer to the following links for more information about two useful connectors:
JDBC Connector: This customizable connector an directly connect to databases that support JDBC (Java Database Connectivity).
Web Services Connector: This connector can directly connect to databases that support Web Services.
Refer to SaaS Connectivity for more information about SailPoint's new connectivity framework that makes it easy to build and manage custom connectors to SaaS sources.
When admins select existing sources, they can view the following information about the source:
Associated connections (any associated identity profiles, apps, or references to the source in a transform).
Associated user accounts. These accounts are linked to their identities - this provides a more complete picture of each user's access across sources.
Associated entitlements (sets of access rights on sources).
Associated access profiles (groupings of entitlements).
The user account data and the entitlements update with each data aggregation from the source.
Organizations generally run scheduled, automated data aggregations to ensure that their data is always in sync between their sources and their Identity Security Cloud tenants so an access change on a source is detected quickly in Identity Security Cloud.
Admins can view a history of these aggregations, and they can also run manual imports.
Refer to Loading Account Data for more information about manual and scheduled aggregations.
Admins can also make changes to determine which user account data Identity Security Cloud collects from the source and how it correlates that account data with identity data.
To define which account attributes the source shares with Identity Security Cloud, admins can edit the account schema on the source.
Refer to Managing Source Account Schemas for more information about source account schemas and how to edit them.
To define the mapping between the source account attributes and their correlating identity attributes, admins can edit the correlation configuration on the source.
Refer to Assigning Source Accounts to Identities for more information about this correlation process between source accounts and identities.
Admins can also delete sources, but they must first ensure that the sources no longer have any active connections: the source must not be associated with any identity profile or any app, and it must not be referenced by any transform.
Refer to Deleting Sources for more information about deleting sources.
Well organized, mapped out connections between sources and Identity Security Cloud are essential to achieving comprehensive identity access governance across all the source systems organizations need.
Refer to Managing Sources for more information about all the different things admins can do with sources once they are connected.
This API generates a create policy/template based on field value transforms. This API is intended for use when setting up JDBC Provisioning type sources, but it will also work on other source types.
Transforms can be used in the provisioning policy to create a new attribute that you only need during provisioning.
Refer to Transforms in Provisioning Policies for more information.
Client Error - Returned if the request body is invalid.
ErrorResponseDto
401
Unauthorized - Returned if there is no authorization header, or if the JWT token is expired.
ListAccessProfiles401Response
403
Forbidden - Returned if the user you are running as, doesn't have access to this end-point.
ErrorResponseDto
404
Not Found - returned if the request URL refers to a resource or object that does not exist
ErrorResponseDto
429
Too Many Requests - Returned in response to too many requests in a given period of time - rate limited. The Retry-After header in the response includes how long to wait before trying again.
ListAccessProfiles429Response
500
Internal Server Error - Returned if there is an unexpected error.
This creates a specific source with a full source JSON representation. Any passwords are submitted as plain-text and encrypted upon receipt in IdentityNow.
If this parameter is true, it configures the source as a Delimited File (CSV) source. Setting this to true will automatically set the type of the source to DelimitedFile. You must use this query parameter to create a Delimited File source as you would in the UI. If you don't set this query parameter and you attempt to set the type attribute directly, the request won't correctly generate the source.
Created Source object. Any passwords will only show the the encrypted cipher-text, as they are not decrypt-able in IdentityNow cloud-based services, per IdentityNow security design.
Source
400
Client Error - Returned if the request body is invalid.
ErrorResponseDto
401
Unauthorized - Returned if there is no authorization header, or if the JWT token is expired.
ListAccessProfiles401Response
403
Forbidden - Returned if the user you are running as, doesn't have access to this end-point.
ErrorResponseDto
429
Too Many Requests - Returned in response to too many requests in a given period of time - rate limited. The Retry-After header in the response includes how long to wait before trying again.
ListAccessProfiles429Response
500
Internal Server Error - Returned if there is an unexpected error.
ErrorResponseDto
HTTP request headers
Content-Type: application/json
Accept: application/json
Example
$Source=@"{
"cluster" : {
"name" : "CorporateCluster",
"id" : "2c9180866166b5b0016167c32ef31a66",
"type" : "CLUSTER"
},
"deleteThreshold" : 10,
"connectorId" : "active-directory",
"description" : "Thisisthecorporatedirectory.",
"type" : "OpenLDAP-Direct",
"connectorClass" : "sailpoint.connector.LDAPConnector",
"connectionType" : "file",
"features" : [ "PROVISIONING", "NO_PERMISSIONS_PROVISIONING", "GROUPS_HAVE_MEMBERS" ],
"passwordPolicies" : [ {
"type" : "PASSWORD_POLICY",
"id" : "2c9180855d191c59015d291ceb053980",
"name" : "CorporatePasswordPolicy"
}, {
"type" : "PASSWORD_POLICY",
"id" : "2c9180855d191c59015d291ceb057777",
"name" : "VendorPasswordPolicy"
} ],
"modified" : "2024-01-23T18:08:50.897Z",
"id" : "2c91808568c529c60168cca6f90c1324",
"connectorImplementationId" : "delimited-file",
"managerCorrelationRule" : {
"name" : "ExampleRule",
"id" : "2c918085708c274401708c2a8a760001",
"type" : "RULE"
},
"owner" : {
"name" : "MyName",
"id" : "2c91808568c529c60168cca6f90c1313",
"type" : "IDENTITY"
},
"managementWorkgroup" : {
"name" : "MyManagementWorkgroup",
"id" : "2c91808568c529c60168cca6f90c2222",
"type" : "GOVERNANCE_GROUP"
},
"accountCorrelationRule" : {
"name" : "ExampleRule",
"id" : "2c918085708c274401708c2a8a760001",
"type" : "RULE"
},
"authoritative" : false,
"connectorAttributes" : {
"healthCheckTimeout" : 30,
"authSearchAttributes" : [ "cn", "uid", "mail" ]
},
"created" : "2022-02-08T14:50:03.827Z",
"managerCorrelationMapping" : {
"accountAttributeName" : "manager",
"identityAttributeName" : "manager"
},
"credentialProviderEnabled" : false,
"accountCorrelationConfig" : {
"name" : "Directory[source-62867]AccountCorrelation",
"id" : "2c9180855d191c59015d28583727245a",
"type" : "ACCOUNT_CORRELATION_CONFIG"
},
"connector" : "active-directory",
"healthy" : true,
"schemas" : [ {
"type" : "CONNECTOR_SCHEMA",
"id" : "2c9180835d191a86015d28455b4b232a",
"name" : "account"
}, {
"type" : "CONNECTOR_SCHEMA",
"id" : "2c9180835d191a86015d28455b4b232b",
"name" : "group"
} ],
"name" : "MySource",
"connectorName" : "ActiveDirectory",
"category" : "CredentialProvider",
"beforeProvisioningRule" : {
"name" : "ExampleRule",
"id" : "2c918085708c274401708c2a8a760001",
"type" : "RULE"
},
"status" : "SOURCE_STATE_HEALTHY",
"since" : "2021-09-28T15:48:29.3801666300Z"
}"@$ProvisionAsCsv=$false# Boolean | If this parameter is `true`, it configures the source as a Delimited File (CSV) source. Setting this to `true` will automatically set the `type` of the source to `DelimitedFile`. You must use this query parameter to create a Delimited File source as you would in the UI. If you don't set this query parameter and you attempt to set the `type` attribute directly, the request won't correctly generate the source. (optional)# Creates a source in IdentityNow.try{$Result=ConvertFrom-JsonToSource-Json$SourceNew-V2024Source-V2024Source$Result# Below is a request that includes all optional parameters# New-V2024Source -V2024Source $Source -V2024ProvisionAsCsv $ProvisionAsCsv }catch{Write-Host$_.Exception.Response.StatusCode.value__"Exception occurred when calling New-V2024Source"Write-Host$_.ErrorDetails}
The schedule was successfully created on the specified source.
Schedule1
400
Client Error - Returned if the request body is invalid.
ErrorResponseDto
401
Unauthorized - Returned if there is no authorization header, or if the JWT token is expired.
ListAccessProfiles401Response
403
Forbidden - Returned if the user you are running as, doesn't have access to this end-point.
ErrorResponseDto
429
Too Many Requests - Returned in response to too many requests in a given period of time - rate limited. The Retry-After header in the response includes how long to wait before trying again.
ListAccessProfiles429Response
500
Internal Server Error - Returned if there is an unexpected error.
ErrorResponseDto
HTTP request headers
Content-Type: application/json
Accept: application/json
Example
$SourceId="2c9180835d191a86015d28455b4a2329"# String | Source ID.$Schedule1=@""@# Create Schedule on Sourcetry{$Result=ConvertFrom-JsonToSchedule1-Json$Schedule1New-V2024SourceSchedule-V2024SourceId$SourceId-V2024Schedule1$Result# Below is a request that includes all optional parameters# New-V2024SourceSchedule -V2024SourceId $SourceId -V2024Schedule1 $Schedule1 }catch{Write-Host$_.Exception.Response.StatusCode.value__"Exception occurred when calling New-V2024SourceSchedule"Write-Host$_.ErrorDetails}
The schema was successfully created on the specified source.
Schema
400
Client Error - Returned if the request body is invalid.
ErrorResponseDto
401
Unauthorized - Returned if there is no authorization header, or if the JWT token is expired.
ListAccessProfiles401Response
403
Forbidden - Returned if the user you are running as, doesn't have access to this end-point.
ErrorResponseDto
429
Too Many Requests - Returned in response to too many requests in a given period of time - rate limited. The Retry-After header in the response includes how long to wait before trying again.
ListAccessProfiles429Response
500
Internal Server Error - Returned if there is an unexpected error.
Use this endpoint to remove all accounts from the system without provisioning changes to the source. Accounts that are removed could be re-created during the next aggregation.
This endpoint is good for:
Removing accounts that no longer exist on the source.
Removing accounts that won't be aggregated following updates to the source configuration.
Forcing accounts to be re-created following the next aggregation to re-run account processing, support testing, etc.
Accepted. Returns task result details of removal request.
TaskResultDto
400
Client Error - Returned if the request body is invalid.
ErrorResponseDto
401
Unauthorized - Returned if there is no authorization header, or if the JWT token is expired.
ListAccessProfiles401Response
403
Forbidden - Returned if the user you are running as, doesn't have access to this end-point.
ErrorResponseDto
429
Too Many Requests - Returned in response to too many requests in a given period of time - rate limited. The Retry-After header in the response includes how long to wait before trying again.
ListAccessProfiles429Response
500
Internal Server Error - Returned if there is an unexpected error.
ErrorResponseDto
HTTP request headers
Content-Type: Not defined
Accept: application/json
Example
$Id="ebbf35756e1140699ce52b233121384a"# String | The source id$XSailPointExperimental="true"# String | Use this header to enable this experimental API. (default to "true")# Remove All Accounts in a Sourcetry{Remove-V2024AccountsAsync-V2024Id$Id-V2024XSailPointExperimental$XSailPointExperimental# Below is a request that includes all optional parameters# Remove-V2024AccountsAsync -V2024Id $Id -V2024XSailPointExperimental $XSailPointExperimental }catch{Write-Host$_.Exception.Response.StatusCode.value__"Exception occurred when calling Remove-V2024AccountsAsync"Write-Host$_.ErrorDetails}
Deletes the native change detection configuration for the source specified by the given ID.
Parameters
Param Type
Name
Data Type
Required
Description
Path
Id
String
True
The source id
XSailPointExperimental
String
True (default to "true")
Use this header to enable this experimental API.
Return type
(empty response body)
Responses
Code
Description
Data Type
204
No content - indicates the request was successful but there is no content to be returned in the response.
400
Client Error - Returned if the request body is invalid.
ErrorResponseDto
401
Unauthorized - Returned if there is no authorization header, or if the JWT token is expired.
ListAccessProfiles401Response
403
Forbidden - Returned if the user you are running as, doesn't have access to this end-point.
ErrorResponseDto
404
Not Found - returned if the request URL refers to a resource or object that does not exist
ErrorResponseDto
429
Too Many Requests - Returned in response to too many requests in a given period of time - rate limited. The Retry-After header in the response includes how long to wait before trying again.
ListAccessProfiles429Response
500
Internal Server Error - Returned if there is an unexpected error.
ErrorResponseDto
HTTP request headers
Content-Type: Not defined
Accept: application/json
Example
$Id="2c9180835d191a86015d28455b4a2329"# String | The source id$XSailPointExperimental="true"# String | Use this header to enable this experimental API. (default to "true")# Delete Native Change Detection Configurationtry{Remove-V2024NativeChangeDetectionConfig-V2024Id$Id-V2024XSailPointExperimental$XSailPointExperimental# Below is a request that includes all optional parameters# Remove-V2024NativeChangeDetectionConfig -V2024Id $Id -V2024XSailPointExperimental $XSailPointExperimental }catch{Write-Host$_.Exception.Response.StatusCode.value__"Exception occurred when calling Remove-V2024NativeChangeDetectionConfig"Write-Host$_.ErrorDetails}
The type of provisioning policy usage. In IdentityNow, a source can support various provisioning operations. For example, when a joiner is added to a source, this may trigger both CREATE and UPDATE provisioning operations. Each usage type is considered a provisioning policy. A source can have any number of these provisioning policies defined. These are the common usage types: CREATE - This usage type relates to 'Create Account Profile', the provisioning template for the account to be created. For example, this would be used for a joiner on a source. UPDATE - This usage type relates to 'Update Account Profile', the provisioning template for the 'Update' connector operations. For example, this would be used for an attribute sync on a source. ENABLE - This usage type relates to 'Enable Account Profile', the provisioning template for the account to be enabled. For example, this could be used for a joiner on a source once the joiner's account is created. DISABLE - This usage type relates to 'Disable Account Profile', the provisioning template for the account to be disabled. For example, this could be used when a leaver is removed temporarily from a source. You can use these four usage types for all your provisioning policy needs.
Return type
(empty response body)
Responses
Code
Description
Data Type
204
No content - indicates the request was successful but there is no content to be returned in the response.
400
Client Error - Returned if the request body is invalid.
ErrorResponseDto
401
Unauthorized - Returned if there is no authorization header, or if the JWT token is expired.
ListAccessProfiles401Response
403
Forbidden - Returned if the user you are running as, doesn't have access to this end-point.
ErrorResponseDto
404
Not Found - returned if the request URL refers to a resource or object that does not exist
ErrorResponseDto
429
Too Many Requests - Returned in response to too many requests in a given period of time - rate limited. The Retry-After header in the response includes how long to wait before trying again.
ListAccessProfiles429Response
500
Internal Server Error - Returned if there is an unexpected error.
ErrorResponseDto
HTTP request headers
Content-Type: Not defined
Accept: application/json
Example
$SourceId="2c9180835d191a86015d28455b4a2329"# String | The Source ID.$UsageType="CREATE"# UsageType | The type of provisioning policy usage. In IdentityNow, a source can support various provisioning operations. For example, when a joiner is added to a source, this may trigger both CREATE and UPDATE provisioning operations. Each usage type is considered a provisioning policy. A source can have any number of these provisioning policies defined. These are the common usage types: CREATE - This usage type relates to 'Create Account Profile', the provisioning template for the account to be created. For example, this would be used for a joiner on a source. UPDATE - This usage type relates to 'Update Account Profile', the provisioning template for the 'Update' connector operations. For example, this would be used for an attribute sync on a source. ENABLE - This usage type relates to 'Enable Account Profile', the provisioning template for the account to be enabled. For example, this could be used for a joiner on a source once the joiner's account is created. DISABLE - This usage type relates to 'Disable Account Profile', the provisioning template for the account to be disabled. For example, this could be used when a leaver is removed temporarily from a source. You can use these four usage types for all your provisioning policy needs. # Delete Provisioning Policy by UsageTypetry{Remove-V2024ProvisioningPolicy-V2024SourceId$SourceId-V2024UsageType$UsageType# Below is a request that includes all optional parameters# Remove-V2024ProvisioningPolicy -V2024SourceId $SourceId -V2024UsageType $UsageType }catch{Write-Host$_.Exception.Response.StatusCode.value__"Exception occurred when calling Remove-V2024ProvisioningPolicy"Write-Host$_.ErrorDetails}
Use this API to delete a specific source in Identity Security Cloud (ISC).
The API removes all the accounts on the source first, and then it deletes the source. You can retrieve the actual task execution status with this method: GET /task-status/{id}
Accepted - Returned if the request was successfully accepted into the system.
DeleteSource202Response
400
Client Error - Returned if the request body is invalid.
ErrorResponseDto
401
Unauthorized - Returned if there is no authorization header, or if the JWT token is expired.
ListAccessProfiles401Response
403
Forbidden - Returned if the user you are running as, doesn't have access to this end-point.
ErrorResponseDto
404
Not Found - returned if the request URL refers to a resource or object that does not exist
ErrorResponseDto
429
Too Many Requests - Returned in response to too many requests in a given period of time - rate limited. The Retry-After header in the response includes how long to wait before trying again.
ListAccessProfiles429Response
500
Internal Server Error - Returned if there is an unexpected error.
ErrorResponseDto
HTTP request headers
Content-Type: Not defined
Accept: application/json
Example
$Id="2c9180835d191a86015d28455b4a2329"# String | Source ID.# Delete Source by IDtry{Remove-V2024Source-V2024Id$Id# Below is a request that includes all optional parameters# Remove-V2024Source -V2024Id $Id }catch{Write-Host$_.Exception.Response.StatusCode.value__"Exception occurred when calling Remove-V2024Source"Write-Host$_.ErrorDetails}
No content - indicates the request was successful but there is no content to be returned in the response.
400
Client Error - Returned if the request body is invalid.
ErrorResponseDto
401
Unauthorized - Returned if there is no authorization header, or if the JWT token is expired.
ListAccessProfiles401Response
403
Forbidden - Returned if the user you are running as, doesn't have access to this end-point.
ErrorResponseDto
404
Not Found - returned if the request URL refers to a resource or object that does not exist
ErrorResponseDto
429
Too Many Requests - Returned in response to too many requests in a given period of time - rate limited. The Retry-After header in the response includes how long to wait before trying again.
ListAccessProfiles429Response
500
Internal Server Error - Returned if there is an unexpected error.
ErrorResponseDto
HTTP request headers
Content-Type: Not defined
Accept: application/json
Example
$SourceId="2c9180835d191a86015d28455b4a2329"# String | The Source id.$ScheduleType="ACCOUNT_AGGREGATION"# String | The Schedule type.# Delete Source Schedule by type.try{Remove-V2024SourceSchedule-V2024SourceId$SourceId-V2024ScheduleType$ScheduleType# Below is a request that includes all optional parameters# Remove-V2024SourceSchedule -V2024SourceId $SourceId -V2024ScheduleType $ScheduleType }catch{Write-Host$_.Exception.Response.StatusCode.value__"Exception occurred when calling Remove-V2024SourceSchedule"Write-Host$_.ErrorDetails}
No content - indicates the request was successful but there is no content to be returned in the response.
400
Client Error - Returned if the request body is invalid.
ErrorResponseDto
401
Unauthorized - Returned if there is no authorization header, or if the JWT token is expired.
ListAccessProfiles401Response
403
Forbidden - Returned if the user you are running as, doesn't have access to this end-point.
ErrorResponseDto
404
Not Found - returned if the request URL refers to a resource or object that does not exist
ErrorResponseDto
429
Too Many Requests - Returned in response to too many requests in a given period of time - rate limited. The Retry-After header in the response includes how long to wait before trying again.
ListAccessProfiles429Response
500
Internal Server Error - Returned if there is an unexpected error.
ErrorResponseDto
HTTP request headers
Content-Type: Not defined
Accept: application/json
Example
$SourceId="2c9180835d191a86015d28455b4a2329"# String | The Source id.$SchemaId="2c9180835d191a86015d28455b4a2329"# String | The Schema id.# Delete Source Schema by IDtry{Remove-V2024SourceSchema-V2024SourceId$SourceId-V2024SchemaId$SchemaId# Below is a request that includes all optional parameters# Remove-V2024SourceSchema -V2024SourceId $SourceId -V2024SchemaId $SchemaId }catch{Write-Host$_.Exception.Response.StatusCode.value__"Exception occurred when calling Remove-V2024SourceSchema"Write-Host$_.ErrorDetails}
This API downloads the CSV schema that defines the account attributes on a source.
NOTE: This API is designated only for Delimited File sources.
Parameters
Param Type
Name
Data Type
Required
Description
Path
Id
String
True
The Source id
Return type
(empty response body)
Responses
Code
Description
Data Type
200
Successfully downloaded the file
400
Client Error - Returned if the request body is invalid.
ErrorResponseDto
401
Unauthorized - Returned if there is no authorization header, or if the JWT token is expired.
ListAccessProfiles401Response
403
Forbidden - Returned if the user you are running as, doesn't have access to this end-point.
ErrorResponseDto
404
Not Found - returned if the request URL refers to a resource or object that does not exist
ErrorResponseDto
429
Too Many Requests - Returned in response to too many requests in a given period of time - rate limited. The Retry-After header in the response includes how long to wait before trying again.
ListAccessProfiles429Response
500
Internal Server Error - Returned if there is an unexpected error.
ErrorResponseDto
HTTP request headers
Content-Type: Not defined
Accept: text/csv, application/json
Example
$Id="8c190e6787aa4ed9a90bd9d5344523fb"# String | The Source id# Downloads source accounts schema templatetry{Get-V2024AccountsSchema-V2024Id$Id# Below is a request that includes all optional parameters# Get-V2024AccountsSchema -V2024Id $Id }catch{Write-Host$_.Exception.Response.StatusCode.value__"Exception occurred when calling Get-V2024AccountsSchema"Write-Host$_.ErrorDetails}
Client Error - Returned if the request body is invalid.
ErrorResponseDto
401
Unauthorized - Returned if there is no authorization header, or if the JWT token is expired.
ListAccessProfiles401Response
403
Forbidden - Returned if the user you are running as, doesn't have access to this end-point.
ErrorResponseDto
404
Not Found - returned if the request URL refers to a resource or object that does not exist
ErrorResponseDto
429
Too Many Requests - Returned in response to too many requests in a given period of time - rate limited. The Retry-After header in the response includes how long to wait before trying again.
ListAccessProfiles429Response
500
Internal Server Error - Returned if there is an unexpected error.
ErrorResponseDto
HTTP request headers
Content-Type: Not defined
Accept: application/json
Example
$Id="2c9180835d191a86015d28455b4a2329"# String | The source id# Get Source Correlation Configurationtry{Get-V2024CorrelationConfig-V2024Id$Id# Below is a request that includes all optional parameters# Get-V2024CorrelationConfig -V2024Id $Id }catch{Write-Host$_.Exception.Response.StatusCode.value__"Exception occurred when calling Get-V2024CorrelationConfig"Write-Host$_.ErrorDetails}
This API downloads the CSV schema that defines the entitlement attributes on a source.
NOTE: This API is designated only for Delimited File sources.
Parameters
Param Type
Name
Data Type
Required
Description
Path
Id
String
True
The Source id
Query
SchemaName
String
(optional)
Name of entitlement schema
Return type
(empty response body)
Responses
Code
Description
Data Type
200
Successfully downloaded the file
400
Client Error - Returned if the request body is invalid.
ErrorResponseDto
401
Unauthorized - Returned if there is no authorization header, or if the JWT token is expired.
ListAccessProfiles401Response
403
Forbidden - Returned if the user you are running as, doesn't have access to this end-point.
ErrorResponseDto
404
Not Found - returned if the request URL refers to a resource or object that does not exist
ErrorResponseDto
429
Too Many Requests - Returned in response to too many requests in a given period of time - rate limited. The Retry-After header in the response includes how long to wait before trying again.
ListAccessProfiles429Response
500
Internal Server Error - Returned if there is an unexpected error.
ErrorResponseDto
HTTP request headers
Content-Type: Not defined
Accept: text/csv, application/json
Example
$Id="8c190e6787aa4ed9a90bd9d5344523fb"# String | The Source id$SchemaName="?schemaName=group"# String | Name of entitlement schema (optional)# Downloads source entitlements schema templatetry{Get-V2024EntitlementsSchema-V2024Id$Id# Below is a request that includes all optional parameters# Get-V2024EntitlementsSchema -V2024Id $Id -V2024SchemaName $SchemaName }catch{Write-Host$_.Exception.Response.StatusCode.value__"Exception occurred when calling Get-V2024EntitlementsSchema"Write-Host$_.ErrorDetails}
Native change detection configuration for a source
NativeChangeDetectionConfig
400
Client Error - Returned if the request body is invalid.
ErrorResponseDto
401
Unauthorized - Returned if there is no authorization header, or if the JWT token is expired.
ListAccessProfiles401Response
403
Forbidden - Returned if the user you are running as, doesn't have access to this end-point.
ErrorResponseDto
404
Not Found - returned if the request URL refers to a resource or object that does not exist
ErrorResponseDto
429
Too Many Requests - Returned in response to too many requests in a given period of time - rate limited. The Retry-After header in the response includes how long to wait before trying again.
ListAccessProfiles429Response
500
Internal Server Error - Returned if there is an unexpected error.
ErrorResponseDto
HTTP request headers
Content-Type: Not defined
Accept: application/json
Example
$Id="2c9180835d191a86015d28455b4a2329"# String | The source id$XSailPointExperimental="true"# String | Use this header to enable this experimental API. (default to "true")# Native Change Detection Configurationtry{Get-V2024NativeChangeDetectionConfig-V2024Id$Id-V2024XSailPointExperimental$XSailPointExperimental# Below is a request that includes all optional parameters# Get-V2024NativeChangeDetectionConfig -V2024Id $Id -V2024XSailPointExperimental $XSailPointExperimental }catch{Write-Host$_.Exception.Response.StatusCode.value__"Exception occurred when calling Get-V2024NativeChangeDetectionConfig"Write-Host$_.ErrorDetails}
The type of provisioning policy usage. In IdentityNow, a source can support various provisioning operations. For example, when a joiner is added to a source, this may trigger both CREATE and UPDATE provisioning operations. Each usage type is considered a provisioning policy. A source can have any number of these provisioning policies defined. These are the common usage types: CREATE - This usage type relates to 'Create Account Profile', the provisioning template for the account to be created. For example, this would be used for a joiner on a source. UPDATE - This usage type relates to 'Update Account Profile', the provisioning template for the 'Update' connector operations. For example, this would be used for an attribute sync on a source. ENABLE - This usage type relates to 'Enable Account Profile', the provisioning template for the account to be enabled. For example, this could be used for a joiner on a source once the joiner's account is created. DISABLE - This usage type relates to 'Disable Account Profile', the provisioning template for the account to be disabled. For example, this could be used when a leaver is removed temporarily from a source. You can use these four usage types for all your provisioning policy needs.
The requested ProvisioningPolicyDto was successfully retrieved.
ProvisioningPolicyDto
400
Client Error - Returned if the request body is invalid.
ErrorResponseDto
401
Unauthorized - Returned if there is no authorization header, or if the JWT token is expired.
ListAccessProfiles401Response
403
Forbidden - Returned if the user you are running as, doesn't have access to this end-point.
ErrorResponseDto
404
Not Found - returned if the request URL refers to a resource or object that does not exist
ErrorResponseDto
429
Too Many Requests - Returned in response to too many requests in a given period of time - rate limited. The Retry-After header in the response includes how long to wait before trying again.
ListAccessProfiles429Response
500
Internal Server Error - Returned if there is an unexpected error.
ErrorResponseDto
HTTP request headers
Content-Type: Not defined
Accept: application/json
Example
$SourceId="2c9180835d191a86015d28455b4a2329"# String | The Source ID.$UsageType="CREATE"# UsageType | The type of provisioning policy usage. In IdentityNow, a source can support various provisioning operations. For example, when a joiner is added to a source, this may trigger both CREATE and UPDATE provisioning operations. Each usage type is considered a provisioning policy. A source can have any number of these provisioning policies defined. These are the common usage types: CREATE - This usage type relates to 'Create Account Profile', the provisioning template for the account to be created. For example, this would be used for a joiner on a source. UPDATE - This usage type relates to 'Update Account Profile', the provisioning template for the 'Update' connector operations. For example, this would be used for an attribute sync on a source. ENABLE - This usage type relates to 'Enable Account Profile', the provisioning template for the account to be enabled. For example, this could be used for a joiner on a source once the joiner's account is created. DISABLE - This usage type relates to 'Disable Account Profile', the provisioning template for the account to be disabled. For example, this could be used when a leaver is removed temporarily from a source. You can use these four usage types for all your provisioning policy needs. # Get Provisioning Policy by UsageTypetry{Get-V2024ProvisioningPolicy-V2024SourceId$SourceId-V2024UsageType$UsageType# Below is a request that includes all optional parameters# Get-V2024ProvisioningPolicy -V2024SourceId $SourceId -V2024UsageType $UsageType }catch{Write-Host$_.Exception.Response.StatusCode.value__"Exception occurred when calling Get-V2024ProvisioningPolicy"Write-Host$_.ErrorDetails}
Client Error - Returned if the request body is invalid.
ErrorResponseDto
401
Unauthorized - Returned if there is no authorization header, or if the JWT token is expired.
ListAccessProfiles401Response
403
Forbidden - Returned if the user you are running as, doesn't have access to this end-point.
ErrorResponseDto
404
Not Found - returned if the request URL refers to a resource or object that does not exist
ErrorResponseDto
429
Too Many Requests - Returned in response to too many requests in a given period of time - rate limited. The Retry-After header in the response includes how long to wait before trying again.
ListAccessProfiles429Response
500
Internal Server Error - Returned if there is an unexpected error.
ErrorResponseDto
HTTP request headers
Content-Type: Not defined
Accept: application/json
Example
$Id="2c9180835d191a86015d28455b4a2329"# String | Source ID.# Get Source by IDtry{Get-V2024Source-V2024Id$Id# Below is a request that includes all optional parameters# Get-V2024Source -V2024Id $Id }catch{Write-Host$_.Exception.Response.StatusCode.value__"Exception occurred when calling Get-V2024Source"Write-Host$_.ErrorDetails}
This API returns the existing attribute synchronization configuration for a source specified by the given ID. The response contains all attributes, regardless of whether they enabled or not.
Attribute synchronization configuration for a source
AttrSyncSourceConfig
400
Client Error - Returned if the request body is invalid.
ErrorResponseDto
401
Unauthorized - Returned if there is no authorization header, or if the JWT token is expired.
ListAccessProfiles401Response
403
Forbidden - Returned if the user you are running as, doesn't have access to this end-point.
ErrorResponseDto
404
Not Found - returned if the request URL refers to a resource or object that does not exist
ErrorResponseDto
429
Too Many Requests - Returned in response to too many requests in a given period of time - rate limited. The Retry-After header in the response includes how long to wait before trying again.
ListAccessProfiles429Response
500
Internal Server Error - Returned if there is an unexpected error.
ErrorResponseDto
HTTP request headers
Content-Type: Not defined
Accept: application/json
Example
$Id="2c9180835d191a86015d28455b4a2329"# String | The source id$XSailPointExperimental="true"# String | Use this header to enable this experimental API. (default to "true")# Attribute Sync Configtry{Get-V2024SourceAttrSyncConfig-V2024Id$Id-V2024XSailPointExperimental$XSailPointExperimental# Below is a request that includes all optional parameters# Get-V2024SourceAttrSyncConfig -V2024Id $Id -V2024XSailPointExperimental $XSailPointExperimental }catch{Write-Host$_.Exception.Response.StatusCode.value__"Exception occurred when calling Get-V2024SourceAttrSyncConfig"Write-Host$_.ErrorDetails}
Unauthorized - Returned if there is no authorization header, or if the JWT token is expired.
ListAccessProfiles401Response
403
Forbidden - Returned if the user you are running as, doesn't have access to this end-point.
ErrorResponseDto
404
Not Found - returned if the request URL refers to a resource or object that does not exist
ErrorResponseDto
429
Too Many Requests - Returned in response to too many requests in a given period of time - rate limited. The Retry-After header in the response includes how long to wait before trying again.
ListAccessProfiles429Response
500
Internal Server Error - Returned if there is an unexpected error.
ErrorResponseDto
HTTP request headers
Content-Type: Not defined
Accept: application/json
Example
$Id="MyId"# String | The Source id$XSailPointExperimental="true"# String | Use this header to enable this experimental API. (default to "true")$Locale="de"# String | The locale to apply to the config. If no viable locale is given, it will default to ""en"" (optional)# Gets source config with language translationstry{Get-V2024SourceConfig-V2024Id$Id-V2024XSailPointExperimental$XSailPointExperimental# Below is a request that includes all optional parameters# Get-V2024SourceConfig -V2024Id $Id -V2024XSailPointExperimental $XSailPointExperimental -V2024Locale $Locale }catch{Write-Host$_.Exception.Response.StatusCode.value__"Exception occurred when calling Get-V2024SourceConfig"Write-Host$_.ErrorDetails}
This API gets the current entitlement request configuration for a source. This source-level configuration should apply for all the entitlements in the source.
Access request to any entitlements in the source should follow this configuration unless a separate entitlement-level configuration is defined.
During access request, this source-level entitlement request configuration overrides the global organization-level configuration.
However, the entitlement-level configuration (if defined) overrides this source-level configuration.
Client Error - Returned if the request body is invalid.
ErrorResponseDto
401
Unauthorized - Returned if there is no authorization header, or if the JWT token is expired.
ListAccessProfiles401Response
403
Forbidden - Returned if the user you are running as, doesn't have access to this end-point.
ErrorResponseDto
429
Too Many Requests - Returned in response to too many requests in a given period of time - rate limited. The Retry-After header in the response includes how long to wait before trying again.
ListAccessProfiles429Response
500
Internal Server Error - Returned if there is an unexpected error.
ErrorResponseDto
HTTP request headers
Content-Type: Not defined
Accept: application/json
Example
$XSailPointExperimental="true"# String | Use this header to enable this experimental API. (default to "true")# Get Source Entitlement Request Configurationtry{Get-V2024SourceEntitlementRequestConfig-V2024XSailPointExperimental$XSailPointExperimental# Below is a request that includes all optional parameters# Get-V2024SourceEntitlementRequestConfig -V2024XSailPointExperimental $XSailPointExperimental }catch{Write-Host$_.Exception.Response.StatusCode.value__"Exception occurred when calling Get-V2024SourceEntitlementRequestConfig"Write-Host$_.ErrorDetails}
Client Error - Returned if the request body is invalid.
ErrorResponseDto
401
Unauthorized - Returned if there is no authorization header, or if the JWT token is expired.
ListAccessProfiles401Response
403
Forbidden - Returned if the user you are running as, doesn't have access to this end-point.
ErrorResponseDto
404
Not Found - returned if the request URL refers to a resource or object that does not exist
ErrorResponseDto
429
Too Many Requests - Returned in response to too many requests in a given period of time - rate limited. The Retry-After header in the response includes how long to wait before trying again.
ListAccessProfiles429Response
500
Internal Server Error - Returned if there is an unexpected error.
ErrorResponseDto
HTTP request headers
Content-Type: Not defined
Accept: application/json
Example
$SourceId="2c9180835d191a86015d28455b4a2329"# String | The Source id.# Fetches source health by idtry{Get-V2024SourceHealth-V2024SourceId$SourceId# Below is a request that includes all optional parameters# Get-V2024SourceHealth -V2024SourceId $SourceId }catch{Write-Host$_.Exception.Response.StatusCode.value__"Exception occurred when calling Get-V2024SourceHealth"Write-Host$_.ErrorDetails}
The requested Schedule was successfully retrieved.
Schedule1
400
Client Error - Returned if the request body is invalid.
ErrorResponseDto
401
Unauthorized - Returned if there is no authorization header, or if the JWT token is expired.
ListAccessProfiles401Response
403
Forbidden - Returned if the user you are running as, doesn't have access to this end-point.
ErrorResponseDto
404
Not Found - returned if the request URL refers to a resource or object that does not exist
ErrorResponseDto
429
Too Many Requests - Returned in response to too many requests in a given period of time - rate limited. The Retry-After header in the response includes how long to wait before trying again.
ListAccessProfiles429Response
500
Internal Server Error - Returned if there is an unexpected error.
ErrorResponseDto
HTTP request headers
Content-Type: Not defined
Accept: application/json
Example
$SourceId="2c9180835d191a86015d28455b4a2329"# String | The Source id.$ScheduleType="ACCOUNT_AGGREGATION"# String | The Schedule type.# Get Source Schedule by Typetry{Get-V2024SourceSchedule-V2024SourceId$SourceId-V2024ScheduleType$ScheduleType# Below is a request that includes all optional parameters# Get-V2024SourceSchedule -V2024SourceId $SourceId -V2024ScheduleType $ScheduleType }catch{Write-Host$_.Exception.Response.StatusCode.value__"Exception occurred when calling Get-V2024SourceSchedule"Write-Host$_.ErrorDetails}
Client Error - Returned if the request body is invalid.
ErrorResponseDto
401
Unauthorized - Returned if there is no authorization header, or if the JWT token is expired.
ListAccessProfiles401Response
403
Forbidden - Returned if the user you are running as, doesn't have access to this end-point.
ErrorResponseDto
404
Not Found - returned if the request URL refers to a resource or object that does not exist
ErrorResponseDto
429
Too Many Requests - Returned in response to too many requests in a given period of time - rate limited. The Retry-After header in the response includes how long to wait before trying again.
ListAccessProfiles429Response
500
Internal Server Error - Returned if there is an unexpected error.
ErrorResponseDto
HTTP request headers
Content-Type: Not defined
Accept: application/json
Example
$SourceId="2c9180835d191a86015d28455b4a2329"# String | Source ID.# List Schedules on Sourcetry{Get-V2024SourceSchedules-V2024SourceId$SourceId# Below is a request that includes all optional parameters# Get-V2024SourceSchedules -V2024SourceId $SourceId }catch{Write-Host$_.Exception.Response.StatusCode.value__"Exception occurred when calling Get-V2024SourceSchedules"Write-Host$_.ErrorDetails}
Client Error - Returned if the request body is invalid.
ErrorResponseDto
401
Unauthorized - Returned if there is no authorization header, or if the JWT token is expired.
ListAccessProfiles401Response
403
Forbidden - Returned if the user you are running as, doesn't have access to this end-point.
ErrorResponseDto
404
Not Found - returned if the request URL refers to a resource or object that does not exist
ErrorResponseDto
429
Too Many Requests - Returned in response to too many requests in a given period of time - rate limited. The Retry-After header in the response includes how long to wait before trying again.
ListAccessProfiles429Response
500
Internal Server Error - Returned if there is an unexpected error.
ErrorResponseDto
HTTP request headers
Content-Type: Not defined
Accept: application/json
Example
$SourceId="2c9180835d191a86015d28455b4a2329"# String | The Source id.$SchemaId="2c9180835d191a86015d28455b4a2329"# String | The Schema id.# Get Source Schema by IDtry{Get-V2024SourceSchema-V2024SourceId$SourceId-V2024SchemaId$SchemaId# Below is a request that includes all optional parameters# Get-V2024SourceSchema -V2024SourceId $SourceId -V2024SchemaId $SchemaId }catch{Write-Host$_.Exception.Response.StatusCode.value__"Exception occurred when calling Get-V2024SourceSchema"Write-Host$_.ErrorDetails}
Use this API to list the schemas that exist on the specified source in Identity Security Cloud (ISC).
Parameters
Param Type
Name
Data Type
Required
Description
Path
SourceId
String
True
Source ID.
Query
IncludeTypes
String
(optional)
If set to 'group', then the account schema is filtered and only group schemas are returned. Only a value of 'group' is recognized presently. Note: The API will check whether include-types is group or not, if not, it will list schemas based on include-names, if include-names is not provided, it will list all schemas.
Query
IncludeNames
String
(optional)
A comma-separated list of schema names to filter result.
Client Error - Returned if the request body is invalid.
ErrorResponseDto
401
Unauthorized - Returned if there is no authorization header, or if the JWT token is expired.
ListAccessProfiles401Response
403
Forbidden - Returned if the user you are running as, doesn't have access to this end-point.
ErrorResponseDto
404
Not Found - returned if the request URL refers to a resource or object that does not exist
ErrorResponseDto
429
Too Many Requests - Returned in response to too many requests in a given period of time - rate limited. The Retry-After header in the response includes how long to wait before trying again.
ListAccessProfiles429Response
500
Internal Server Error - Returned if there is an unexpected error.
ErrorResponseDto
HTTP request headers
Content-Type: Not defined
Accept: application/json
Example
$SourceId="2c9180835d191a86015d28455b4a2329"# String | Source ID.$IncludeTypes="group"# String | If set to 'group', then the account schema is filtered and only group schemas are returned. Only a value of 'group' is recognized presently. Note: The API will check whether include-types is group or not, if not, it will list schemas based on include-names, if include-names is not provided, it will list all schemas. (optional)$IncludeNames="account"# String | A comma-separated list of schema names to filter result. (optional)# List Schemas on Sourcetry{Get-V2024SourceSchemas-V2024SourceId$SourceId# Below is a request that includes all optional parameters# Get-V2024SourceSchemas -V2024SourceId $SourceId -V2024IncludeTypes $IncludeTypes -V2024IncludeNames $IncludeNames }catch{Write-Host$_.Exception.Response.StatusCode.value__"Exception occurred when calling Get-V2024SourceSchemas"Write-Host$_.ErrorDetails}
Starts an account aggregation on the specified source.
If the target source is a delimited file source, then the CSV file needs to be included in the request body.
You will also need to set the Content-Type header to multipart/form-data.
Parameters
Param Type
Name
Data Type
Required
Description
Path
Id
String
True
Source Id
XSailPointExperimental
String
True (default to "true")
Use this header to enable this experimental API.
File
System.IO.FileInfo
(optional)
The CSV file containing the source accounts to aggregate.
DisableOptimization
String
(optional)
Use this flag to reprocess every account whether or not the data has changed.
Client Error - Returned if the request body is invalid.
ErrorResponseDto
401
Unauthorized - Returned if there is no authorization header, or if the JWT token is expired.
ListAccessProfiles401Response
403
Forbidden - Returned if the user you are running as, doesn't have access to this end-point.
ErrorResponseDto
429
Too Many Requests - Returned in response to too many requests in a given period of time - rate limited. The Retry-After header in the response includes how long to wait before trying again.
ListAccessProfiles429Response
500
Internal Server Error - Returned if there is an unexpected error.
ErrorResponseDto
HTTP request headers
Content-Type: multipart/form-data
Accept: application/json
Example
$Id="ef38f94347e94562b5bb8424a56397d8"# String | Source Id$XSailPointExperimental="true"# String | Use this header to enable this experimental API. (default to "true")$File=# System.IO.FileInfo | The CSV file containing the source accounts to aggregate. (optional)$DisableOptimization="MyDisableOptimization"# String | Use this flag to reprocess every account whether or not the data has changed. (optional)# Account Aggregationtry{Import-V2024Accounts-V2024Id$Id-V2024XSailPointExperimental$XSailPointExperimental# Below is a request that includes all optional parameters# Import-V2024Accounts -V2024Id $Id -V2024XSailPointExperimental $XSailPointExperimental -V2024File $File -V2024DisableOptimization $DisableOptimization }catch{Write-Host$_.Exception.Response.StatusCode.value__"Exception occurred when calling Import-V2024Accounts"Write-Host$_.ErrorDetails}
Client Error - Returned if the request body is invalid.
ErrorResponseDto
401
Unauthorized - Returned if there is no authorization header, or if the JWT token is expired.
ListAccessProfiles401Response
403
Forbidden - Returned if the user you are running as, doesn't have access to this end-point.
ErrorResponseDto
429
Too Many Requests - Returned in response to too many requests in a given period of time - rate limited. The Retry-After header in the response includes how long to wait before trying again.
ListAccessProfiles429Response
500
Internal Server Error - Returned if there is an unexpected error.
ErrorResponseDto
HTTP request headers
Content-Type: multipart/form-data
Accept: application/json
Example
$Id="8c190e6787aa4ed9a90bd9d5344523fb"# String | The Source id$File=# System.IO.FileInfo | (optional)# Uploads source accounts schema templatetry{Import-V2024AccountsSchema-V2024Id$Id# Below is a request that includes all optional parameters# Import-V2024AccountsSchema -V2024Id $Id -V2024File $File }catch{Write-Host$_.Exception.Response.StatusCode.value__"Exception occurred when calling Import-V2024AccountsSchema"Write-Host$_.ErrorDetails}
Uploaded the file successfully and sent all post-upload events
Source
400
Client Error - Returned if the request body is invalid.
ErrorResponseDto
401
Unauthorized - Returned if there is no authorization header, or if the JWT token is expired.
ListAccessProfiles401Response
403
Forbidden - Returned if the user you are running as, doesn't have access to this end-point.
ErrorResponseDto
429
Too Many Requests - Returned in response to too many requests in a given period of time - rate limited. The Retry-After header in the response includes how long to wait before trying again.
ListAccessProfiles429Response
500
Internal Server Error - Returned if there is an unexpected error.
ErrorResponseDto
HTTP request headers
Content-Type: multipart/form-data
Accept: application/json
Example
$SourceId="2c9180835d191a86015d28455b4a2329"# String | The Source id.$File=# System.IO.FileInfo | (optional)# Upload connector file to sourcetry{Import-V2024ConnectorFile-V2024SourceId$SourceId# Below is a request that includes all optional parameters# Import-V2024ConnectorFile -V2024SourceId $SourceId -V2024File $File }catch{Write-Host$_.Exception.Response.StatusCode.value__"Exception occurred when calling Import-V2024ConnectorFile"Write-Host$_.ErrorDetails}
Client Error - Returned if the request body is invalid.
ErrorResponseDto
401
Unauthorized - Returned if there is no authorization header, or if the JWT token is expired.
ListAccessProfiles401Response
403
Forbidden - Returned if the user you are running as, doesn't have access to this end-point.
ErrorResponseDto
429
Too Many Requests - Returned in response to too many requests in a given period of time - rate limited. The Retry-After header in the response includes how long to wait before trying again.
ListAccessProfiles429Response
500
Internal Server Error - Returned if there is an unexpected error.
ErrorResponseDto
HTTP request headers
Content-Type: multipart/form-data
Accept: application/json
Example
$Id="8c190e6787aa4ed9a90bd9d5344523fb"# String | The Source id$SchemaName="?schemaName=group"# String | Name of entitlement schema (optional)$File=# System.IO.FileInfo | (optional)# Uploads source entitlements schema templatetry{Import-V2024EntitlementsSchema-V2024Id$Id# Below is a request that includes all optional parameters# Import-V2024EntitlementsSchema -V2024Id $Id -V2024SchemaName $SchemaName -V2024File $File }catch{Write-Host$_.Exception.Response.StatusCode.value__"Exception occurred when calling Import-V2024EntitlementsSchema"Write-Host$_.ErrorDetails}
Client Error - Returned if the request body is invalid.
ErrorResponseDto
401
Unauthorized - Returned if there is no authorization header, or if the JWT token is expired.
ListAccessProfiles401Response
403
Forbidden - Returned if the user you are running as, doesn't have access to this end-point.
ErrorResponseDto
429
Too Many Requests - Returned in response to too many requests in a given period of time - rate limited. The Retry-After header in the response includes how long to wait before trying again.
ListAccessProfiles429Response
500
Internal Server Error - Returned if there is an unexpected error.
ErrorResponseDto
HTTP request headers
Content-Type: multipart/form-data
Accept: application/json
Example
$Id="75dbec1ebe154d5785da27b95e1dd5d7"# String | Source Id$XSailPointExperimental="true"# String | Use this header to enable this experimental API. (default to "true")$File=# System.IO.FileInfo | (optional)# Process Uncorrelated Accountstry{Import-V2024UncorrelatedAccounts-V2024Id$Id-V2024XSailPointExperimental$XSailPointExperimental# Below is a request that includes all optional parameters# Import-V2024UncorrelatedAccounts -V2024Id $Id -V2024XSailPointExperimental $XSailPointExperimental -V2024File $File }catch{Write-Host$_.Exception.Response.StatusCode.value__"Exception occurred when calling Import-V2024UncorrelatedAccounts"Write-Host$_.ErrorDetails}
Client Error - Returned if the request body is invalid.
ErrorResponseDto
401
Unauthorized - Returned if there is no authorization header, or if the JWT token is expired.
ListAccessProfiles401Response
403
Forbidden - Returned if the user you are running as, doesn't have access to this end-point.
ErrorResponseDto
404
Not Found - returned if the request URL refers to a resource or object that does not exist
ErrorResponseDto
429
Too Many Requests - Returned in response to too many requests in a given period of time - rate limited. The Retry-After header in the response includes how long to wait before trying again.
ListAccessProfiles429Response
500
Internal Server Error - Returned if there is an unexpected error.
ErrorResponseDto
HTTP request headers
Content-Type: Not defined
Accept: application/json
Example
$SourceId="2c9180835d191a86015d28455b4a2329"# String | The Source id# Lists ProvisioningPoliciestry{Get-V2024ProvisioningPolicies-V2024SourceId$SourceId# Below is a request that includes all optional parameters# Get-V2024ProvisioningPolicies -V2024SourceId $SourceId }catch{Write-Host$_.Exception.Response.StatusCode.value__"Exception occurred when calling Get-V2024ProvisioningPolicies"Write-Host$_.ErrorDetails}
Offset into the full result set. Usually specified with limit to paginate through the results. See V3 API Standard Collection Parameters for more information.
Query
Count
Boolean
(optional) (default to $false)
If true it will populate the X-Total-Count response header with the number of results that would be returned if limit and offset were ignored. Since requesting a total count can have a performance impact, it is recommended not to send count=true if that value will not be used. See V3 API Standard Collection Parameters for more information.
Query
Filters
String
(optional)
Filter results using the standard syntax described in V3 API Standard Collection Parameters Filtering is supported for the following fields and operators: id: eq, in, ge, gt, le, lt, ne, isnull, swname: co, eq, in, sw, ge, gt, ne, isnulltype: eq, in, ge, gt, ne, isnull, swowner.id: eq, in, ge, gt, le, lt, ne, isnull, swfeatures: ca, cocreated: eq, ge, gt, in, le, lt, ne, isnull, swmodified: eq, ge, gt, in, le, lt, ne, isnull, swmanagementWorkgroup.id: eq, ge, gt, in, le, lt, ne, isnull, swdescription: eq, swauthoritative: eq, ne, isnullhealthy: isnullstatus: eq, in, ge, gt, le, lt, ne, isnull, swconnectionType: eq, ge, gt, in, le, lt, ne, isnull, swconnectorName: eq, ge, gt, in, ne, isnull, swcategory: co, eq, ge, gt, in, le, lt, ne, sw
Query
Sorters
String
(optional)
Sort results using the standard syntax described in V3 API Standard Collection Parameters Sorting is supported for the following fields: type, created, modified, name, owner.name, healthy, status, id, description, owner.id, accountCorrelationConfig.id, accountCorrelationConfig.name, managerCorrelationRule.type, managerCorrelationRule.id, managerCorrelationRule.name, authoritative, managementWorkgroup.id, connectorName, connectionType
Query
ForSubadmin
String
(optional)
Filter the returned list of sources for the identity specified by the parameter, which is the id of an identity with the role SOURCE_SUBADMIN. By convention, the value me indicates the identity id of the current user. Subadmins may only view Sources which they are able to administer; all other Sources will be filtered out when this parameter is set. If the current user is a SOURCE_SUBADMIN but fails to pass a valid value for this parameter, a 403 Forbidden is returned.
Client Error - Returned if the request body is invalid.
ErrorResponseDto
401
Unauthorized - Returned if there is no authorization header, or if the JWT token is expired.
ListAccessProfiles401Response
403
Forbidden - Returned if the user you are running as, doesn't have access to this end-point.
ErrorResponseDto
404
Not Found - returned if the request URL refers to a resource or object that does not exist
ErrorResponseDto
429
Too Many Requests - Returned in response to too many requests in a given period of time - rate limited. The Retry-After header in the response includes how long to wait before trying again.
ListAccessProfiles429Response
500
Internal Server Error - Returned if there is an unexpected error.
ErrorResponseDto
HTTP request headers
Content-Type: Not defined
Accept: application/json
Example
$Limit=250# Int32 | Max number of results to return. See [V3 API Standard Collection Parameters](https://developer.sailpoint.com/idn/api/standard-collection-parameters) for more information. (optional) (default to 250)$Offset=0# Int32 | Offset into the full result set. Usually specified with *limit* to paginate through the results. See [V3 API Standard Collection Parameters](https://developer.sailpoint.com/idn/api/standard-collection-parameters) for more information. (optional) (default to 0)$Count=$true# Boolean | If *true* it will populate the *X-Total-Count* response header with the number of results that would be returned if *limit* and *offset* were ignored. Since requesting a total count can have a performance impact, it is recommended not to send **count=true** if that value will not be used. See [V3 API Standard Collection Parameters](https://developer.sailpoint.com/idn/api/standard-collection-parameters) for more information. (optional) (default to $false)$Filters='name eq "Employees"'# String | Filter results using the standard syntax described in [V3 API Standard Collection Parameters](https://developer.sailpoint.com/idn/api/standard-collection-parameters#filtering-results) Filtering is supported for the following fields and operators: **id**: *eq, in, ge, gt, le, lt, ne, isnull, sw* **name**: *co, eq, in, sw, ge, gt, ne, isnull* **type**: *eq, in, ge, gt, ne, isnull, sw* **owner.id**: *eq, in, ge, gt, le, lt, ne, isnull, sw* **features**: *ca, co* **created**: *eq, ge, gt, in, le, lt, ne, isnull, sw* **modified**: *eq, ge, gt, in, le, lt, ne, isnull, sw* **managementWorkgroup.id**: *eq, ge, gt, in, le, lt, ne, isnull, sw* **description**: *eq, sw* **authoritative**: *eq, ne, isnull* **healthy**: *isnull* **status**: *eq, in, ge, gt, le, lt, ne, isnull, sw* **connectionType**: *eq, ge, gt, in, le, lt, ne, isnull, sw* **connectorName**: *eq, ge, gt, in, ne, isnull, sw* **category**: *co, eq, ge, gt, in, le, lt, ne, sw* (optional)$Sorters="name"# String | Sort results using the standard syntax described in [V3 API Standard Collection Parameters](https://developer.sailpoint.com/idn/api/standard-collection-parameters#sorting-results) Sorting is supported for the following fields: **type, created, modified, name, owner.name, healthy, status, id, description, owner.id, accountCorrelationConfig.id, accountCorrelationConfig.name, managerCorrelationRule.type, managerCorrelationRule.id, managerCorrelationRule.name, authoritative, managementWorkgroup.id, connectorName, connectionType** (optional)$ForSubadmin="name"# String | Filter the returned list of sources for the identity specified by the parameter, which is the id of an identity with the role SOURCE_SUBADMIN. By convention, the value **me** indicates the identity id of the current user. Subadmins may only view Sources which they are able to administer; all other Sources will be filtered out when this parameter is set. If the current user is a SOURCE_SUBADMIN but fails to pass a valid value for this parameter, a 403 Forbidden is returned. (optional)$IncludeIDNSource=$true# Boolean | Include the IdentityNow source in the response. (optional) (default to $false)# Lists all sources in IdentityNow.try{Get-V2024Sources# Below is a request that includes all optional parameters# Get-V2024Sources -V2024Limit $Limit -V2024Offset $Offset -V2024Count $Count -V2024Filters $Filters -V2024Sorters $Sorters -V2024ForSubadmin $ForSubadmin -V2024IncludeIDNSource $IncludeIDNSource }catch{Write-Host$_.Exception.Response.StatusCode.value__"Exception occurred when calling Get-V2024Sources"Write-Host$_.ErrorDetails}
List of resource objects that was fetched from the source connector.
ResourceObjectsResponse
400
Client Error - Returned if the request body is invalid.
ErrorResponseDto
401
Unauthorized - Returned if there is no authorization header, or if the JWT token is expired.
ListAccessProfiles401Response
403
Forbidden - Returned if the user you are running as, doesn't have access to this end-point.
ErrorResponseDto
404
Not Found - returned if the request URL refers to a resource or object that does not exist
ErrorResponseDto
429
Too Many Requests - Returned in response to too many requests in a given period of time - rate limited. The Retry-After header in the response includes how long to wait before trying again.
ListAccessProfiles429Response
500
Internal Server Error - Returned if there is an unexpected error.
ErrorResponseDto
HTTP request headers
Content-Type: application/json
Accept: application/json
Example
$SourceId="cef3ee201db947c5912551015ba0c679"# String | The ID of the Source$XSailPointExperimental="true"# String | Use this header to enable this experimental API. (default to "true")$ResourceObjectsRequest=@"{
"maxCount" : 100,
"objectType" : "group"
}"@# Peek source connector's resource objectstry{$Result=ConvertFrom-JsonToResourceObjectsRequest-Json$ResourceObjectsRequestReceive-V2024ResourceObjects-V2024SourceId$SourceId-V2024XSailPointExperimental$XSailPointExperimental-V2024ResourceObjectsRequest$Result# Below is a request that includes all optional parameters# Receive-V2024ResourceObjects -V2024SourceId $SourceId -V2024XSailPointExperimental $XSailPointExperimental -V2024ResourceObjectsRequest $ResourceObjectsRequest }catch{Write-Host$_.Exception.Response.StatusCode.value__"Exception occurred when calling Receive-V2024ResourceObjects"Write-Host$_.ErrorDetails}
The result of pinging connection with the source connector.
StatusResponse
400
Client Error - Returned if the request body is invalid.
ErrorResponseDto
401
Unauthorized - Returned if there is no authorization header, or if the JWT token is expired.
ListAccessProfiles401Response
403
Forbidden - Returned if the user you are running as, doesn't have access to this end-point.
ErrorResponseDto
404
Not Found - returned if the request URL refers to a resource or object that does not exist
ErrorResponseDto
429
Too Many Requests - Returned in response to too many requests in a given period of time - rate limited. The Retry-After header in the response includes how long to wait before trying again.
ListAccessProfiles429Response
500
Internal Server Error - Returned if there is an unexpected error.
ErrorResponseDto
HTTP request headers
Content-Type: Not defined
Accept: application/json
Example
$SourceId="cef3ee201db947c5912551015ba0c679"# String | The ID of the Source$XSailPointExperimental="true"# String | Use this header to enable this experimental API. (default to "true")# Ping cluster for source connectortry{Ping-V2024Cluster-V2024SourceId$SourceId-V2024XSailPointExperimental$XSailPointExperimental# Below is a request that includes all optional parameters# Ping-V2024Cluster -V2024SourceId $SourceId -V2024XSailPointExperimental $XSailPointExperimental }catch{Write-Host$_.Exception.Response.StatusCode.value__"Exception occurred when calling Ping-V2024Cluster"Write-Host$_.ErrorDetails}
Client Error - Returned if the request body is invalid.
ErrorResponseDto
401
Unauthorized - Returned if there is no authorization header, or if the JWT token is expired.
ListAccessProfiles401Response
403
Forbidden - Returned if the user you are running as, doesn't have access to this end-point.
ErrorResponseDto
404
Not Found - returned if the request URL refers to a resource or object that does not exist
ErrorResponseDto
429
Too Many Requests - Returned in response to too many requests in a given period of time - rate limited. The Retry-After header in the response includes how long to wait before trying again.
ListAccessProfiles429Response
500
Internal Server Error - Returned if there is an unexpected error.
Updated native change detection configuration for a source
NativeChangeDetectionConfig
400
Client Error - Returned if the request body is invalid.
ErrorResponseDto
401
Unauthorized - Returned if there is no authorization header, or if the JWT token is expired.
ListAccessProfiles401Response
403
Forbidden - Returned if the user you are running as, doesn't have access to this end-point.
ErrorResponseDto
404
Not Found - returned if the request URL refers to a resource or object that does not exist
ErrorResponseDto
429
Too Many Requests - Returned in response to too many requests in a given period of time - rate limited. The Retry-After header in the response includes how long to wait before trying again.
ListAccessProfiles429Response
500
Internal Server Error - Returned if there is an unexpected error.
ErrorResponseDto
HTTP request headers
Content-Type: application/json
Accept: application/json
Example
$Id="2c9180835d191a86015d28455b4a2329"# String | The source id$XSailPointExperimental="true"# String | Use this header to enable this experimental API. (default to "true")$NativeChangeDetectionConfig=@"{
"selectedEntitlements" : [ "memberOf", "memberOfSharedMailbox" ],
"operations" : [ "ACCOUNT_UPDATED", "ACCOUNT_DELETED" ],
"selectedNonEntitlementAttributes" : [ "lastName", "phoneNumber", "objectType", "servicePrincipalName" ],
"allNonEntitlementAttributes" : false,
"allEntitlements" : false,
"enabled" : true
}"@# Update Native Change Detection Configurationtry{$Result=ConvertFrom-JsonToNativeChangeDetectionConfig-Json$NativeChangeDetectionConfigSend-V2024NativeChangeDetectionConfig-V2024Id$Id-V2024XSailPointExperimental$XSailPointExperimental-V2024NativeChangeDetectionConfig$Result# Below is a request that includes all optional parameters# Send-V2024NativeChangeDetectionConfig -V2024Id $Id -V2024XSailPointExperimental $XSailPointExperimental -V2024NativeChangeDetectionConfig $NativeChangeDetectionConfig }catch{Write-Host$_.Exception.Response.StatusCode.value__"Exception occurred when calling Send-V2024NativeChangeDetectionConfig"Write-Host$_.ErrorDetails}
This end-point updates the provisioning policy with the specified usage on the specified source in IdentityNow.
Transforms can be used in the provisioning policy to create a new attribute that you only need during provisioning.
Refer to Transforms in Provisioning Policies for more information.
The type of provisioning policy usage. In IdentityNow, a source can support various provisioning operations. For example, when a joiner is added to a source, this may trigger both CREATE and UPDATE provisioning operations. Each usage type is considered a provisioning policy. A source can have any number of these provisioning policies defined. These are the common usage types: CREATE - This usage type relates to 'Create Account Profile', the provisioning template for the account to be created. For example, this would be used for a joiner on a source. UPDATE - This usage type relates to 'Update Account Profile', the provisioning template for the 'Update' connector operations. For example, this would be used for an attribute sync on a source. ENABLE - This usage type relates to 'Enable Account Profile', the provisioning template for the account to be enabled. For example, this could be used for a joiner on a source once the joiner's account is created. DISABLE - This usage type relates to 'Disable Account Profile', the provisioning template for the account to be disabled. For example, this could be used when a leaver is removed temporarily from a source. You can use these four usage types for all your provisioning policy needs.
The ProvisioningPolicyDto was successfully replaced.
ProvisioningPolicyDto
400
Client Error - Returned if the request body is invalid.
ErrorResponseDto
401
Unauthorized - Returned if there is no authorization header, or if the JWT token is expired.
ListAccessProfiles401Response
403
Forbidden - Returned if the user you are running as, doesn't have access to this end-point.
ErrorResponseDto
404
Not Found - returned if the request URL refers to a resource or object that does not exist
ErrorResponseDto
429
Too Many Requests - Returned in response to too many requests in a given period of time - rate limited. The Retry-After header in the response includes how long to wait before trying again.
ListAccessProfiles429Response
500
Internal Server Error - Returned if there is an unexpected error.
ErrorResponseDto
HTTP request headers
Content-Type: application/json
Accept: application/json
Example
$SourceId="2c9180835d191a86015d28455b4a2329"# String | The Source ID.$UsageType="CREATE"# UsageType | The type of provisioning policy usage. In IdentityNow, a source can support various provisioning operations. For example, when a joiner is added to a source, this may trigger both CREATE and UPDATE provisioning operations. Each usage type is considered a provisioning policy. A source can have any number of these provisioning policies defined. These are the common usage types: CREATE - This usage type relates to 'Create Account Profile', the provisioning template for the account to be created. For example, this would be used for a joiner on a source. UPDATE - This usage type relates to 'Update Account Profile', the provisioning template for the 'Update' connector operations. For example, this would be used for an attribute sync on a source. ENABLE - This usage type relates to 'Enable Account Profile', the provisioning template for the account to be enabled. For example, this could be used for a joiner on a source once the joiner's account is created. DISABLE - This usage type relates to 'Disable Account Profile', the provisioning template for the account to be disabled. For example, this could be used when a leaver is removed temporarily from a source. You can use these four usage types for all your provisioning policy needs. $ProvisioningPolicyDto=@"{
"name" : "exampleprovisioningpolicyforinactiveidentities",
"description" : "thisprovisioningpolicycreatesaccessbasedonanidentitygoinginactive",
"fields" : [ {
"isRequired" : false,
"transform" : {
"type" : "rule",
"attributes" : {
"name" : "CreateUniqueLDAPAttribute"
}
},
"isMultiValued" : false,
"name" : "userName",
"attributes" : {
"template" : "${firstname}.${lastname}${uniqueCounter}",
"cloudMaxUniqueChecks" : "50",
"cloudMaxSize" : "20",
"cloudRequired" : "true"
},
"type" : "string"
}, {
"isRequired" : false,
"transform" : {
"type" : "rule",
"attributes" : {
"name" : "CreateUniqueLDAPAttribute"
}
},
"isMultiValued" : false,
"name" : "userName",
"attributes" : {
"template" : "${firstname}.${lastname}${uniqueCounter}",
"cloudMaxUniqueChecks" : "50",
"cloudMaxSize" : "20",
"cloudRequired" : "true"
},
"type" : "string"
} ],
"usageType" : "CREATE"
}"@# Update Provisioning Policy by UsageTypetry{$Result=ConvertFrom-JsonToProvisioningPolicyDto-Json$ProvisioningPolicyDtoSend-V2024ProvisioningPolicy-V2024SourceId$SourceId-V2024UsageType$UsageType-V2024ProvisioningPolicyDto$Result# Below is a request that includes all optional parameters# Send-V2024ProvisioningPolicy -V2024SourceId $SourceId -V2024UsageType $UsageType -V2024ProvisioningPolicyDto $ProvisioningPolicyDto }catch{Write-Host$_.Exception.Response.StatusCode.value__"Exception occurred when calling Send-V2024ProvisioningPolicy"Write-Host$_.ErrorDetails}
Use this API to update a source in Identity Security Cloud (ISC), using a full object representation. This means that when you use this API, it completely replaces the existing source configuration.
These fields are immutable, so they cannot be changed:
id
type
authoritative
connector
connectorClass
passwordPolicies
Attempts to modify these fields will result in a 400 error.
Updated Source object. Any passwords will only show the the encrypted cipher-text so that they aren't decryptable in Identity Security Cloud (ISC) cloud-based services, per ISC security design.
Source
400
Client Error - Returned if the request body is invalid.
ErrorResponseDto
401
Unauthorized - Returned if there is no authorization header, or if the JWT token is expired.
ListAccessProfiles401Response
403
Forbidden - Returned if the user you are running as, doesn't have access to this end-point.
ErrorResponseDto
404
Not Found - returned if the request URL refers to a resource or object that does not exist
ErrorResponseDto
429
Too Many Requests - Returned in response to too many requests in a given period of time - rate limited. The Retry-After header in the response includes how long to wait before trying again.
ListAccessProfiles429Response
500
Internal Server Error - Returned if there is an unexpected error.
Replaces the attribute synchronization configuration for the source specified by the given ID with the configuration provided in the request body. Only the "enabled" field of the values in the "attributes" array is mutable. Attempting to change other attributes or add new values to the "attributes" array will result in an error.
Updated attribute synchronization configuration for a source
AttrSyncSourceConfig
400
Client Error - Returned if the request body is invalid.
ErrorResponseDto
401
Unauthorized - Returned if there is no authorization header, or if the JWT token is expired.
ListAccessProfiles401Response
403
Forbidden - Returned if the user you are running as, doesn't have access to this end-point.
ErrorResponseDto
404
Not Found - returned if the request URL refers to a resource or object that does not exist
ErrorResponseDto
429
Too Many Requests - Returned in response to too many requests in a given period of time - rate limited. The Retry-After header in the response includes how long to wait before trying again.
ListAccessProfiles429Response
500
Internal Server Error - Returned if there is an unexpected error.
ErrorResponseDto
HTTP request headers
Content-Type: application/json
Accept: application/json
Example
$Id="2c9180835d191a86015d28455b4a2329"# String | The source id$XSailPointExperimental="true"# String | Use this header to enable this experimental API. (default to "true")$AttrSyncSourceConfig=@"{
"attributes" : [ {
"name" : "email",
"displayName" : "Email",
"enabled" : true,
"target" : "mail"
}, {
"name" : "firstname",
"displayName" : "FirstName",
"enabled" : false,
"target" : "givenName"
} ],
"source" : {
"name" : "HRActiveDirectory",
"id" : "2c9180835d191a86015d28455b4b232a",
"type" : "SOURCE"
}
}"@# Update Attribute Sync Configtry{$Result=ConvertFrom-JsonToAttrSyncSourceConfig-Json$AttrSyncSourceConfigSend-V2024SourceAttrSyncConfig-V2024Id$Id-V2024XSailPointExperimental$XSailPointExperimental-V2024AttrSyncSourceConfig$Result# Below is a request that includes all optional parameters# Send-V2024SourceAttrSyncConfig -V2024Id $Id -V2024XSailPointExperimental $XSailPointExperimental -V2024AttrSyncSourceConfig $AttrSyncSourceConfig }catch{Write-Host$_.Exception.Response.StatusCode.value__"Exception occurred when calling Send-V2024SourceAttrSyncConfig"Write-Host$_.ErrorDetails}
This API will completely replace an existing Schema with the submitted payload. Some fields of the Schema cannot be updated. These fields are listed below.
id
name
created
modified
Any attempt to modify these fields will result in an error response with a status code of 400.
id must remain in the request body, but it cannot be changed. If id is omitted from the request body, the result will be a 400 error.
Client Error - Returned if the request body is invalid.
ErrorResponseDto
401
Unauthorized - Returned if there is no authorization header, or if the JWT token is expired.
ListAccessProfiles401Response
403
Forbidden - Returned if the user you are running as, doesn't have access to this end-point.
ErrorResponseDto
404
Not Found - returned if the request URL refers to a resource or object that does not exist
ErrorResponseDto
429
Too Many Requests - Returned in response to too many requests in a given period of time - rate limited. The Retry-After header in the response includes how long to wait before trying again.
ListAccessProfiles429Response
500
Internal Server Error - Returned if there is an unexpected error.
Client Error - Returned if the request body is invalid.
ErrorResponseDto
401
Unauthorized - Returned if there is no authorization header, or if the JWT token is expired.
ListAccessProfiles401Response
403
Forbidden - Returned if the user you are running as, doesn't have access to this end-point.
ErrorResponseDto
404
Not Found - returned if the request URL refers to a resource or object that does not exist
ErrorResponseDto
429
Too Many Requests - Returned in response to too many requests in a given period of time - rate limited. The Retry-After header in the response includes how long to wait before trying again.
ListAccessProfiles429Response
500
Internal Server Error - Returned if there is an unexpected error.
ErrorResponseDto
HTTP request headers
Content-Type: Not defined
Accept: application/json
Example
$Id="MyId"# String | The Source id$XSailPointExperimental="true"# String | Use this header to enable this experimental API. (default to "true")# Synchronize single source attributes.try{Sync-V2024AttributesForSource-V2024Id$Id-V2024XSailPointExperimental$XSailPointExperimental# Below is a request that includes all optional parameters# Sync-V2024AttributesForSource -V2024Id $Id -V2024XSailPointExperimental $XSailPointExperimental }catch{Write-Host$_.Exception.Response.StatusCode.value__"Exception occurred when calling Sync-V2024AttributesForSource"Write-Host$_.ErrorDetails}
This endpoint performs a more detailed validation of the source''s configuration that can take longer than the lighter weight credential validation performed by the checkConnection API.
The result of testing source connector configuration with response from it.
StatusResponse
400
Client Error - Returned if the request body is invalid.
ErrorResponseDto
401
Unauthorized - Returned if there is no authorization header, or if the JWT token is expired.
ListAccessProfiles401Response
403
Forbidden - Returned if the user you are running as, doesn't have access to this end-point.
ErrorResponseDto
404
Not Found - returned if the request URL refers to a resource or object that does not exist
ErrorResponseDto
429
Too Many Requests - Returned in response to too many requests in a given period of time - rate limited. The Retry-After header in the response includes how long to wait before trying again.
ListAccessProfiles429Response
500
Internal Server Error - Returned if there is an unexpected error.
ErrorResponseDto
HTTP request headers
Content-Type: Not defined
Accept: application/json
Example
$SourceId="cef3ee201db947c5912551015ba0c679"# String | The ID of the Source$XSailPointExperimental="true"# String | Use this header to enable this experimental API. (default to "true")# Test configuration for source connectortry{Test-V2024SourceConfiguration-V2024SourceId$SourceId-V2024XSailPointExperimental$XSailPointExperimental# Below is a request that includes all optional parameters# Test-V2024SourceConfiguration -V2024SourceId $SourceId -V2024XSailPointExperimental $XSailPointExperimental }catch{Write-Host$_.Exception.Response.StatusCode.value__"Exception occurred when calling Test-V2024SourceConfiguration"Write-Host$_.ErrorDetails}
This endpoint validates that the configured credentials are valid and will properly authenticate with the source identified by the sourceId path parameter.
The result of checking connection to the source connector with response from it.
StatusResponse
400
Client Error - Returned if the request body is invalid.
ErrorResponseDto
401
Unauthorized - Returned if there is no authorization header, or if the JWT token is expired.
ListAccessProfiles401Response
403
Forbidden - Returned if the user you are running as, doesn't have access to this end-point.
ErrorResponseDto
404
Not Found - returned if the request URL refers to a resource or object that does not exist
ErrorResponseDto
429
Too Many Requests - Returned in response to too many requests in a given period of time - rate limited. The Retry-After header in the response includes how long to wait before trying again.
ListAccessProfiles429Response
500
Internal Server Error - Returned if there is an unexpected error.
ErrorResponseDto
HTTP request headers
Content-Type: Not defined
Accept: application/json
Example
$SourceId="cef3ee201db947c5912551015ba0c679"# String | The ID of the Source.$XSailPointExperimental="true"# String | Use this header to enable this experimental API. (default to "true")# Check connection for source connector.try{Test-V2024SourceConnection-V2024SourceId$SourceId-V2024XSailPointExperimental$XSailPointExperimental# Below is a request that includes all optional parameters# Test-V2024SourceConnection -V2024SourceId $SourceId -V2024XSailPointExperimental $XSailPointExperimental }catch{Write-Host$_.Exception.Response.StatusCode.value__"Exception occurred when calling Test-V2024SourceConnection"Write-Host$_.ErrorDetails}
Client Error - Returned if the request body is invalid.
ErrorResponseDto
401
Unauthorized - Returned if there is no authorization header, or if the JWT token is expired.
ListAccessProfiles401Response
403
Forbidden - Returned if the user you are running as, doesn't have access to this end-point.
ErrorResponseDto
404
Not Found - returned if the request URL refers to a resource or object that does not exist
ErrorResponseDto
429
Too Many Requests - Returned in response to too many requests in a given period of time - rate limited. The Retry-After header in the response includes how long to wait before trying again.
ListAccessProfiles429Response
500
Internal Server Error - Returned if there is an unexpected error.
ErrorResponseDto
HTTP request headers
Content-Type: application/json
Accept: application/json
Example
$SourceId="8c190e6787aa4ed9a90bd9d5344523fb"# String | The Source id$PasswordPolicyHoldersDtoInner=@""@# PasswordPolicyHoldersDtoInner[] | # Update Password Policytry{$Result=ConvertFrom-JsonToPasswordPolicyHoldersDtoInner-Json$PasswordPolicyHoldersDtoInnerUpdate-V2024PasswordPolicyHolders-V2024SourceId$SourceId-V2024PasswordPolicyHoldersDtoInner$Result# Below is a request that includes all optional parameters# Update-V2024PasswordPolicyHolders -V2024SourceId $SourceId -V2024PasswordPolicyHoldersDtoInner $PasswordPolicyHoldersDtoInner }catch{Write-Host$_.Exception.Response.StatusCode.value__"Exception occurred when calling Update-V2024PasswordPolicyHolders"Write-Host$_.ErrorDetails}
A list of the ProvisioningPolicyDto was successfully replaced.
ProvisioningPolicyDto[]
400
Client Error - Returned if the request body is invalid.
ErrorResponseDto
401
Unauthorized - Returned if there is no authorization header, or if the JWT token is expired.
ListAccessProfiles401Response
403
Forbidden - Returned if the user you are running as, doesn't have access to this end-point.
ErrorResponseDto
404
Not Found - returned if the request URL refers to a resource or object that does not exist
ErrorResponseDto
429
Too Many Requests - Returned in response to too many requests in a given period of time - rate limited. The Retry-After header in the response includes how long to wait before trying again.
ListAccessProfiles429Response
500
Internal Server Error - Returned if there is an unexpected error.
This API selectively updates an existing Provisioning Policy using a JSONPatch payload.
Transforms can be used in the provisioning policy to create a new attribute that you only need during provisioning.
Refer to Transforms in Provisioning Policies for more information.
The type of provisioning policy usage. In IdentityNow, a source can support various provisioning operations. For example, when a joiner is added to a source, this may trigger both CREATE and UPDATE provisioning operations. Each usage type is considered a provisioning policy. A source can have any number of these provisioning policies defined. These are the common usage types: CREATE - This usage type relates to 'Create Account Profile', the provisioning template for the account to be created. For example, this would be used for a joiner on a source. UPDATE - This usage type relates to 'Update Account Profile', the provisioning template for the 'Update' connector operations. For example, this would be used for an attribute sync on a source. ENABLE - This usage type relates to 'Enable Account Profile', the provisioning template for the account to be enabled. For example, this could be used for a joiner on a source once the joiner's account is created. DISABLE - This usage type relates to 'Disable Account Profile', the provisioning template for the account to be disabled. For example, this could be used when a leaver is removed temporarily from a source. You can use these four usage types for all your provisioning policy needs.
The ProvisioningPolicyDto was successfully updated.
ProvisioningPolicyDto
400
Client Error - Returned if the request body is invalid.
ErrorResponseDto
401
Unauthorized - Returned if there is no authorization header, or if the JWT token is expired.
ListAccessProfiles401Response
403
Forbidden - Returned if the user you are running as, doesn't have access to this end-point.
ErrorResponseDto
404
Not Found - returned if the request URL refers to a resource or object that does not exist
ErrorResponseDto
429
Too Many Requests - Returned in response to too many requests in a given period of time - rate limited. The Retry-After header in the response includes how long to wait before trying again.
ListAccessProfiles429Response
500
Internal Server Error - Returned if there is an unexpected error.
ErrorResponseDto
HTTP request headers
Content-Type: application/json-patch+json
Accept: application/json
Example
$SourceId="2c9180835d191a86015d28455b4a2329"# String | The Source id.$UsageType="CREATE"# UsageType | The type of provisioning policy usage. In IdentityNow, a source can support various provisioning operations. For example, when a joiner is added to a source, this may trigger both CREATE and UPDATE provisioning operations. Each usage type is considered a provisioning policy. A source can have any number of these provisioning policies defined. These are the common usage types: CREATE - This usage type relates to 'Create Account Profile', the provisioning template for the account to be created. For example, this would be used for a joiner on a source. UPDATE - This usage type relates to 'Update Account Profile', the provisioning template for the 'Update' connector operations. For example, this would be used for an attribute sync on a source. ENABLE - This usage type relates to 'Enable Account Profile', the provisioning template for the account to be enabled. For example, this could be used for a joiner on a source once the joiner's account is created. DISABLE - This usage type relates to 'Disable Account Profile', the provisioning template for the account to be disabled. For example, this could be used when a leaver is removed temporarily from a source. You can use these four usage types for all your provisioning policy needs. $JsonPatchOperation=@"{
"op" : "replace",
"path" : "/description",
"value" : "Newdescription"
}"@# JsonPatchOperation[] | The JSONPatch payload used to update the schema.# Partial update of Provisioning Policytry{$Result=ConvertFrom-JsonToJsonPatchOperation-Json$JsonPatchOperationUpdate-V2024ProvisioningPolicy-V2024SourceId$SourceId-V2024UsageType$UsageType-V2024JsonPatchOperation$Result# Below is a request that includes all optional parameters# Update-V2024ProvisioningPolicy -V2024SourceId $SourceId -V2024UsageType $UsageType -V2024JsonPatchOperation $JsonPatchOperation }catch{Write-Host$_.Exception.Response.StatusCode.value__"Exception occurred when calling Update-V2024ProvisioningPolicy"Write-Host$_.ErrorDetails}
A list of account update operations according to the JSON Patch standard. Any password changes are submitted as plain-text and encrypted upon receipt in Identity Security Cloud (ISC).
Updated Source object. Any passwords will only show the the encrypted cipher-text so that they aren't decryptable in Identity Security Cloud (ISC) cloud-based services, per ISC security design.
Source
400
Client Error - Returned if the request body is invalid.
ErrorResponseDto
401
Unauthorized - Returned if there is no authorization header, or if the JWT token is expired.
ListAccessProfiles401Response
403
Forbidden - Returned if the user you are running as, doesn't have access to this end-point.
ErrorResponseDto
404
Not Found - returned if the request URL refers to a resource or object that does not exist
ErrorResponseDto
429
Too Many Requests - Returned in response to too many requests in a given period of time - rate limited. The Retry-After header in the response includes how long to wait before trying again.
ListAccessProfiles429Response
500
Internal Server Error - Returned if there is an unexpected error.
ErrorResponseDto
HTTP request headers
Content-Type: application/json-patch+json
Accept: application/json
Example
$Id="2c9180835d191a86015d28455b4a2329"# String | Source ID.$JsonPatchOperation=@"{
"op" : "replace",
"path" : "/description",
"value" : "Newdescription"
}"@# JsonPatchOperation[] | A list of account update operations according to the [JSON Patch](https://tools.ietf.org/html/rfc6902) standard. Any password changes are submitted as plain-text and encrypted upon receipt in Identity Security Cloud (ISC).# Update Source (Partial)try{$Result=ConvertFrom-JsonToJsonPatchOperation-Json$JsonPatchOperationUpdate-V2024Source-V2024Id$Id-V2024JsonPatchOperation$Result# Below is a request that includes all optional parameters# Update-V2024Source -V2024Id $Id -V2024JsonPatchOperation $JsonPatchOperation }catch{Write-Host$_.Exception.Response.StatusCode.value__"Exception occurred when calling Update-V2024Source"Write-Host$_.ErrorDetails}
This API replaces the current entitlement request configuration for a source. This source-level configuration should apply for all the entitlements in the source.
Access request to any entitlements in the source should follow this configuration unless a separate entitlement-level configuration is defined.
During access request, this source-level entitlement request configuration overrides the global organization-level configuration.
However, the entitlement-level configuration (if defined) overrides this source-level configuration.
Client Error - Returned if the request body is invalid.
ErrorResponseDto
401
Unauthorized - Returned if there is no authorization header, or if the JWT token is expired.
ListAccessProfiles401Response
403
Forbidden - Returned if the user you are running as, doesn't have access to this end-point.
ErrorResponseDto
429
Too Many Requests - Returned in response to too many requests in a given period of time - rate limited. The Retry-After header in the response includes how long to wait before trying again.
ListAccessProfiles429Response
500
Internal Server Error - Returned if there is an unexpected error.
ErrorResponseDto
HTTP request headers
Content-Type: application/json
Accept: application/json
Example
$XSailPointExperimental="true"# String | Use this header to enable this experimental API. (default to "true")$SourceEntitlementRequestConfig=@"{
"accessRequestConfig" : {
"denialCommentRequired" : false,
"approvalSchemes" : [ {
"approverId" : "e3eab852-8315-467f-9de7-70eda97f63c8",
"approverType" : "GOVERNANCE_GROUP"
}, {
"approverId" : "e3eab852-8315-467f-9de7-70eda97f63c8",
"approverType" : "GOVERNANCE_GROUP"
} ],
"requestCommentRequired" : true
}
}"@# Update Source Entitlement Request Configurationtry{$Result=ConvertFrom-JsonToSourceEntitlementRequestConfig-Json$SourceEntitlementRequestConfigUpdate-V2024SourceEntitlementRequestConfig-V2024XSailPointExperimental$XSailPointExperimental-V2024SourceEntitlementRequestConfig$Result# Below is a request that includes all optional parameters# Update-V2024SourceEntitlementRequestConfig -V2024XSailPointExperimental $XSailPointExperimental -V2024SourceEntitlementRequestConfig $SourceEntitlementRequestConfig }catch{Write-Host$_.Exception.Response.StatusCode.value__"Exception occurred when calling Update-V2024SourceEntitlementRequestConfig"Write-Host$_.ErrorDetails}
Client Error - Returned if the request body is invalid.
ErrorResponseDto
401
Unauthorized - Returned if there is no authorization header, or if the JWT token is expired.
ListAccessProfiles401Response
403
Forbidden - Returned if the user you are running as, doesn't have access to this end-point.
ErrorResponseDto
404
Not Found - returned if the request URL refers to a resource or object that does not exist
ErrorResponseDto
429
Too Many Requests - Returned in response to too many requests in a given period of time - rate limited. The Retry-After header in the response includes how long to wait before trying again.
ListAccessProfiles429Response
500
Internal Server Error - Returned if there is an unexpected error.
ErrorResponseDto
HTTP request headers
Content-Type: application/json-patch+json
Accept: application/json
Example
$SourceId="2c9180835d191a86015d28455b4a2329"# String | The Source id.$ScheduleType="ACCOUNT_AGGREGATION"# String | The Schedule type.$JsonPatchOperation=@"{
"op" : "replace",
"path" : "/description",
"value" : "Newdescription"
}"@# JsonPatchOperation[] | The JSONPatch payload used to update the schedule.# Update Source Schedule (Partial)try{$Result=ConvertFrom-JsonToJsonPatchOperation-Json$JsonPatchOperationUpdate-V2024SourceSchedule-V2024SourceId$SourceId-V2024ScheduleType$ScheduleType-V2024JsonPatchOperation$Result# Below is a request that includes all optional parameters# Update-V2024SourceSchedule -V2024SourceId $SourceId -V2024ScheduleType $ScheduleType -V2024JsonPatchOperation $JsonPatchOperation }catch{Write-Host$_.Exception.Response.StatusCode.value__"Exception occurred when calling Update-V2024SourceSchedule"Write-Host$_.ErrorDetails}
Use this API to selectively update an existing Schema using a JSONPatch payload.
The following schema fields are immutable and cannot be updated:
id
name
created
modified
To switch an account attribute to a group entitlement, you need to have the following in place:
isEntitlement: true
Must define a schema for the group and add it to the source before updating the isGroup flag. For example, here is the group account attribute referencing a schema that defines the group:
{"name":"groups","type":"STRING","schema":{"type":"CONNECTOR_SCHEMA","id":"2c9180887671ff8c01767b4671fc7d60","name":"group"},"description":"The groups, roles etc. that reference account group objects","isMulti":true,"isEntitlement":true,"isGroup":true}
Client Error - Returned if the request body is invalid.
ErrorResponseDto
401
Unauthorized - Returned if there is no authorization header, or if the JWT token is expired.
ListAccessProfiles401Response
403
Forbidden - Returned if the user you are running as, doesn't have access to this end-point.
ErrorResponseDto
404
Not Found - returned if the request URL refers to a resource or object that does not exist
ErrorResponseDto
429
Too Many Requests - Returned in response to too many requests in a given period of time - rate limited. The Retry-After header in the response includes how long to wait before trying again.
ListAccessProfiles429Response
500
Internal Server Error - Returned if there is an unexpected error.
ErrorResponseDto
HTTP request headers
Content-Type: application/json-patch+json
Accept: application/json
Example
$SourceId="2c9180835d191a86015d28455b4a2329"# String | The Source id.$SchemaId="2c9180835d191a86015d28455b4a2329"# String | The Schema id.$JsonPatchOperation=@"{
"op" : "replace",
"path" : "/description",
"value" : "Newdescription"
}"@# JsonPatchOperation[] | The JSONPatch payload used to update the schema.# Update Source Schema (Partial)try{$Result=ConvertFrom-JsonToJsonPatchOperation-Json$JsonPatchOperationUpdate-V2024SourceSchema-V2024SourceId$SourceId-V2024SchemaId$SchemaId-V2024JsonPatchOperation$Result# Below is a request that includes all optional parameters# Update-V2024SourceSchema -V2024SourceId $SourceId -V2024SchemaId $SchemaId -V2024JsonPatchOperation $JsonPatchOperation }catch{Write-Host$_.Exception.Response.StatusCode.value__"Exception occurred when calling Update-V2024SourceSchema"Write-Host$_.ErrorDetails}