diff --git a/dereferenced/deref-sailpoint-api.beta.json b/dereferenced/deref-sailpoint-api.beta.json
index 2e72c65..0e8bcf3 100644
--- a/dereferenced/deref-sailpoint-api.beta.json
+++ b/dereferenced/deref-sailpoint-api.beta.json
@@ -71,7 +71,7 @@
},
{
"name": "Certifications",
- "description": "Use this API to implement certification functionality.\nThis API provides specific functionality that improves an organization's ability to manage its certification process.\n\nA certification refers to IdentityNow's mechanism for reviewing a user's access to entitlements (sets of permissions) and approving or removing that access.\nThese certifications serve as a way of showing that a user's access has been reviewed and approved.\nMultiple certifications by different reviewers are often required to approve a user's access.\nA set of multiple certifications is called a certification campaign.\n\nFor example, an organization may use a Manager Certification as a way of showing that a user's access has been reviewed and approved by their manager, or if the certification is part of a campaign, that the user's access has been reviewed and approved by multiple managers.\nOnce this certification has been completed, IdentityNow would provision all the access the user needs, nothing more.\n\nThis API enables administrators and reviewers to get useful information about certifications at a high level, such as the reviewers involved, and at a more granular level, such as the permissions affected by changes to entitlements within those certifications.\nIt also provides the useful ability to reassign identities and items within certifications to other reviewers, rather than [reassigning the entire certifications themselves](https://developer.sailpoint.com/idn/api/beta/reassign-identity-certs-async).\n"
+ "description": "Use this API to implement certification functionality.\nThis API provides specific functionality that improves an organization's ability to manage its certification process.\n\nA certification refers to IdentityNow's mechanism for reviewing a user's access to entitlements (sets of permissions) and approving or removing that access.\nThese certifications serve as a way of showing that a user's access has been reviewed and approved.\nMultiple certifications by different reviewers are often required to approve a user's access.\nA set of multiple certifications is called a certification campaign.\n\nFor example, an organization may use a Manager Certification as a way of showing that a user's access has been reviewed and approved by their manager, or if the certification is part of a campaign, that the user's access has been reviewed and approved by multiple managers.\nOnce this certification has been completed, IdentityNow would provision all the access the user needs, nothing more.\n\nThis API enables administrators and reviewers to get useful information about certifications at a high level, such as the reviewers involved, and at a more granular level, such as the permissions affected by changes to entitlements within those certifications.\nIt also provides the useful ability to reassign identities and items within certifications to other reviewers, rather than [reassigning the entire certifications themselves](https://developer.sailpoint.com/idn/api/beta/submit-reassign-certs-async/).\n"
},
{
"name": "Connector Rule Management"
@@ -86,7 +86,7 @@
},
{
"name": "Custom Password Instructions",
- "description": "Use this API to implement custom password instruction functionality.\nWith this functionality in place, administrators can create custom password instructions to help users reset their passwords, change them, unlock their accounts, or recover their usernames.\nThis allows administrators to emphasize password policies or provide organization-specific instructions.\n\nAdministrators must first use [Update Password Org Config](https://developer.sailpoint.com/idn/api/beta/update-password-org-config) to set `customInstructionsEnabled` to `true`.\n\nOnce they have enabled custom instructions, they can use [Create Custom Password Instructions](https://developer.sailpoint.com/idn/api/beta/create-custom-password-instructions) to create custom page content for the specific pageId they select.\n\nFor example, an administrator can use the pageId forget-username:user-email to set the custom text for the case when users forget their usernames and must enter their emails.\n\nRefer to [Creating Custom Instruction Text](https://documentation.sailpoint.com/saas/help/pwd/pwd_reset.html#creating-custom-instruction-text) for more information about creating custom password instructions.\n"
+ "description": "Use this API to implement custom password instruction functionality.\nWith this functionality in place, administrators can create custom password instructions to help users reset their passwords, change them, unlock their accounts, or recover their usernames.\nThis allows administrators to emphasize password policies or provide organization-specific instructions.\n\nAdministrators must first use [Update Password Org Config](https://developer.sailpoint.com/idn/api/beta/put-password-org-config) to set `customInstructionsEnabled` to `true`.\n\nOnce they have enabled custom instructions, they can use [Create Custom Password Instructions](https://developer.sailpoint.com/idn/api/beta/create-custom-password-instructions) to create custom page content for the specific pageId they select.\n\nFor example, an administrator can use the pageId forget-username:user-email to set the custom text for the case when users forget their usernames and must enter their emails.\n\nRefer to [Creating Custom Instruction Text](https://documentation.sailpoint.com/saas/help/pwd/pwd_reset.html#creating-custom-instruction-text) for more information about creating custom password instructions.\n"
},
{
"name": "Entitlements",
@@ -192,7 +192,7 @@
},
{
"name": "Roles",
- "description": "Use this API to implement and customize role functionality.\nWith this functionality in place, administrators can create roles and configure them for use throughout IdentityNow.\nIdentityNow can use established criteria to automatically assign the roles to qualified users. This enables users to get all the access they need quickly and securely and administrators to spend their time on other tasks.\n\nEntitlements represent the most granular level of access in IdentityNow.\nAccess profiles represent the next level and often group entitlements.\nRoles represent the broadest level of access and often group access profiles.\n\nFor example, an Active Directory source in IdentityNow can have multiple entitlements: the first, 'Employees,' may represent the access all employees have at the organization, and a second, 'Developers,' may represent the access all developers have at the organization.\n\nAn administrator can then create a broader set of access in the form of an access profile, 'AD Developers' grouping the 'Employees' entitlement with the 'Developers' entitlement.\n\nAn administrator can then create an even broader set of access in the form of a role grouping the 'AD Developers' access profile with another profile, 'GitHub Developers,' grouping entitlements for the GitHub source.\n\nWhen users only need Active Directory employee access, they can request access to the 'Employees' entitlement.\n\nWhen users need both Active Directory employee and developer access, they can request access to the 'AD Developers' access profile.\n\nWhen users need both the 'AD Developers' access profile and the 'GitHub Developers' access profile, they can request access to the role grouping both.\n\nRoles often represent positions within organizations.\nFor example, an organization's accountant can access all the tools the organization's accountants need with the 'Accountant' role.\nIf the accountant switches to engineering, a qualified member of the organization can quickly revoke the accountant's 'Accountant' access and grant access to the 'Engineer' role instead, granting access to all the tools the organization's engineers need.\n\nIn IdentityNow, adminstrators can use the Access drop-down menu and select Roles to view, configure, and delete existing roles, as well as create new ones.\nAdministrators can enable and disable the role, and they can also make the following configurations:\n\n- Manage Access: Manage the role's access by adding or removing access profiles.\n\n- Define Assignment: Define the criteria IdentityNow uses to assign the role to identities.\nUse the first option, 'Standard Criteria,' to provide specific criteria for assignment like specific account attributes, entitlements, or identity attributes.\nUse the second, 'Identity List,' to specify the identities for assignment.\n\n- Access Requests: Configure roles to be requestable and establish an approval process for any requests that the role be granted or revoked.\nDo not configure a role to be requestable without establishing a secure access request approval process for that role first.\n\nRefer to [Working with Roles](https://documentation.sailpoint.com/saas/help/provisioning/roles.html) for more information about roles.\n"
+ "description": "Use this API to implement and customize role functionality.\nWith this functionality in place, administrators can create roles and configure them for use throughout IdentityNow.\nIdentityNow can use established criteria to automatically assign the roles to qualified users. This enables users to get all the access they need quickly and securely and administrators to spend their time on other tasks.\n\nEntitlements represent the most granular level of access in IdentityNow.\nAccess profiles represent the next level and often group entitlements.\nRoles represent the broadest level of access and often group access profiles.\n\nFor example, an Active Directory source in IdentityNow can have multiple entitlements: the first, 'Employees,' may represent the access all employees have at the organization, and a second, 'Developers,' may represent the access all developers have at the organization.\n\nAn administrator can then create a broader set of access in the form of an access profile, 'AD Developers' grouping the 'Employees' entitlement with the 'Developers' entitlement.\n\nAn administrator can then create an even broader set of access in the form of a role grouping the 'AD Developers' access profile with another profile, 'GitHub Developers,' grouping entitlements for the GitHub source.\n\nWhen users only need Active Directory employee access, they can request access to the 'Employees' entitlement.\n\nWhen users need both Active Directory employee and developer access, they can request access to the 'AD Developers' access profile.\n\nWhen users need both the 'AD Developers' access profile and the 'GitHub Developers' access profile, they can request access to the role grouping both.\n\nRoles often represent positions within organizations.\nFor example, an organization's accountant can access all the tools the organization's accountants need with the 'Accountant' role.\nIf the accountant switches to engineering, a qualified member of the organization can quickly revoke the accountant's 'Accountant' access and grant access to the 'Engineer' role instead, granting access to all the tools the organization's engineers need.\n\nIn IdentityNow, adminstrators can use the Access drop-down menu and select Roles to view, configure, and delete existing roles, as well as create new ones.\nAdministrators can enable and disable the role, and they can also make the following configurations:\n\n- Manage Access: Manage the role's access by adding or removing access profiles.\n\n- Define Assignment: Define the criteria IdentityNow uses to assign the role to identities.\nUse the first option, 'Standard Criteria,' to provide specific criteria for assignment like specific account attributes, entitlements, or identity attributes.\nUse the second, 'Identity List,' to specify the identities for assignment.\n\n- Access Requests: Configure roles to be requestable and establish an approval process for any requests that the role be granted or revoked.\nDo not configure a role to be requestable without establishing a secure access request approval process for that role first.\n\nRefer to [Working with Roles](https://documentation.sailpoint.com/saas/help/access/roles.html) for more information about roles.\n"
},
{
"name": "Search Attribute Configuration"
@@ -237,7 +237,7 @@
},
{
"name": "Triggers",
- "description": "Event Triggers provide real-time updates to changes in IdentityNow so you can take action as soon as an event occurs, rather than poll an API endpoint for updates. IdentityNow provides a user interface within the admin console to create and manage trigger subscriptions. These endpoints allow for programatically creating and managing trigger subscriptions.\n\nThere are two types of event triggers:\n * `FIRE_AND_FORGET`: This trigger type will send a payload to each subscriber without needing a response. Each trigger of this type has a limit of **50 subscriptions**.\n * `REQUEST_RESPONSE`: This trigger type will send a payload to a subscriber and expect a response back. Each trigger of this type may only have **one subscription**.\n\n## Available Event Triggers\nProduction ready event triggers that are available in all tenants.\n\n| Name | ID | Type | Trigger condition |\n|-|-|-|-|\n| [Access Request Dynamic Approval](https://developer.sailpoint.com/idn/docs/event-triggers/triggers/access-request-dynamic-approval) | idn:access-request-dynamic-approver | REQUEST_RESPONSE |After an access request is submitted. Expects the subscriber to respond with the ID of an identity or workgroup to add to the approval workflow. |\n| [Access Request Decision](https://developer.sailpoint.com/idn/docs/event-triggers/triggers/access-request-decision) | idn:access-request-post-approval | FIRE_AND_FORGET | After an access request is approved. |\n| [Access Request Submitted](https://developer.sailpoint.com/idn/docs/event-triggers/triggers/access-request-submitted) | idn:access-request-pre-approval | REQUEST_RESPONSE | After an access request is submitted. Expects the subscriber to respond with an approval decision. |\n| [Account Aggregation Completed](https://developer.sailpoint.com/idn/docs/event-triggers/triggers/account-aggregation-completed) | idn:account-aggregation-completed | FIRE_AND_FORGET | After an account aggregation completed, terminated, failed. |\n| Account Attributes Changed | idn:account-attributes-changed | FIRE_AND_FORGET | After an account aggregation, and one or more account attributes have changed. |\n| Account Correlated | idn:account-correlated | FIRE_AND_FORGET | After an account is added to an identity. |\n| Accounts Collected for Aggregation | idn:aggregation-accounts-collected | FIRE_AND_FORGET | New, changed, and deleted accounts have been gathered during an aggregation and are being processed. |\n| Account Uncorrelated | idn:account-uncorrelated | FIRE_AND_FORGET | After an account is removed from an identity. |\n| Campaign Activated | idn:campaign-activated | FIRE_AND_FORGET | After a campaign is activated. |\n| Campaign Ended | idn:campaign-ended | FIRE_AND_FORGET | After a campaign ends. |\n| Campaign Generated | idn:campaign-generated | FIRE_AND_FORGET | After a campaign finishes generating. |\n| Certification Signed Off | idn:certification-signed-off | FIRE_AND_FORGET | After a certification is signed off by its reviewer. |\n| [Identity Attributes Changed](https://developer.sailpoint.com/idn/docs/event-triggers/triggers/account-aggregation-completed) | idn:identity-attributes-changed | FIRE_AND_FORGET | After One or more identity attributes changed. |\n| [Identity Created](https://developer.sailpoint.com/idn/docs/event-triggers/triggers/identity-created) | idn:identity-created | FIRE_AND_FORGET | After an identity is created. |\n| [Provisioning Action Completed](https://developer.sailpoint.com/idn/docs/event-triggers/triggers/provisioning-action-completed) | idn:post-provisioning | FIRE_AND_FORGET | After a provisioning action completed on a source. |\n| [Scheduled Search](https://developer.sailpoint.com/idn/docs/event-triggers/triggers/scheduled-search) | idn:saved-search-complete | FIRE_AND_FORGET | After a scheduled search completed. |\n| [Source Created](https://developer.sailpoint.com/idn/docs/event-triggers/triggers/source-created) | idn:source-created | FIRE_AND_FORGET | After a source is created. |\n| [Source Deleted](https://developer.sailpoint.com/idn/docs/event-triggers/triggers/source-deleted) | idn:source-deleted | FIRE_AND_FORGET | After a source is deleted. |\n| [Source Updated](https://developer.sailpoint.com/idn/docs/event-triggers/triggers/source-updated) | idn:source-updated | FIRE_AND_FORGET | After configuration changes have been made to a source. |\n| [VA Cluster Status Change](https://developer.sailpoint.com/idn/docs/event-triggers/triggers/va-cluster-status-change) | idn:va-cluster-status-change | FIRE_AND_FORGET | After the status of a VA cluster has changed. |\n\n## Early Access Event Triggers\nTriggers that are in-development and not ready for production use. Please contact support to enable these triggers in your tenant.\n\n| Name | ID | Type | Trigger condition |\n|-|-|-|-|\n| [Identity Deleted](https://developer.sailpoint.com/idn/docs/event-triggers/triggers/identity-deleted) | idn:identity-deleted | FIRE_AND_FORGET | After an identity is deleted. |\n| [Source Account Created](https://developer.sailpoint.com/idn/docs/event-triggers/triggers/source-account-created) | idn:source-account-created | FIRE_AND_FORGET | After a source account is created. |\n| [Source Account Deleted](https://developer.sailpoint.com/idn/docs/event-triggers/triggers/source-account-deleted) | idn:source-account-deleted | FIRE_AND_FORGET | After a source account is deleted. |\n| [Source Account Updated](https://developer.sailpoint.com/idn/docs/event-triggers/triggers/source-account-updated) | idn:source-account-updated | FIRE_AND_FORGET | After a source account is changed. |\n\nRefer to [Event Triggers](https://developer.sailpoint.com/idn/docs/event-triggers/) for more information about event triggers.\n"
+ "description": "Event Triggers provide real-time updates to changes in IdentityNow so you can take action as soon as an event occurs, rather than poll an API endpoint for updates. IdentityNow provides a user interface within the admin console to create and manage trigger subscriptions. These endpoints allow for programatically creating and managing trigger subscriptions.\n\nThere are two types of event triggers:\n * `FIRE_AND_FORGET`: This trigger type will send a payload to each subscriber without needing a response. Each trigger of this type has a limit of **50 subscriptions**.\n * `REQUEST_RESPONSE`: This trigger type will send a payload to a subscriber and expect a response back. Each trigger of this type may only have **one subscription**.\n\n## Available Event Triggers\nProduction ready event triggers that are available in all tenants.\n\n| Name | ID | Type | Trigger condition |\n|-|-|-|-|\n| [Access Request Dynamic Approval](https://developer.sailpoint.com/idn/docs/event-triggers/triggers/access-request-dynamic-approval) | idn:access-request-dynamic-approver | REQUEST_RESPONSE |After an access request is submitted. Expects the subscriber to respond with the ID of an identity or workgroup to add to the approval workflow. |\n| [Access Request Decision](https://developer.sailpoint.com/idn/docs/event-triggers/triggers/access-request-decision) | idn:access-request-post-approval | FIRE_AND_FORGET | After an access request is approved. |\n| [Access Request Submitted](https://developer.sailpoint.com/idn/docs/event-triggers/triggers/access-request-submitted) | idn:access-request-pre-approval | REQUEST_RESPONSE | After an access request is submitted. Expects the subscriber to respond with an approval decision. |\n| [Account Aggregation Completed](https://developer.sailpoint.com/idn/docs/event-triggers/triggers/account-aggregation-completed) | idn:account-aggregation-completed | FIRE_AND_FORGET | After an account aggregation completed, terminated, failed. |\n| Account Attributes Changed | idn:account-attributes-changed | FIRE_AND_FORGET | After an account aggregation, and one or more account attributes have changed. |\n| Account Correlated | idn:account-correlated | FIRE_AND_FORGET | After an account is added to an identity. |\n| Accounts Collected for Aggregation | idn:aggregation-accounts-collected | FIRE_AND_FORGET | New, changed, and deleted accounts have been gathered during an aggregation and are being processed. |\n| Account Uncorrelated | idn:account-uncorrelated | FIRE_AND_FORGET | After an account is removed from an identity. |\n| Campaign Activated | idn:campaign-activated | FIRE_AND_FORGET | After a campaign is activated. |\n| Campaign Ended | idn:campaign-ended | FIRE_AND_FORGET | After a campaign ends. |\n| Campaign Generated | idn:campaign-generated | FIRE_AND_FORGET | After a campaign finishes generating. |\n| Certification Signed Off | idn:certification-signed-off | FIRE_AND_FORGET | After a certification is signed off by its reviewer. |\n| [Identity Attributes Changed](https://developer.sailpoint.com/idn/docs/event-triggers/triggers/account-aggregation-completed) | idn:identity-attributes-changed | FIRE_AND_FORGET | After One or more identity attributes changed. |\n| [Identity Created](https://developer.sailpoint.com/idn/docs/event-triggers/triggers/identity-created) | idn:identity-created | FIRE_AND_FORGET | After an identity is created. |\n| [Provisioning Action Completed](https://developer.sailpoint.com/idn/docs/event-triggers/triggers/provisioning-completed) | idn:post-provisioning | FIRE_AND_FORGET | After a provisioning action completed on a source. |\n| [Scheduled Search](https://developer.sailpoint.com/idn/docs/event-triggers/triggers/scheduled-search) | idn:saved-search-complete | FIRE_AND_FORGET | After a scheduled search completed. |\n| [Source Created](https://developer.sailpoint.com/idn/docs/event-triggers/triggers/source-created) | idn:source-created | FIRE_AND_FORGET | After a source is created. |\n| [Source Deleted](https://developer.sailpoint.com/idn/docs/event-triggers/triggers/source-deleted) | idn:source-deleted | FIRE_AND_FORGET | After a source is deleted. |\n| [Source Updated](https://developer.sailpoint.com/idn/docs/event-triggers/triggers/source-updated) | idn:source-updated | FIRE_AND_FORGET | After configuration changes have been made to a source. |\n| [VA Cluster Status Change](https://developer.sailpoint.com/idn/docs/event-triggers/triggers/va-cluster-status-change) | idn:va-cluster-status-change | FIRE_AND_FORGET | After the status of a VA cluster has changed. |\n\n## Early Access Event Triggers\nTriggers that are in-development and not ready for production use. Please contact support to enable these triggers in your tenant.\n\n| Name | ID | Type | Trigger condition |\n|-|-|-|-|\n| [Identity Deleted](https://developer.sailpoint.com/idn/docs/event-triggers/triggers/identity-deleted) | idn:identity-deleted | FIRE_AND_FORGET | After an identity is deleted. |\n| [Source Account Created](https://developer.sailpoint.com/idn/docs/event-triggers/triggers/source-account-created) | idn:source-account-created | FIRE_AND_FORGET | After a source account is created. |\n| [Source Account Deleted](https://developer.sailpoint.com/idn/docs/event-triggers/triggers/source-account-deleted) | idn:source-account-deleted | FIRE_AND_FORGET | After a source account is deleted. |\n| [Source Account Updated](https://developer.sailpoint.com/idn/docs/event-triggers/triggers/source-account-updated) | idn:source-account-updated | FIRE_AND_FORGET | After a source account is changed. |\n\nRefer to [Event Triggers](https://developer.sailpoint.com/idn/docs/event-triggers/) for more information about event triggers.\n"
},
{
"name": "Work Items",
@@ -7854,7 +7854,7 @@
"Access Requests"
],
"summary": "Close Access Request",
- "description": "This endpoint closes access requests that are stuck in a pending state. It can be used throughout a request's lifecycle (even after the approval state, unlike Cancel Access Request). A token with ORG_ADMIN authority is required.\n\nTo find pending access requests via the UI, navigate to Search and use this query: status: Pending AND \"Access Request\". Use the Column Chooser to select \"Tracking Number,\" and the Download button to export a CSV containing the Tracking Numbers.\n\nTo find pending access requests via the API, use List Account Activities.\n\nInput the ids from either source\n\nTo track the status of endpoint requests, navigate to Search and use this query: name:\"Close Identity Requests\". Search will include \"Close Identity Requests Started\" audits when requests are initiated, and \"Close Identity Requests Completed\" audits when requests are completed. The completion audit will list the Identity Request IDs that finished in error.\n\nThis API triggers the Provisioning Action Completed event trigger for each access request that is closed.\n",
+ "description": "This endpoint closes access requests that are stuck in a pending state. It can be used throughout a request's lifecycle even after the approval state, unlike the [Cancel Access Request endpoint](https://developer.sailpoint.com/idn/api/v3/cancel-access-request/). A token with ORG_ADMIN authority is required.\n\nTo find pending access requests with the UI, navigate to Search and use this query: status: Pending AND \"Access Request\". Use the Column Chooser to select 'Tracking Number', and use the 'Download' button to export a CSV containing the tracking numbers.\n\nTo find pending access requests with the API, use the [List Account Activities endpoint](https://developer.sailpoint.com/idn/api/v3/list-account-activities/).\n\nInput the IDs from either source.\n\nTo track the status of endpoint requests, navigate to Search and use this query: name:\"Close Identity Requests\". Search will include \"Close Identity Requests Started\" audits when requests are initiated and \"Close Identity Requests Completed\" audits when requests are completed. The completion audit will list the identity request IDs that finished in error.\n\nThis API triggers the [Provisioning Completed event trigger](https://developer.sailpoint.com/idn/docs/event-triggers/triggers/provisioning-completed/) for each access request that is closed.\n",
"requestBody": {
"required": true,
"content": {
diff --git a/dereferenced/deref-sailpoint-api.beta.yaml b/dereferenced/deref-sailpoint-api.beta.yaml
index f27abf3..eb3cd7c 100644
--- a/dereferenced/deref-sailpoint-api.beta.yaml
+++ b/dereferenced/deref-sailpoint-api.beta.yaml
@@ -258,7 +258,7 @@ tags:
Once this certification has been completed, IdentityNow would provision all the access the user needs, nothing more.
This API enables administrators and reviewers to get useful information about certifications at a high level, such as the reviewers involved, and at a more granular level, such as the permissions affected by changes to entitlements within those certifications.
- It also provides the useful ability to reassign identities and items within certifications to other reviewers, rather than [reassigning the entire certifications themselves](https://developer.sailpoint.com/idn/api/beta/reassign-identity-certs-async).
+ It also provides the useful ability to reassign identities and items within certifications to other reviewers, rather than [reassigning the entire certifications themselves](https://developer.sailpoint.com/idn/api/beta/submit-reassign-certs-async/).
- name: Connector Rule Management
- name: Connectors
description: |
@@ -292,7 +292,7 @@ tags:
With this functionality in place, administrators can create custom password instructions to help users reset their passwords, change them, unlock their accounts, or recover their usernames.
This allows administrators to emphasize password policies or provide organization-specific instructions.
- Administrators must first use [Update Password Org Config](https://developer.sailpoint.com/idn/api/beta/update-password-org-config) to set `customInstructionsEnabled` to `true`.
+ Administrators must first use [Update Password Org Config](https://developer.sailpoint.com/idn/api/beta/put-password-org-config) to set `customInstructionsEnabled` to `true`.
Once they have enabled custom instructions, they can use [Create Custom Password Instructions](https://developer.sailpoint.com/idn/api/beta/create-custom-password-instructions) to create custom page content for the specific pageId they select.
@@ -666,7 +666,7 @@ tags:
- Access Requests: Configure roles to be requestable and establish an approval process for any requests that the role be granted or revoked.
Do not configure a role to be requestable without establishing a secure access request approval process for that role first.
- Refer to [Working with Roles](https://documentation.sailpoint.com/saas/help/provisioning/roles.html) for more information about roles.
+ Refer to [Working with Roles](https://documentation.sailpoint.com/saas/help/access/roles.html) for more information about roles.
- name: Search Attribute Configuration
- name: Segments
description: |
@@ -858,7 +858,7 @@ tags:
| Certification Signed Off | idn:certification-signed-off | FIRE_AND_FORGET | After a certification is signed off by its reviewer. |
| [Identity Attributes Changed](https://developer.sailpoint.com/idn/docs/event-triggers/triggers/account-aggregation-completed) | idn:identity-attributes-changed | FIRE_AND_FORGET | After One or more identity attributes changed. |
| [Identity Created](https://developer.sailpoint.com/idn/docs/event-triggers/triggers/identity-created) | idn:identity-created | FIRE_AND_FORGET | After an identity is created. |
- | [Provisioning Action Completed](https://developer.sailpoint.com/idn/docs/event-triggers/triggers/provisioning-action-completed) | idn:post-provisioning | FIRE_AND_FORGET | After a provisioning action completed on a source. |
+ | [Provisioning Action Completed](https://developer.sailpoint.com/idn/docs/event-triggers/triggers/provisioning-completed) | idn:post-provisioning | FIRE_AND_FORGET | After a provisioning action completed on a source. |
| [Scheduled Search](https://developer.sailpoint.com/idn/docs/event-triggers/triggers/scheduled-search) | idn:saved-search-complete | FIRE_AND_FORGET | After a scheduled search completed. |
| [Source Created](https://developer.sailpoint.com/idn/docs/event-triggers/triggers/source-created) | idn:source-created | FIRE_AND_FORGET | After a source is created. |
| [Source Deleted](https://developer.sailpoint.com/idn/docs/event-triggers/triggers/source-deleted) | idn:source-deleted | FIRE_AND_FORGET | After a source is deleted. |
@@ -6726,17 +6726,17 @@ paths:
- Access Requests
summary: Close Access Request
description: |
- This endpoint closes access requests that are stuck in a pending state. It can be used throughout a request's lifecycle (even after the approval state, unlike Cancel Access Request). A token with ORG_ADMIN authority is required.
+ This endpoint closes access requests that are stuck in a pending state. It can be used throughout a request's lifecycle even after the approval state, unlike the [Cancel Access Request endpoint](https://developer.sailpoint.com/idn/api/v3/cancel-access-request/). A token with ORG_ADMIN authority is required.
- To find pending access requests via the UI, navigate to Search and use this query: status: Pending AND "Access Request". Use the Column Chooser to select "Tracking Number," and the Download button to export a CSV containing the Tracking Numbers.
+ To find pending access requests with the UI, navigate to Search and use this query: status: Pending AND "Access Request". Use the Column Chooser to select 'Tracking Number', and use the 'Download' button to export a CSV containing the tracking numbers.
- To find pending access requests via the API, use List Account Activities.
+ To find pending access requests with the API, use the [List Account Activities endpoint](https://developer.sailpoint.com/idn/api/v3/list-account-activities/).
- Input the ids from either source
+ Input the IDs from either source.
- To track the status of endpoint requests, navigate to Search and use this query: name:"Close Identity Requests". Search will include "Close Identity Requests Started" audits when requests are initiated, and "Close Identity Requests Completed" audits when requests are completed. The completion audit will list the Identity Request IDs that finished in error.
+ To track the status of endpoint requests, navigate to Search and use this query: name:"Close Identity Requests". Search will include "Close Identity Requests Started" audits when requests are initiated and "Close Identity Requests Completed" audits when requests are completed. The completion audit will list the identity request IDs that finished in error.
- This API triggers the Provisioning Action Completed event trigger for each access request that is closed.
+ This API triggers the [Provisioning Completed event trigger](https://developer.sailpoint.com/idn/docs/event-triggers/triggers/provisioning-completed/) for each access request that is closed.
requestBody:
required: true
content:
diff --git a/dereferenced/deref-sailpoint-api.v3.json b/dereferenced/deref-sailpoint-api.v3.json
index 23947a4..c715a25 100644
--- a/dereferenced/deref-sailpoint-api.v3.json
+++ b/dereferenced/deref-sailpoint-api.v3.json
@@ -135,7 +135,7 @@
},
{
"name": "Roles",
- "description": "Use this API to implement and customize role functionality.\nWith this functionality in place, administrators can create roles and configure them for use throughout IdentityNow. \nIdentityNow can use established criteria to automatically assign the roles to qualified users. This enables users to get all the access they need quickly and securely and administrators to spend their time on other tasks.\n\nEntitlements represent the most granular level of access in IdentityNow. \nAccess profiles represent the next level and often group entitlements. \nRoles represent the broadest level of access and often group access profiles. \n\nFor example, an Active Directory source in IdentityNow can have multiple entitlements: the first, 'Employees,' may represent the access all employees have at the organization, and a second, 'Developers,' may represent the access all developers have at the organization.\n\nAn administrator can then create a broader set of access in the form of an access profile, 'AD Developers' grouping the 'Employees' entitlement with the 'Developers' entitlement.\n\nAn administrator can then create an even broader set of access in the form of a role grouping the 'AD Developers' access profile with another profile, 'GitHub Developers,' grouping entitlements for the GitHub source.\n\nWhen users only need Active Directory employee access, they can request access to the 'Employees' entitlement.\n\nWhen users need both Active Directory employee and developer access, they can request access to the 'AD Developers' access profile.\n\nWhen users need both the 'AD Developers' access profile and the 'GitHub Developers' access profile, they can request access to the role grouping both. \n\nRoles often represent positions within organizations. \nFor example, an organization's accountant can access all the tools the organization's accountants need with the 'Accountant' role. \nIf the accountant switches to engineering, a qualified member of the organization can quickly revoke the accountant's 'Accountant' access and grant access to the 'Engineer' role instead, granting access to all the tools the organization's engineers need.\n\nIn IdentityNow, adminstrators can use the Access drop-down menu and select Roles to view, configure, and delete existing roles, as well as create new ones. \nAdministrators can enable and disable the role, and they can also make the following configurations: \n\n- Manage Access: Manage the role's access by adding or removing access profiles.\n\n- Define Assignment: Define the criteria IdentityNow uses to assign the role to identities. \nUse the first option, 'Standard Criteria,' to provide specific criteria for assignment like specific account attributes, entitlements, or identity attributes. \nUse the second, 'Identity List,' to specify the identities for assignment.\n\n- Access Requests: Configure roles to be requestable and establish an approval process for any requests that the role be granted or revoked. \nDo not configure a role to be requestable without establishing a secure access request approval process for that role first. \n\nRefer to [Working with Roles](https://documentation.sailpoint.com/saas/help/provisioning/roles.html) for more information about roles.\n"
+ "description": "Use this API to implement and customize role functionality.\nWith this functionality in place, administrators can create roles and configure them for use throughout IdentityNow. \nIdentityNow can use established criteria to automatically assign the roles to qualified users. This enables users to get all the access they need quickly and securely and administrators to spend their time on other tasks.\n\nEntitlements represent the most granular level of access in IdentityNow. \nAccess profiles represent the next level and often group entitlements. \nRoles represent the broadest level of access and often group access profiles. \n\nFor example, an Active Directory source in IdentityNow can have multiple entitlements: the first, 'Employees,' may represent the access all employees have at the organization, and a second, 'Developers,' may represent the access all developers have at the organization.\n\nAn administrator can then create a broader set of access in the form of an access profile, 'AD Developers' grouping the 'Employees' entitlement with the 'Developers' entitlement.\n\nAn administrator can then create an even broader set of access in the form of a role grouping the 'AD Developers' access profile with another profile, 'GitHub Developers,' grouping entitlements for the GitHub source.\n\nWhen users only need Active Directory employee access, they can request access to the 'Employees' entitlement.\n\nWhen users need both Active Directory employee and developer access, they can request access to the 'AD Developers' access profile.\n\nWhen users need both the 'AD Developers' access profile and the 'GitHub Developers' access profile, they can request access to the role grouping both. \n\nRoles often represent positions within organizations. \nFor example, an organization's accountant can access all the tools the organization's accountants need with the 'Accountant' role. \nIf the accountant switches to engineering, a qualified member of the organization can quickly revoke the accountant's 'Accountant' access and grant access to the 'Engineer' role instead, granting access to all the tools the organization's engineers need.\n\nIn IdentityNow, adminstrators can use the Access drop-down menu and select Roles to view, configure, and delete existing roles, as well as create new ones. \nAdministrators can enable and disable the role, and they can also make the following configurations: \n\n- Manage Access: Manage the role's access by adding or removing access profiles.\n\n- Define Assignment: Define the criteria IdentityNow uses to assign the role to identities. \nUse the first option, 'Standard Criteria,' to provide specific criteria for assignment like specific account attributes, entitlements, or identity attributes. \nUse the second, 'Identity List,' to specify the identities for assignment.\n\n- Access Requests: Configure roles to be requestable and establish an approval process for any requests that the role be granted or revoked. \nDo not configure a role to be requestable without establishing a secure access request approval process for that role first. \n\nRefer to [Working with Roles](https://documentation.sailpoint.com/saas/help/access/roles.html) for more information about roles.\n"
},
{
"name": "Saved Search",
diff --git a/dereferenced/deref-sailpoint-api.v3.yaml b/dereferenced/deref-sailpoint-api.v3.yaml
index bcc37f4..f3aa2ce 100644
--- a/dereferenced/deref-sailpoint-api.v3.yaml
+++ b/dereferenced/deref-sailpoint-api.v3.yaml
@@ -589,7 +589,7 @@ tags:
- Access Requests: Configure roles to be requestable and establish an approval process for any requests that the role be granted or revoked.
Do not configure a role to be requestable without establishing a secure access request approval process for that role first.
- Refer to [Working with Roles](https://documentation.sailpoint.com/saas/help/provisioning/roles.html) for more information about roles.
+ Refer to [Working with Roles](https://documentation.sailpoint.com/saas/help/access/roles.html) for more information about roles.
- name: Saved Search
description: |
Use this API to implement saved search functionality.
diff --git a/postman/collections/sailpoint-api-beta.json b/postman/collections/sailpoint-api-beta.json
index f3acbde..d5b43c5 100644
--- a/postman/collections/sailpoint-api-beta.json
+++ b/postman/collections/sailpoint-api-beta.json
@@ -5,7 +5,7 @@
"description": "Use this API to implement and customize access profile functionality.\nWith this functionality in place, administrators can create access profiles and configure them for use throughout IdentityNow, enabling users to get the access they need quickly and securely.\n\nAccess profiles group entitlements, which represent access rights on sources.\n\nFor example, an Active Directory source in IdentityNow can have multiple entitlements: the first, 'Employees,' may represent the access all employees have at the organization, and a second, 'Developers,' may represent the access all developers have at the organization.\n\nAn administrator can then create a broader set of access in the form of an access profile, 'AD Developers' grouping the 'Employees' entitlement with the 'Developers' entitlement.\n\nWhen users only need Active Directory employee access, they can request access to the 'Employees' entitlement.\n\nWhen users need both Active Directory employee and developer access, they can request access to the 'AD Developers' access profile.\n\nAccess profiles are the most important units of access in IdentityNow. IdentityNow uses access profiles in many features, including the following:\n\n- Provisioning: When you use the Provisioning Service, lifecycle states and roles both grant access to users in the form of access profiles.\n\n- Certifications: You can approve or revoke access profiles in certification campaigns, just like entitlements.\n\n- Access Requests: You can assign access profiles to applications, and when a user requests access to the app associated with an access profile and someone approves the request, access is granted to both the application and its associated access profile.\n\n- Roles: You can group one or more access profiles into a role to quickly assign access items based on an identity's role.\n\nIn IdentityNow, administrators can use the Access drop-down menu and select Access Profiles to view, configure, and delete existing access profiles, as well as create new ones.\nAdministrators can enable and disable an access profile, and they can also make the following configurations:\n\n- Manage Entitlements: Manage the profile's access by adding and removing entitlements.\n\n- Access Requests: Configure access profiles to be requestable and establish an approval process for any requests that the access profile be granted or revoked.\nDo not configure an access profile to be requestable without first establishing a secure access request approval process for the access profile.\n\n- Multiple Account Options: Define the logic IdentityNow uses to provision access to an identity with multiple accounts on the source.\n\nRefer to [Managing Access Profiles](https://documentation.sailpoint.com/saas/help/access/access-profiles.html) for more information about access profiles.\n",
"item": [
{
- "id": "c5b84629-d4f0-4c9c-a5d6-53933a8f3a78",
+ "id": "624b4f8a-3b5b-4c15-ad4b-d55b55641c3c",
"name": "List Access Profiles",
"request": {
"name": "List Access Profiles",
@@ -107,7 +107,7 @@
},
"response": [
{
- "id": "e9e93cad-9e96-4ac9-85ec-74c03d242465",
+ "id": "a4d05f36-06fb-406b-9a3b-87a9707ee9d2",
"name": "List of Access Profiles",
"originalRequest": {
"url": {
@@ -218,12 +218,12 @@
"value": "application/json"
}
],
- "body": "[\n {\n \"owner\": {\n \"type\": \"IDENTITY\",\n \"id\": \"\",\n \"name\": \"\"\n },\n \"name\": \"\",\n \"source\": {\n \"id\": \"\",\n \"type\": \"SOURCE\",\n \"name\": \"\"\n },\n \"id\": \"\",\n \"description\": \"\",\n \"created\": \"\",\n \"modified\": \"\",\n \"enabled\": \"\",\n \"entitlements\": [\n {\n \"type\": \"ENTITLEMENT\",\n \"id\": \"\",\n \"name\": \"\"\n },\n {\n \"type\": \"ENTITLEMENT\",\n \"id\": \"\",\n \"name\": \"\"\n }\n ],\n \"requestable\": \"\",\n \"accessRequestConfig\": {\n \"commentsRequired\": \"\",\n \"denialCommentsRequired\": \"\",\n \"approvalSchemes\": [\n {\n \"approverType\": \"APP_OWNER\",\n \"approverId\": \"\"\n },\n {\n \"approverType\": \"MANAGER\",\n \"approverId\": \"\"\n }\n ]\n },\n \"revocationRequestConfig\": {\n \"commentsRequired\": false,\n \"denialCommentsRequired\": false,\n \"approvalSchemes\": [\n {\n \"approverType\": \"OWNER\",\n \"approverId\": \"\"\n },\n {\n \"approverType\": \"MANAGER\",\n \"approverId\": \"\"\n }\n ]\n },\n \"segments\": [\n \"\",\n \"\"\n ],\n \"provisioningCriteria\": {\n \"operation\": \"HAS\",\n \"attribute\": \"\",\n \"value\": \"\",\n \"children\": [\n {\n \"operation\": \"OR\",\n \"attribute\": \"\",\n \"value\": \"\",\n \"children\": [\n {\n \"operation\": \"OR\",\n \"attribute\": \"\",\n \"value\": \"\"\n },\n {\n \"operation\": \"EQUALS\",\n \"attribute\": \"\",\n \"value\": \"\"\n }\n ]\n },\n {\n \"operation\": \"HAS\",\n \"attribute\": \"\",\n \"value\": \"\",\n \"children\": [\n {\n \"operation\": \"OR\",\n \"attribute\": \"\",\n \"value\": \"\"\n },\n {\n \"operation\": \"NOT_EQUALS\",\n \"attribute\": \"\",\n \"value\": \"\"\n }\n ]\n }\n ]\n }\n },\n {\n \"owner\": {\n \"type\": \"IDENTITY\",\n \"id\": \"\",\n \"name\": \"\"\n },\n \"name\": \"\",\n \"source\": {\n \"id\": \"\",\n \"type\": \"SOURCE\",\n \"name\": \"\"\n },\n \"id\": \"\",\n \"description\": \"\",\n \"created\": \"\",\n \"modified\": \"\",\n \"enabled\": \"\",\n \"entitlements\": [\n {\n \"type\": \"ENTITLEMENT\",\n \"id\": \"\",\n \"name\": \"\"\n },\n {\n \"type\": \"ENTITLEMENT\",\n \"id\": \"\",\n \"name\": \"\"\n }\n ],\n \"requestable\": \"\",\n \"accessRequestConfig\": {\n \"commentsRequired\": \"\",\n \"denialCommentsRequired\": \"\",\n \"approvalSchemes\": [\n {\n \"approverType\": \"GOVERNANCE_GROUP\",\n \"approverId\": \"\"\n },\n {\n \"approverType\": \"GOVERNANCE_GROUP\",\n \"approverId\": \"\"\n }\n ]\n },\n \"revocationRequestConfig\": {\n \"commentsRequired\": false,\n \"denialCommentsRequired\": false,\n \"approvalSchemes\": [\n {\n \"approverType\": \"OWNER\",\n \"approverId\": \"\"\n },\n {\n \"approverType\": \"MANAGER\",\n \"approverId\": \"\"\n }\n ]\n },\n \"segments\": [\n \"\",\n \"\"\n ],\n \"provisioningCriteria\": {\n \"operation\": \"OR\",\n \"attribute\": \"\",\n \"value\": \"\",\n \"children\": [\n {\n \"operation\": \"HAS\",\n \"attribute\": \"\",\n \"value\": \"\",\n \"children\": [\n {\n \"operation\": \"OR\",\n \"attribute\": \"\",\n \"value\": \"\"\n },\n {\n \"operation\": \"NOT_EQUALS\",\n \"attribute\": \"\",\n \"value\": \"\"\n }\n ]\n },\n {\n \"operation\": \"NOT_EQUALS\",\n \"attribute\": \"\",\n \"value\": \"\",\n \"children\": [\n {\n \"operation\": \"AND\",\n \"attribute\": \"\",\n \"value\": \"\"\n },\n {\n \"operation\": \"NOT_EQUALS\",\n \"attribute\": \"\",\n \"value\": \"\"\n }\n ]\n }\n ]\n }\n }\n]",
+ "body": "[\n {\n \"owner\": {\n \"type\": \"IDENTITY\",\n \"id\": \"\",\n \"name\": \"\"\n },\n \"name\": \"\",\n \"source\": {\n \"id\": \"\",\n \"type\": \"SOURCE\",\n \"name\": \"\"\n },\n \"id\": \"\",\n \"description\": \"\",\n \"created\": \"\",\n \"modified\": \"\",\n \"enabled\": \"\",\n \"entitlements\": [\n {\n \"type\": \"ENTITLEMENT\",\n \"id\": \"\",\n \"name\": \"\"\n },\n {\n \"type\": \"ENTITLEMENT\",\n \"id\": \"\",\n \"name\": \"\"\n }\n ],\n \"requestable\": \"\",\n \"accessRequestConfig\": {\n \"commentsRequired\": \"\",\n \"denialCommentsRequired\": \"\",\n \"approvalSchemes\": [\n {\n \"approverType\": \"APP_OWNER\",\n \"approverId\": \"\"\n },\n {\n \"approverType\": \"APP_OWNER\",\n \"approverId\": \"\"\n }\n ]\n },\n \"revocationRequestConfig\": {\n \"commentsRequired\": false,\n \"denialCommentsRequired\": false,\n \"approvalSchemes\": [\n {\n \"approverType\": \"APP_OWNER\",\n \"approverId\": \"\"\n },\n {\n \"approverType\": \"GOVERNANCE_GROUP\",\n \"approverId\": \"\"\n }\n ]\n },\n \"segments\": [\n \"\",\n \"\"\n ],\n \"provisioningCriteria\": {\n \"operation\": \"AND\",\n \"attribute\": \"\",\n \"value\": \"\",\n \"children\": [\n {\n \"operation\": \"AND\",\n \"attribute\": \"\",\n \"value\": \"\",\n \"children\": [\n {\n \"operation\": \"CONTAINS\",\n \"attribute\": \"\",\n \"value\": \"\"\n },\n {\n \"operation\": \"OR\",\n \"attribute\": \"\",\n \"value\": \"\"\n }\n ]\n },\n {\n \"operation\": \"HAS\",\n \"attribute\": \"\",\n \"value\": \"\",\n \"children\": [\n {\n \"operation\": \"AND\",\n \"attribute\": \"\",\n \"value\": \"\"\n },\n {\n \"operation\": \"CONTAINS\",\n \"attribute\": \"\",\n \"value\": \"\"\n }\n ]\n }\n ]\n }\n },\n {\n \"owner\": {\n \"type\": \"IDENTITY\",\n \"id\": \"\",\n \"name\": \"\"\n },\n \"name\": \"\",\n \"source\": {\n \"id\": \"\",\n \"type\": \"SOURCE\",\n \"name\": \"\"\n },\n \"id\": \"\",\n \"description\": \"\",\n \"created\": \"\",\n \"modified\": \"\",\n \"enabled\": \"\",\n \"entitlements\": [\n {\n \"type\": \"ENTITLEMENT\",\n \"id\": \"\",\n \"name\": \"\"\n },\n {\n \"type\": \"ENTITLEMENT\",\n \"id\": \"\",\n \"name\": \"\"\n }\n ],\n \"requestable\": \"\",\n \"accessRequestConfig\": {\n \"commentsRequired\": \"\",\n \"denialCommentsRequired\": \"\",\n \"approvalSchemes\": [\n {\n \"approverType\": \"OWNER\",\n \"approverId\": \"\"\n },\n {\n \"approverType\": \"GOVERNANCE_GROUP\",\n \"approverId\": \"\"\n }\n ]\n },\n \"revocationRequestConfig\": {\n \"commentsRequired\": false,\n \"denialCommentsRequired\": false,\n \"approvalSchemes\": [\n {\n \"approverType\": \"APP_OWNER\",\n \"approverId\": \"\"\n },\n {\n \"approverType\": \"MANAGER\",\n \"approverId\": \"\"\n }\n ]\n },\n \"segments\": [\n \"\",\n \"\"\n ],\n \"provisioningCriteria\": {\n \"operation\": \"CONTAINS\",\n \"attribute\": \"\",\n \"value\": \"\",\n \"children\": [\n {\n \"operation\": \"CONTAINS\",\n \"attribute\": \"\",\n \"value\": \"\",\n \"children\": [\n {\n \"operation\": \"EQUALS\",\n \"attribute\": \"\",\n \"value\": \"\"\n },\n {\n \"operation\": \"HAS\",\n \"attribute\": \"\",\n \"value\": \"\"\n }\n ]\n },\n {\n \"operation\": \"CONTAINS\",\n \"attribute\": \"\",\n \"value\": \"\",\n \"children\": [\n {\n \"operation\": \"OR\",\n \"attribute\": \"\",\n \"value\": \"\"\n },\n {\n \"operation\": \"OR\",\n \"attribute\": \"\",\n \"value\": \"\"\n }\n ]\n }\n ]\n }\n }\n]",
"cookie": [],
"_postman_previewlanguage": "json"
},
{
- "id": "06975499-4476-48e7-b6ac-f0dced03c29f",
+ "id": "162763ea-d125-4167-b229-6ea80aa5fcd3",
"name": "Client Error - Returned if the request body is invalid.",
"originalRequest": {
"url": {
@@ -334,12 +334,12 @@
"value": "application/json"
}
],
- "body": "{\n \"detailCode\": \"\",\n \"trackingId\": \"\",\n \"messages\": [\n {\n \"locale\": \"\",\n \"localeOrigin\": \"REQUEST\",\n \"text\": \"\"\n },\n {\n \"locale\": \"\",\n \"localeOrigin\": \"REQUEST\",\n \"text\": \"\"\n }\n ],\n \"causes\": [\n {\n \"locale\": \"\",\n \"localeOrigin\": \"DEFAULT\",\n \"text\": \"\"\n },\n {\n \"locale\": \"\",\n \"localeOrigin\": \"DEFAULT\",\n \"text\": \"\"\n }\n ]\n}",
+ "body": "{\n \"detailCode\": \"\",\n \"trackingId\": \"\",\n \"messages\": [\n {\n \"locale\": \"\",\n \"localeOrigin\": \"REQUEST\",\n \"text\": \"\"\n },\n {\n \"locale\": \"\",\n \"localeOrigin\": \"DEFAULT\",\n \"text\": \"\"\n }\n ],\n \"causes\": [\n {\n \"locale\": \"\",\n \"localeOrigin\": \"REQUEST\",\n \"text\": \"\"\n },\n {\n \"locale\": \"\",\n \"localeOrigin\": \"DEFAULT\",\n \"text\": \"\"\n }\n ]\n}",
"cookie": [],
"_postman_previewlanguage": "json"
},
{
- "id": "711d8b43-8657-4d74-baca-7369e8863a0e",
+ "id": "520e7805-62e8-4a9c-a968-f379165e72e8",
"name": "Unauthorized - Returned if there is no authorization header, or if the JWT token is expired.",
"originalRequest": {
"url": {
@@ -455,7 +455,7 @@
"_postman_previewlanguage": "json"
},
{
- "id": "18d261d1-ddcf-4d90-a971-667b07c07877",
+ "id": "e828fe81-bc96-46b0-9626-a189313274f5",
"name": "Forbidden - Returned if the user you are running as, doesn't have access to this end-point.",
"originalRequest": {
"url": {
@@ -566,12 +566,12 @@
"value": "application/json"
}
],
- "body": "{\n \"detailCode\": \"\",\n \"trackingId\": \"\",\n \"messages\": [\n {\n \"locale\": \"\",\n \"localeOrigin\": \"REQUEST\",\n \"text\": \"\"\n },\n {\n \"locale\": \"\",\n \"localeOrigin\": \"REQUEST\",\n \"text\": \"\"\n }\n ],\n \"causes\": [\n {\n \"locale\": \"\",\n \"localeOrigin\": \"DEFAULT\",\n \"text\": \"\"\n },\n {\n \"locale\": \"\",\n \"localeOrigin\": \"DEFAULT\",\n \"text\": \"\"\n }\n ]\n}",
+ "body": "{\n \"detailCode\": \"\",\n \"trackingId\": \"\",\n \"messages\": [\n {\n \"locale\": \"\",\n \"localeOrigin\": \"REQUEST\",\n \"text\": \"\"\n },\n {\n \"locale\": \"\",\n \"localeOrigin\": \"DEFAULT\",\n \"text\": \"\"\n }\n ],\n \"causes\": [\n {\n \"locale\": \"\",\n \"localeOrigin\": \"REQUEST\",\n \"text\": \"\"\n },\n {\n \"locale\": \"\",\n \"localeOrigin\": \"DEFAULT\",\n \"text\": \"\"\n }\n ]\n}",
"cookie": [],
"_postman_previewlanguage": "json"
},
{
- "id": "2b94be0f-4b5b-4419-802d-8a5e9b82f2e2",
+ "id": "da213031-51e4-4c6a-bfd7-51e25a2b10dd",
"name": "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.",
"originalRequest": {
"url": {
@@ -687,7 +687,7 @@
"_postman_previewlanguage": "json"
},
{
- "id": "af7466ea-6bcd-4dcf-9d5c-04c4d863dd60",
+ "id": "f2d6c426-8d92-4b73-98bd-34f854b487bc",
"name": "Internal Server Error - Returned if there is an unexpected error.",
"originalRequest": {
"url": {
@@ -798,7 +798,7 @@
"value": "application/json"
}
],
- "body": "{\n \"detailCode\": \"\",\n \"trackingId\": \"\",\n \"messages\": [\n {\n \"locale\": \"\",\n \"localeOrigin\": \"REQUEST\",\n \"text\": \"\"\n },\n {\n \"locale\": \"\",\n \"localeOrigin\": \"REQUEST\",\n \"text\": \"\"\n }\n ],\n \"causes\": [\n {\n \"locale\": \"\",\n \"localeOrigin\": \"DEFAULT\",\n \"text\": \"\"\n },\n {\n \"locale\": \"\",\n \"localeOrigin\": \"DEFAULT\",\n \"text\": \"\"\n }\n ]\n}",
+ "body": "{\n \"detailCode\": \"\",\n \"trackingId\": \"\",\n \"messages\": [\n {\n \"locale\": \"\",\n \"localeOrigin\": \"REQUEST\",\n \"text\": \"\"\n },\n {\n \"locale\": \"\",\n \"localeOrigin\": \"DEFAULT\",\n \"text\": \"\"\n }\n ],\n \"causes\": [\n {\n \"locale\": \"\",\n \"localeOrigin\": \"REQUEST\",\n \"text\": \"\"\n },\n {\n \"locale\": \"\",\n \"localeOrigin\": \"DEFAULT\",\n \"text\": \"\"\n }\n ]\n}",
"cookie": [],
"_postman_previewlanguage": "json"
}
@@ -809,7 +809,7 @@
}
},
{
- "id": "8a4c54b6-10be-42b1-a8a0-b864c69fdff8",
+ "id": "e273166e-eb5c-4b9d-b78f-1cb9f682ee5a",
"name": "Create an Access Profile",
"request": {
"name": "Create an Access Profile",
@@ -840,7 +840,7 @@
"method": "POST",
"body": {
"mode": "raw",
- "raw": "{\n \"owner\": {\n \"type\": \"IDENTITY\",\n \"id\": \"\",\n \"name\": \"\"\n },\n \"name\": \"\",\n \"source\": {\n \"id\": \"\",\n \"type\": \"SOURCE\",\n \"name\": \"\"\n },\n \"id\": \"\",\n \"description\": \"\",\n \"created\": \"\",\n \"modified\": \"\",\n \"enabled\": \"\",\n \"entitlements\": [\n {\n \"type\": \"ENTITLEMENT\",\n \"id\": \"\",\n \"name\": \"\"\n },\n {\n \"type\": \"ENTITLEMENT\",\n \"id\": \"\",\n \"name\": \"\"\n }\n ],\n \"requestable\": \"\",\n \"accessRequestConfig\": {\n \"commentsRequired\": \"\",\n \"denialCommentsRequired\": \"\",\n \"approvalSchemes\": [\n {\n \"approverType\": \"MANAGER\",\n \"approverId\": \"\"\n },\n {\n \"approverType\": \"GOVERNANCE_GROUP\",\n \"approverId\": \"\"\n }\n ]\n },\n \"revocationRequestConfig\": {\n \"commentsRequired\": false,\n \"denialCommentsRequired\": false,\n \"approvalSchemes\": [\n {\n \"approverType\": \"SOURCE_OWNER\",\n \"approverId\": \"\"\n },\n {\n \"approverType\": \"OWNER\",\n \"approverId\": \"\"\n }\n ]\n },\n \"segments\": [\n \"\",\n \"\"\n ],\n \"provisioningCriteria\": {\n \"operation\": \"CONTAINS\",\n \"attribute\": \"\",\n \"value\": \"\",\n \"children\": [\n {\n \"operation\": \"HAS\",\n \"attribute\": \"\",\n \"value\": \"\",\n \"children\": [\n {\n \"operation\": \"OR\",\n \"attribute\": \"\",\n \"value\": \"\"\n },\n {\n \"operation\": \"CONTAINS\",\n \"attribute\": \"\",\n \"value\": \"\"\n }\n ]\n },\n {\n \"operation\": \"HAS\",\n \"attribute\": \"\",\n \"value\": \"\",\n \"children\": [\n {\n \"operation\": \"EQUALS\",\n \"attribute\": \"\",\n \"value\": \"\"\n },\n {\n \"operation\": \"EQUALS\",\n \"attribute\": \"\",\n \"value\": \"\"\n }\n ]\n }\n ]\n }\n}",
+ "raw": "{\n \"owner\": {\n \"type\": \"IDENTITY\",\n \"id\": \"\",\n \"name\": \"\"\n },\n \"name\": \"\",\n \"source\": {\n \"id\": \"\",\n \"type\": \"SOURCE\",\n \"name\": \"\"\n },\n \"id\": \"\",\n \"description\": \"\",\n \"created\": \"\",\n \"modified\": \"