Use this API to implement connector rule management functionality.
With this functionality in place, administrators can implement connector-executed rules in a programmatic, scalable way.
In Identity Security Cloud (ISC), rules serve as a flexible configuration framework you can leverage to perform complex or advanced configurations.
Connector-executed rules are rules that are executed in the ISC virtual appliance (VA), usually extensions of the connector itself, the bridge between the data source and ISC.
This API allows administrators to view existing connector-executed rules, make changes to them, delete them, and create new ones from the available types.
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.
ListAccessModelMetadataAttribute401Response
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.
ListAccessModelMetadataAttribute429Response
500
Internal Server Error - Returned if there is an unexpected error.
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.
ListAccessModelMetadataAttribute401Response
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.
ListAccessModelMetadataAttribute429Response
500
Internal Server Error - Returned if there is an unexpected error.
ErrorResponseDto
HTTP request headers
Content-Type: Not defined
Accept: application/json
Example
$Id="8c190e6787aa4ed9a90bd9d5344523fb"# String | ID of the connector rule to delete# Delete a connector-ruletry{Remove-BetaConnectorRule-Id$Id# Below is a request that includes all optional parameters# Remove-BetaConnectorRule -Id $Id }catch{Write-Host$_.Exception.Response.StatusCode.value__"Exception occurred when calling Remove-BetaConnectorRule"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.
ListAccessModelMetadataAttribute401Response
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.
ListAccessModelMetadataAttribute429Response
500
Internal Server Error - Returned if there is an unexpected error.
ErrorResponseDto
HTTP request headers
Content-Type: Not defined
Accept: application/json
Example
$Id="8c190e6787aa4ed9a90bd9d5344523fb"# String | ID of the connector rule to retrieve# Connector-rule by idtry{Get-BetaConnectorRule-Id$Id# Below is a request that includes all optional parameters# Get-BetaConnectorRule -Id $Id }catch{Write-Host$_.Exception.Response.StatusCode.value__"Exception occurred when calling Get-BetaConnectorRule"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.
ListAccessModelMetadataAttribute401Response
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.
ListAccessModelMetadataAttribute429Response
500
Internal Server Error - Returned if there is an unexpected error.
ErrorResponseDto
HTTP request headers
Content-Type: Not defined
Accept: application/json
Example
# List connector rulestry{Get-BetaConnectorRuleList# Below is a request that includes all optional parameters# Get-BetaConnectorRuleList }catch{Write-Host$_.Exception.Response.StatusCode.value__"Exception occurred when calling Get-BetaConnectorRuleList"Write-Host$_.ErrorDetails}
Updates an existing connector rule with the one provided in the request body. Note that the fields 'id', 'name', and 'type' are immutable.
A token with ORG_ADMIN authority is required to call this API.
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.
ListAccessModelMetadataAttribute401Response
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.
ListAccessModelMetadataAttribute429Response
500
Internal Server Error - Returned if there is an unexpected error.
ErrorResponseDto
HTTP request headers
Content-Type: application/json
Accept: application/json
Example
$Id="8c190e6787aa4ed9a90bd9d5344523fb"# String | ID of the connector rule to update$ConnectorRuleUpdateRequest=@"{
"sourceCode" : {
"version" : "1.0",
"script" : "return\"Mr. \"+firstName;"
},
"signature" : {
"output" : {
"name" : "firstName",
"description" : "thefirstnameoftheidentity",
"type" : "String"
},
"input" : [ {
"name" : "firstName",
"description" : "thefirstnameoftheidentity",
"type" : "String"
}, {
"name" : "firstName",
"description" : "thefirstnameoftheidentity",
"type" : "String"
} ]
},
"name" : "WebServiceBeforeOperationRule",
"description" : "Thisruledoesthat",
"attributes" : { },
"id" : "8113d48c0b914f17b4c6072d4dcb9dfe",
"type" : "BuildMap"
}"@# Update a connector ruletry{Update-BetaConnectorRule-Id$Id# Below is a request that includes all optional parameters# Update-BetaConnectorRule -Id $Id -ConnectorRuleUpdateRequest $Result }catch{Write-Host$_.Exception.Response.StatusCode.value__"Exception occurred when calling Update-BetaConnectorRule"Write-Host$_.ErrorDetails}
The status of the code's eligibility as a connector rule
ConnectorRuleValidationResponse
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.
ListAccessModelMetadataAttribute401Response
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.
ListAccessModelMetadataAttribute429Response
500
Internal Server Error - Returned if there is an unexpected error.
ErrorResponseDto
HTTP request headers
Content-Type: application/json
Accept: application/json
Example
$SourceCode=@"{
"version" : "1.0",
"script" : "return\"Mr. \"+firstName;"
}"@# Validate connector ruletry{$Result=ConvertFrom-JsonToSourceCode-Json$SourceCodeConfirm-BetaConnectorRule-SourceCode$Result# Below is a request that includes all optional parameters# Confirm-BetaConnectorRule -SourceCode $Result }catch{Write-Host$_.Exception.Response.StatusCode.value__"Exception occurred when calling Confirm-BetaConnectorRule"Write-Host$_.ErrorDetails}