mirror of
https://github.com/LukeHagar/api-specs.git
synced 2025-12-06 04:19:09 +00:00
Apply automatic changes
This commit is contained in:
committed by
github-actions[bot]
parent
cb420847ff
commit
b745b313a0
@@ -73674,7 +73674,11 @@
|
||||
"Identities"
|
||||
],
|
||||
"summary": "Process a list of identityIds",
|
||||
"description": "You could use this endpoint to:\n1. Calculate identity attributes, including applying or running any rules or transforms (e.g. calculate Lifecycle State at a point-in-time it's expected to change).\n2. Evaluate role assignments, leading to assignment of new roles and removal of existing roles.\n3. Enforce provisioning for any assigned accesses that haven't been fulfilled (e.g. failure due to source health).\n4. Recalculate manager relationships.\n5. Potentially clean-up identity processing errors, assuming the error has been resolved.\n\nTo learn more, refer to the [identity processing documentation](https://documentation.sailpoint.com/saas/help/setup/identity_processing.html).\n\nA token with ORG_ADMIN or HELPDESK authority is required to call this API.\n",
|
||||
"description": "This operation should not be used to schedule your own identity processing or to perform system wide identity refreshes. The system will use a combination of [event-based processing](https://documentation.sailpoint.com/saas/help/setup/identity_processing.html?h=process#event-based-processing) and [scheduled processing](https://documentation.sailpoint.com/saas/help/setup/identity_processing.html?h=process#scheduled-processing) that runs every day at 8:00 AM and 8:00 PM in the tenant's timezone to keep your identities synchronized. \n\nThis endpoint will perform the following tasks:\n1. Calculate identity attributes, including applying or running any rules or transforms (e.g. calculate Lifecycle State at a point-in-time it's expected to change).\n2. Evaluate role assignments, leading to assignment of new roles and removal of existing roles.\n3. Enforce provisioning for any assigned accesses that haven't been fulfilled (e.g. failure due to source health).\n4. Recalculate manager relationships.\n5. Potentially clean-up identity processing errors, assuming the error has been resolved.\n\nA token with ORG_ADMIN or HELPDESK authority is required to call this API.\n",
|
||||
"externalDocs": {
|
||||
"description": "Learn more about manually processing identities here",
|
||||
"url": "https://documentation.sailpoint.com/saas/help/setup/identity_processing.html"
|
||||
},
|
||||
"security": [
|
||||
{
|
||||
"UserContextAuth": [
|
||||
@@ -85253,7 +85257,11 @@
|
||||
"Identity Profiles"
|
||||
],
|
||||
"summary": "Process identities under profile",
|
||||
"description": "Process identities under the profile\n\nA token with ORG_ADMIN authority is required to call this API.",
|
||||
"description": "Process identities under the profile\nThis operation should not be used to schedule your own identity processing or to perform system wide identity refreshes. The system will use a combination of [event-based processing](https://documentation.sailpoint.com/saas/help/setup/identity_processing.html?h=process#event-based-processing) and [scheduled processing](https://documentation.sailpoint.com/saas/help/setup/identity_processing.html?h=process#scheduled-processing) that runs every day at 8:00 AM and 8:00 PM in the tenant's timezone to keep your identities synchronized. \nThis should only be run on identity profiles that have the `identityRefreshRequired` attribute set to `true`. If `identityRefreshRequired` is false, then there is no benefit to running this operation. Typically, this operation is performed when a change is made to the identity profile or its related lifecycle states that requires a refresh.\nThis operation will perform the following activities on all identities under the identity profile.\n1. Updates identity attribute according to the identity profile mappings. 2. Determines the identity's correct manager through manager correlation. 3. Updates the identity's access according to their assigned lifecycle state. 4. Updates the identity's access based on role assignment criteria.\nA token with ORG_ADMIN authority is required to call this API.",
|
||||
"externalDocs": {
|
||||
"description": "Learn more about manually processing identities here",
|
||||
"url": "https://documentation.sailpoint.com/saas/help/setup/identity_processing.html"
|
||||
},
|
||||
"parameters": [
|
||||
{
|
||||
"in": "path",
|
||||
|
||||
@@ -55774,16 +55774,19 @@ paths:
|
||||
- Identities
|
||||
summary: Process a list of identityIds
|
||||
description: |
|
||||
You could use this endpoint to:
|
||||
This operation should not be used to schedule your own identity processing or to perform system wide identity refreshes. The system will use a combination of [event-based processing](https://documentation.sailpoint.com/saas/help/setup/identity_processing.html?h=process#event-based-processing) and [scheduled processing](https://documentation.sailpoint.com/saas/help/setup/identity_processing.html?h=process#scheduled-processing) that runs every day at 8:00 AM and 8:00 PM in the tenant's timezone to keep your identities synchronized.
|
||||
|
||||
This endpoint will perform the following tasks:
|
||||
1. Calculate identity attributes, including applying or running any rules or transforms (e.g. calculate Lifecycle State at a point-in-time it's expected to change).
|
||||
2. Evaluate role assignments, leading to assignment of new roles and removal of existing roles.
|
||||
3. Enforce provisioning for any assigned accesses that haven't been fulfilled (e.g. failure due to source health).
|
||||
4. Recalculate manager relationships.
|
||||
5. Potentially clean-up identity processing errors, assuming the error has been resolved.
|
||||
|
||||
To learn more, refer to the [identity processing documentation](https://documentation.sailpoint.com/saas/help/setup/identity_processing.html).
|
||||
|
||||
A token with ORG_ADMIN or HELPDESK authority is required to call this API.
|
||||
externalDocs:
|
||||
description: Learn more about manually processing identities here
|
||||
url: 'https://documentation.sailpoint.com/saas/help/setup/identity_processing.html'
|
||||
security:
|
||||
- UserContextAuth:
|
||||
- 'idn:identity:manage'
|
||||
@@ -64228,8 +64231,14 @@ paths:
|
||||
summary: Process identities under profile
|
||||
description: |-
|
||||
Process identities under the profile
|
||||
|
||||
This operation should not be used to schedule your own identity processing or to perform system wide identity refreshes. The system will use a combination of [event-based processing](https://documentation.sailpoint.com/saas/help/setup/identity_processing.html?h=process#event-based-processing) and [scheduled processing](https://documentation.sailpoint.com/saas/help/setup/identity_processing.html?h=process#scheduled-processing) that runs every day at 8:00 AM and 8:00 PM in the tenant's timezone to keep your identities synchronized.
|
||||
This should only be run on identity profiles that have the `identityRefreshRequired` attribute set to `true`. If `identityRefreshRequired` is false, then there is no benefit to running this operation. Typically, this operation is performed when a change is made to the identity profile or its related lifecycle states that requires a refresh.
|
||||
This operation will perform the following activities on all identities under the identity profile.
|
||||
1. Updates identity attribute according to the identity profile mappings. 2. Determines the identity's correct manager through manager correlation. 3. Updates the identity's access according to their assigned lifecycle state. 4. Updates the identity's access based on role assignment criteria.
|
||||
A token with ORG_ADMIN authority is required to call this API.
|
||||
externalDocs:
|
||||
description: Learn more about manually processing identities here
|
||||
url: 'https://documentation.sailpoint.com/saas/help/setup/identity_processing.html'
|
||||
parameters:
|
||||
- in: path
|
||||
name: identity-profile-id
|
||||
|
||||
@@ -70337,7 +70337,11 @@
|
||||
"Identity Profiles"
|
||||
],
|
||||
"summary": "Process identities under profile",
|
||||
"description": "Process identities under the profile\n\nA token with ORG_ADMIN authority is required to call this API.",
|
||||
"description": "Process identities under the profile\nThis operation should not be used to schedule your own identity processing or to perform system wide identity refreshes. The system will use a combination of [event-based processing](https://documentation.sailpoint.com/saas/help/setup/identity_processing.html?h=process#event-based-processing) and [scheduled processing](https://documentation.sailpoint.com/saas/help/setup/identity_processing.html?h=process#scheduled-processing) that runs every day at 8:00 AM and 8:00 PM in the tenant's timezone to keep your identities synchronized. \nThis should only be run on identity profiles that have the `identityRefreshRequired` attribute set to `true`. If `identityRefreshRequired` is false, then there is no benefit to running this operation. Typically, this operation is performed when a change is made to the identity profile or its related lifecycle states that requires a refresh.\nThis operation will perform the following activities on all identities under the identity profile.\n1. Updates identity attribute according to the identity profile mappings. 2. Determines the identity's correct manager through manager correlation. 3. Updates the identity's access according to their assigned lifecycle state. 4. Updates the identity's access based on role assignment criteria.\nA token with ORG_ADMIN authority is required to call this API.",
|
||||
"externalDocs": {
|
||||
"description": "Learn more about manually processing identities here",
|
||||
"url": "https://documentation.sailpoint.com/saas/help/setup/identity_processing.html"
|
||||
},
|
||||
"parameters": [
|
||||
{
|
||||
"in": "path",
|
||||
|
||||
@@ -53635,8 +53635,14 @@ paths:
|
||||
summary: Process identities under profile
|
||||
description: |-
|
||||
Process identities under the profile
|
||||
|
||||
This operation should not be used to schedule your own identity processing or to perform system wide identity refreshes. The system will use a combination of [event-based processing](https://documentation.sailpoint.com/saas/help/setup/identity_processing.html?h=process#event-based-processing) and [scheduled processing](https://documentation.sailpoint.com/saas/help/setup/identity_processing.html?h=process#scheduled-processing) that runs every day at 8:00 AM and 8:00 PM in the tenant's timezone to keep your identities synchronized.
|
||||
This should only be run on identity profiles that have the `identityRefreshRequired` attribute set to `true`. If `identityRefreshRequired` is false, then there is no benefit to running this operation. Typically, this operation is performed when a change is made to the identity profile or its related lifecycle states that requires a refresh.
|
||||
This operation will perform the following activities on all identities under the identity profile.
|
||||
1. Updates identity attribute according to the identity profile mappings. 2. Determines the identity's correct manager through manager correlation. 3. Updates the identity's access according to their assigned lifecycle state. 4. Updates the identity's access based on role assignment criteria.
|
||||
A token with ORG_ADMIN authority is required to call this API.
|
||||
externalDocs:
|
||||
description: Learn more about manually processing identities here
|
||||
url: 'https://documentation.sailpoint.com/saas/help/setup/identity_processing.html'
|
||||
parameters:
|
||||
- in: path
|
||||
name: identity-profile-id
|
||||
|
||||
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
File diff suppressed because one or more lines are too long
Reference in New Issue
Block a user