Skip to content

Commit

Permalink
Automated commit 'Merge pull request #1529 from sailpoint/devrel-1430
Browse files Browse the repository at this point in the history
devrel-1430' by github action: 7574127501
  • Loading branch information
tyler-mairose-sp committed Jan 18, 2024
1 parent 947efbf commit cb4d0d3
Show file tree
Hide file tree
Showing 5 changed files with 45 additions and 30 deletions.
2 changes: 2 additions & 0 deletions idn/beta/schemas/ProvisioningConfig.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -5,6 +5,7 @@ properties:
description: Specifies whether this configuration is used to manage provisioning requests for all sources from the org. If true, no managedResourceRefs are allowed.
type: boolean
readOnly: true
default: false
example: true
managedResourceRefs:
description: References to sources for the Service Desk integration template. May only be specified if universalManager is false.
Expand Down Expand Up @@ -43,6 +44,7 @@ properties:
noProvisioningRequests:
description: Name of an attribute that when true disables the saving of ProvisioningRequest objects whenever plans are sent through this integration.
type: boolean
default: false
example: true
provisioningRequestExpiration:
description: When saving pending requests is enabled, this defines the number of hours the request is allowed to live before it is considered expired and no longer affects plan compilation.
Expand Down
16 changes: 10 additions & 6 deletions idn/beta/schemas/ServiceDeskIntegrationDto.yaml
Original file line number Diff line number Diff line change
@@ -1,19 +1,23 @@
allOf:
- $ref: './BaseCommonDto.yaml'
- type: object
description: Specification of a Service Desk integration.
description: Service Desk integration's specification.
required:
- name
- description
- type
- attributes
properties:
name:
description: Service Desk integration's name. The name must be unique.
type: string
example: Service Desk Integration Name
description:
description: Description of the Service Desk integration.
description: Service Desk integration's description.
type: string
example: A very nice Service Desk integration
type:
description: |
Service Desk integration types
Service Desk integration types:
- ServiceNowSDIM
- ServiceNow
Expand All @@ -27,7 +31,7 @@ allOf:
allOf:
- $ref: '../../v3/schemas/SourceClusterDto.yaml'
cluster:
description: ID of the cluster for the Service Desk integration (replaced by clusterRef, retained for backward compatibility).
description: Cluster ID for the Service Desk integration (replaced by clusterRef, retained for backward compatibility).
type: string
example: xyzzy999
deprecated: true
Expand All @@ -44,7 +48,7 @@ allOf:
description: The 'provisioningConfig' property specifies the configuration used to provision integrations.
$ref: './ProvisioningConfig.yaml'
attributes:
description: Attributes of the Service Desk integration. Validation constraints enforced by the implementation.
description: Service Desk integration's attributes. Validation constraints enforced by the implementation.
type: object
additionalProperties: true
example: {
Expand Down
20 changes: 19 additions & 1 deletion idn/sailpoint-api.v3.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -736,7 +736,25 @@ tags:
Refer to [Subscribe to a SOD Policy](https://documentation.sailpoint.com/saas/help/sod/policy-violations.html#subscribe-to-an-sod-policy) for more information about SOD policy subscriptions.
- name: SOD Violations
description: Operations for Predicting SOD (Separation of Duties) violations
description: |
Use this API to check for current "separation of duties" (SOD) policy violations as well as potential future SOD policy violations.
With SOD violation functionality in place, administrators can get information about current SOD policy violations and predict whether an access change will trigger new violations, which helps to prevent them from occurring at all.
"Separation of duties" refers to the concept that people shouldn't have conflicting sets of access - all their access should be configured in a way that protects your organization's assets and data.
For example, people who record monetary transactions shouldn't be able to issue payment for those transactions.
Any changes to major system configurations should be approved by someone other than the person requesting the change.
Organizations can use "separation of duties" (SOD) policies to enforce and track their internal security rules throughout their tenants.
These SOD policies limit each user's involvement in important processes and protects the organization from individuals gaining excessive access.
Once a SOD policy is in place, if an identity has conflicting access items, a SOD violation will trigger.
These violations are included in SOD violation reports that other users will see in emails at regular intervals if they're subscribed to the SOD policy.
The other users can then better help to enforce these SOD policies.
Administrators can use the SOD violations APIs to check a set of identities for any current SOD violations, and they can use them to check whether adding an access item would potentially trigger a SOD violation.
This second option is a good way to prevent SOD violations from triggering at all.
Refer to [Handling Policy Violations](https://documentation.sailpoint.com/saas/help/sod/policy-violations.html) for more information about SOD policy violations.
- name: Sources
description: |
Use this API to implement and customize source functionality.
Expand Down
2 changes: 2 additions & 0 deletions idn/v3/schemas/ProvisioningConfig.yaml
Original file line number Diff line number Diff line change
Expand Up @@ -5,6 +5,7 @@ properties:
description: Specifies whether this configuration is used to manage provisioning requests for all sources from the org. If true, no managedResourceRefs are allowed.
type: boolean
readOnly: true
default: false
example: true
managedResourceRefs:
description: References to sources for the Service Desk integration template. May only be specified if universalManager is false.
Expand All @@ -31,6 +32,7 @@ properties:
noProvisioningRequests:
description: Name of an attribute that when true disables the saving of ProvisioningRequest objects whenever plans are sent through this integration.
type: boolean
default: false
example: true
provisioningRequestExpiration:
description: When saving pending requests is enabled, this defines the number of hours the request is allowed to live before it is considered expired and no longer affects plan compilation.
Expand Down
35 changes: 12 additions & 23 deletions idn/v3/schemas/ServiceDeskIntegrationDto.yaml
Original file line number Diff line number Diff line change
@@ -1,48 +1,37 @@
allOf:
- $ref: './BaseCommonDto.yaml'
- type: object
description: Specification of a Service Desk integration
description: Service Desk integration's specification.
required:
- name
- description
- type
- attributes
properties:
name:
description: Service Desk integration's name. The name must be unique.
type: string
example: Service Desk Integration Name
description:
description: Description of the Service Desk integration
description: Service Desk integration's description.
type: string
example: A very nice Service Desk integration
type:
description: |
Service Desk integration types
Service Desk integration types:
- ServiceNowSDIM
- ServiceNow
type: string
default: ServiceNowSDIM
example: ServiceNowSDIM
ownerRef:
type: object
description: Source for Service Desk integration template.
properties:
type:
type: string
description: DTO type of source for service desk integration template.
enum:
- SOURCE
example: SOURCE
id:
type: string
description: ID of source for service desk integration template.
example: 2c9180835d191a86015d28455b4b232a
name:
type: string
description: Human-readable name of source for service desk integration template.
example: HR Active Directory
allOf:
- $ref: '../../v3/schemas/OwnerDto.yaml'
clusterRef:
allOf:
- $ref: '../../v3/schemas/SourceClusterDto.yaml'
cluster:
description: ID of the cluster for the Service Desk integration (replaced by clusterRef, retained for backward compatibility).
description: Cluster ID for the Service Desk integration (replaced by clusterRef, retained for backward compatibility).
type: string
example: xyzzy999
deprecated: true
Expand All @@ -59,7 +48,7 @@ allOf:
description: The 'provisioningConfig' property specifies the configuration used to provision integrations.
$ref: './ProvisioningConfig.yaml'
attributes:
description: Attributes of the Service Desk integration. Validation constraints enforced by the implementation.
description: Service Desk integration's attributes. Validation constraints enforced by the implementation.
type: object
additionalProperties: true
example: {
Expand Down

0 comments on commit cb4d0d3

Please sign in to comment.