sailpoint-api-client 1.7.17 → 1.7.19

package/dist/beta/api.d.ts

@@ -4707,6 +4707,13 @@ export interface ArgumentBeta {
  */
 export interface ArrayInner1Beta {
 }
+/**
+ *
+ * @export
+ * @interface ArrayInner2Beta
+ */
+export interface ArrayInner2Beta {
+}
 /**
  *
  * @export
@@ -14783,10 +14790,50 @@ export interface JsonPatchOperationBeta {
     'value'?: UpdateMultiHostSourcesRequestInnerValueBeta;
 }
 export declare const JsonPatchOperationBetaOpBeta: {
+    readonly Add: "add";
     readonly Remove: "remove";
     readonly Replace: "replace";
+    readonly Move: "move";
+    readonly Copy: "copy";
+    readonly Test: "test";
 };
 export type JsonPatchOperationBetaOpBeta = typeof JsonPatchOperationBetaOpBeta[keyof typeof JsonPatchOperationBetaOpBeta];
+/**
+ * A JSONPatch Operation for Role Mining endpoints, supporting only remove and replace operations as defined by [RFC 6902 - JSON Patch](https://tools.ietf.org/html/rfc6902)
+ * @export
+ * @interface JsonPatchOperationRoleMiningBeta
+ */
+export interface JsonPatchOperationRoleMiningBeta {
+    /**
+     * The operation to be performed
+     * @type {string}
+     * @memberof JsonPatchOperationRoleMiningBeta
+     */
+    'op': JsonPatchOperationRoleMiningBetaOpBeta;
+    /**
+     * A string JSON Pointer representing the target path to an element to be affected by the operation
+     * @type {string}
+     * @memberof JsonPatchOperationRoleMiningBeta
+     */
+    'path': string;
+    /**
+     *
+     * @type {JsonPatchOperationRoleMiningValueBeta}
+     * @memberof JsonPatchOperationRoleMiningBeta
+     */
+    'value'?: JsonPatchOperationRoleMiningValueBeta;
+}
+export declare const JsonPatchOperationRoleMiningBetaOpBeta: {
+    readonly Remove: "remove";
+    readonly Replace: "replace";
+};
+export type JsonPatchOperationRoleMiningBetaOpBeta = typeof JsonPatchOperationRoleMiningBetaOpBeta[keyof typeof JsonPatchOperationRoleMiningBetaOpBeta];
+/**
+ * @type JsonPatchOperationRoleMiningValueBeta
+ * The value to be used for the operation, required for \"replace\" operations
+ * @export
+ */
+export type JsonPatchOperationRoleMiningValueBeta = Array<ArrayInner1Beta> | boolean | number | object | string;
 /**
  * A limited JSONPatch Operation as defined by [RFC 6902 - JSON Patch](https://tools.ietf.org/html/rfc6902)
  * @export
@@ -14823,7 +14870,7 @@ export type JsonPatchOperationsBetaOpBeta = typeof JsonPatchOperationsBetaOpBeta
  * The value to be used for the operation, required for \"add\" and \"replace\" operations
  * @export
  */
-export type JsonPatchOperationsValueBeta = Array<ArrayInner1Beta> | boolean | string;
+export type JsonPatchOperationsValueBeta = Array<ArrayInner2Beta> | boolean | string;
 /**
  *
  * @export
@@ -20588,36 +20635,6 @@ export declare const PatOwnerBetaTypeBeta: {
     readonly Identity: "IDENTITY";
 };
 export type PatOwnerBetaTypeBeta = typeof PatOwnerBetaTypeBeta[keyof typeof PatOwnerBetaTypeBeta];
-/**
- *
- * @export
- * @interface PatchRoleMiningPotentialRoleRequestInnerBeta
- */
-export interface PatchRoleMiningPotentialRoleRequestInnerBeta {
-    /**
-     * The operation to be performed
-     * @type {string}
-     * @memberof PatchRoleMiningPotentialRoleRequestInnerBeta
-     */
-    'op'?: PatchRoleMiningPotentialRoleRequestInnerBetaOpBeta;
-    /**
-     * A string JSON Pointer representing the target path to an element to be affected by the operation
-     * @type {string}
-     * @memberof PatchRoleMiningPotentialRoleRequestInnerBeta
-     */
-    'path': string;
-    /**
-     *
-     * @type {UpdateMultiHostSourcesRequestInnerValueBeta}
-     * @memberof PatchRoleMiningPotentialRoleRequestInnerBeta
-     */
-    'value'?: UpdateMultiHostSourcesRequestInnerValueBeta;
-}
-export declare const PatchRoleMiningPotentialRoleRequestInnerBetaOpBeta: {
-    readonly Remove: "remove";
-    readonly Replace: "replace";
-};
-export type PatchRoleMiningPotentialRoleRequestInnerBetaOpBeta = typeof PatchRoleMiningPotentialRoleRequestInnerBetaOpBeta[keyof typeof PatchRoleMiningPotentialRoleRequestInnerBetaOpBeta];
 /**
  *
  * @export
@@ -24338,7 +24355,7 @@ export interface RoleMiningIdentityDistributionDistributionInnerBeta {
      * @type {string}
      * @memberof RoleMiningIdentityDistributionDistributionInnerBeta
      */
-    'attributeValue'?: string;
+    'attributeValue'?: string | null;
     /**
      * The number of identities that have this attribute value
      * @type {number}
@@ -24425,12 +24442,24 @@ export interface RoleMiningPotentialRoleBeta {
      * @memberof RoleMiningPotentialRoleBeta
      */
     'identityIds'?: Array<string>;
+    /**
+     * The status for this identity group which can be OBTAINED or COMPRESSED
+     * @type {string}
+     * @memberof RoleMiningPotentialRoleBeta
+     */
+    'identityGroupStatus'?: string | null;
     /**
      * Name of the potential role.
      * @type {string}
      * @memberof RoleMiningPotentialRoleBeta
      */
     'name'?: string;
+    /**
+     *
+     * @type {RoleMiningPotentialRolePotentialRoleRefBeta}
+     * @memberof RoleMiningPotentialRoleBeta
+     */
+    'potentialRoleRef'?: RoleMiningPotentialRolePotentialRoleRefBeta | null;
     /**
      *
      * @type {RoleMiningPotentialRoleProvisionStateBeta}
@@ -24586,6 +24615,25 @@ export declare const RoleMiningPotentialRoleExportStateBeta: {
     readonly Error: "ERROR";
 };
 export type RoleMiningPotentialRoleExportStateBeta = typeof RoleMiningPotentialRoleExportStateBeta[keyof typeof RoleMiningPotentialRoleExportStateBeta];
+/**
+ * The potential role reference
+ * @export
+ * @interface RoleMiningPotentialRolePotentialRoleRefBeta
+ */
+export interface RoleMiningPotentialRolePotentialRoleRefBeta {
+    /**
+     * Id of the potential role
+     * @type {string}
+     * @memberof RoleMiningPotentialRolePotentialRoleRefBeta
+     */
+    'id'?: string;
+    /**
+     * Name of the potential role
+     * @type {string}
+     * @memberof RoleMiningPotentialRolePotentialRoleRefBeta
+     */
+    'name'?: string;
+}
 /**
  *
  * @export
@@ -29800,13 +29848,6 @@ export declare const SubscriptionPatchRequestInnerBetaOpBeta: {
     readonly Copy: "copy";
 };
 export type SubscriptionPatchRequestInnerBetaOpBeta = typeof SubscriptionPatchRequestInnerBetaOpBeta[keyof typeof SubscriptionPatchRequestInnerBetaOpBeta];
-/**
- *
- * @export
- * @interface SubscriptionPatchRequestInnerValueAnyOfInnerBeta
- */
-export interface SubscriptionPatchRequestInnerValueAnyOfInnerBeta {
-}
 /**
  * The value to be used for the operation, required for \"add\" and \"replace\" operations
  * @export
@@ -35049,7 +35090,7 @@ export declare const AccessRequestsBetaApiAxiosParamCreator: (configuration?: Co
      */
     closeAccessRequest: (closeAccessRequestBeta: CloseAccessRequestBeta, axiosOptions?: RawAxiosRequestConfig) => Promise<RequestArgs>;
     /**
-     * >**Required scopes:** ORG_ADMIN requires idn:access-request:manage. USER level requires idn:access-request-self:manage (Personal Access Token only).  Use this API to submit an access request in Identity Security Cloud (ISC), where it follows any ISC approval processes.  :::info The ability to request access using this API is constrained by the Access Request Segments defined in the API token\'s user context. :::  Access requests are processed asynchronously by ISC. A successful response from this endpoint means that the request has been submitted to ISC and is queued for processing. Because this endpoint is asynchronous, it does not return an error if you submit duplicate access requests in quick succession or submit an access request for access that is already in progress, approved, or rejected.  It is best practice to check for any existing access requests that reference the same access items before submitting a new access request. This can be accomplished by using the [List Access Request Status](https://developer.sailpoint.com/idn/api/v3/list-access-request-status) or the [Pending Access Request Approvals](https://developer.sailpoint.com/idn/api/v3/list-pending-approvals) APIs. You can also use the [Search API](https://developer.sailpoint.com/idn/api/v3/search) to check the existing access items an identity has before submitting an access request to ensure that you aren\'t requesting access that is already granted. If you use this API to request access that an identity already has,  without changing the account details or end date information from the existing assignment,  the API will cancel the request as a duplicate.  There are two types of access request:  __GRANT_ACCESS__ * Can be requested for multiple identities in a single request. * Supports self request and request on behalf of other users. Refer to the [Get Access Request Configuration](https://developer.sailpoint.com/idn/api/v3/get-access-request-config) endpoint for request configuration options.   * Allows any authenticated token (except API) to call this endpoint to request to grant access to themselves. Depending on the configuration, a user can request access for others. * Roles, access profiles and entitlements can be requested. * You can specify a `removeDate` to set or alter a sunset date-time on an assignment. The removeDate must be a future date-time, in the UTC timezone. Additionally, if the user already has the access assigned with a sunset date, you can also submit a request without a `removeDate` to request removal of the sunset date and time. * If a `removeDate` is specified, then the requested role, access profile, or entitlement will be removed on that date and time. * Now supports an alternate field \'requestedForWithRequestedItems\' for users to specify account selections while requesting items where they have more than one account on the source.  :::caution  If any entitlements are being requested, then the maximum number of entitlements that can be requested is 25, and the maximum number of identities that can be requested for is 10. If you exceed these limits, the request will fail with a 400 error. If you are not requesting any entitlements, then there are no limits.  :::  __REVOKE_ACCESS__ * Can only be requested for a single identity at a time. * You cannot use an access request to revoke access from an identity if that access has been granted by role membership or by birthright provisioning.  * Does not support self request. Only manager can request to revoke access for their directly managed employees. * If a `removeDate` is specified, then the requested role, access profile, or entitlement will be removed on that date and time. * Roles, access profiles, and entitlements can be requested for revocation. * Revoke requests for entitlements are limited to 1 entitlement per access request currently. * You can specify a `removeDate` to add or alter a sunset date and time on an assignment. The `removeDate` must be a future date-time, in the UTC timezone. If the user already has the access assigned with a sunset date and time, the removeDate must be a date-time earlier than the existing sunset date and time.  * Allows a manager to request to revoke access for direct employees. A user with ORG_ADMIN authority can also request to revoke access from anyone. * Now supports REVOKE_ACCESS requests for identities with multiple accounts on a single source, with the help of \'assignmentId\' and \'nativeIdentity\' fields. These fields should be used within the \'requestedItems\' section for the revoke requests.  * Usage of \'requestedForWithRequestedItems\' field is not supported for revoke requests.
+     * Use this API to submit an access request in Identity Security Cloud (ISC), where it follows any ISC approval processes.  :::info The ability to request access using this API is constrained by the Access Request Segments defined in the API token\'s user context. :::  Access requests are processed asynchronously by ISC. A successful response from this endpoint means that the request has been submitted to ISC and is queued for processing. Because this endpoint is asynchronous, it does not return an error if you submit duplicate access requests in quick succession or submit an access request for access that is already in progress, approved, or rejected.  It is best practice to check for any existing access requests that reference the same access items before submitting a new access request. This can be accomplished by using the [List Access Request Status](https://developer.sailpoint.com/idn/api/v3/list-access-request-status) or the [Pending Access Request Approvals](https://developer.sailpoint.com/idn/api/v3/list-pending-approvals) APIs. You can also use the [Search API](https://developer.sailpoint.com/idn/api/v3/search) to check the existing access items an identity has before submitting an access request to ensure that you aren\'t requesting access that is already granted. If you use this API to request access that an identity already has,  without changing the account details or end date information from the existing assignment,  the API will cancel the request as a duplicate.  There are two types of access request:  __GRANT_ACCESS__ * Can be requested for multiple identities in a single request. * Supports self request and request on behalf of other users. Refer to the [Get Access Request Configuration](https://developer.sailpoint.com/idn/api/v3/get-access-request-config) endpoint for request configuration options.   * Allows any authenticated token (except API) to call this endpoint to request to grant access to themselves. Depending on the configuration, a user can request access for others. * Roles, access profiles and entitlements can be requested. * You can specify a `removeDate` to set or alter a sunset date-time on an assignment. The removeDate must be a future date-time, in the UTC timezone. Additionally, if the user already has the access assigned with a sunset date, you can also submit a request without a `removeDate` to request removal of the sunset date and time. * If a `removeDate` is specified, then the requested role, access profile, or entitlement will be removed on that date and time. * Now supports an alternate field \'requestedForWithRequestedItems\' for users to specify account selections while requesting items where they have more than one account on the source.  :::caution  If any entitlements are being requested, then the maximum number of entitlements that can be requested is 25, and the maximum number of identities that can be requested for is 10. If you exceed these limits, the request will fail with a 400 error. If you are not requesting any entitlements, then there are no limits.  :::  __REVOKE_ACCESS__ * Can only be requested for a single identity at a time. * You cannot use an access request to revoke access from an identity if that access has been granted by role membership or by birthright provisioning.  * Does not support self request. Only manager can request to revoke access for their directly managed employees. * If a `removeDate` is specified, then the requested role, access profile, or entitlement will be removed on that date and time. * Roles, access profiles, and entitlements can be requested for revocation. * Revoke requests for entitlements are limited to 1 entitlement per access request currently. * You can specify a `removeDate` to add or alter a sunset date and time on an assignment. The `removeDate` must be a future date-time, in the UTC timezone. If the user already has the access assigned with a sunset date and time, the removeDate must be a date-time earlier than the existing sunset date and time.  * Allows a manager to request to revoke access for direct employees. A user with ORG_ADMIN authority can also request to revoke access from anyone. * Now supports REVOKE_ACCESS requests for identities with multiple accounts on a single source, with the help of \'assignmentId\' and \'nativeIdentity\' fields. These fields should be used within the \'requestedItems\' section for the revoke requests.  * Usage of \'requestedForWithRequestedItems\' field is not supported for revoke requests.
      * @summary Submit access request
      * @param {AccessRequestBeta} accessRequestBeta
      * @param {*} [axiosOptions] Override http request option.
@@ -35129,7 +35170,7 @@ export declare const AccessRequestsBetaApiFp: (configuration?: Configuration) =>
      */
     closeAccessRequest(closeAccessRequestBeta: CloseAccessRequestBeta, axiosOptions?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<object>>;
     /**
-     * >**Required scopes:** ORG_ADMIN requires idn:access-request:manage. USER level requires idn:access-request-self:manage (Personal Access Token only).  Use this API to submit an access request in Identity Security Cloud (ISC), where it follows any ISC approval processes.  :::info The ability to request access using this API is constrained by the Access Request Segments defined in the API token\'s user context. :::  Access requests are processed asynchronously by ISC. A successful response from this endpoint means that the request has been submitted to ISC and is queued for processing. Because this endpoint is asynchronous, it does not return an error if you submit duplicate access requests in quick succession or submit an access request for access that is already in progress, approved, or rejected.  It is best practice to check for any existing access requests that reference the same access items before submitting a new access request. This can be accomplished by using the [List Access Request Status](https://developer.sailpoint.com/idn/api/v3/list-access-request-status) or the [Pending Access Request Approvals](https://developer.sailpoint.com/idn/api/v3/list-pending-approvals) APIs. You can also use the [Search API](https://developer.sailpoint.com/idn/api/v3/search) to check the existing access items an identity has before submitting an access request to ensure that you aren\'t requesting access that is already granted. If you use this API to request access that an identity already has,  without changing the account details or end date information from the existing assignment,  the API will cancel the request as a duplicate.  There are two types of access request:  __GRANT_ACCESS__ * Can be requested for multiple identities in a single request. * Supports self request and request on behalf of other users. Refer to the [Get Access Request Configuration](https://developer.sailpoint.com/idn/api/v3/get-access-request-config) endpoint for request configuration options.   * Allows any authenticated token (except API) to call this endpoint to request to grant access to themselves. Depending on the configuration, a user can request access for others. * Roles, access profiles and entitlements can be requested. * You can specify a `removeDate` to set or alter a sunset date-time on an assignment. The removeDate must be a future date-time, in the UTC timezone. Additionally, if the user already has the access assigned with a sunset date, you can also submit a request without a `removeDate` to request removal of the sunset date and time. * If a `removeDate` is specified, then the requested role, access profile, or entitlement will be removed on that date and time. * Now supports an alternate field \'requestedForWithRequestedItems\' for users to specify account selections while requesting items where they have more than one account on the source.  :::caution  If any entitlements are being requested, then the maximum number of entitlements that can be requested is 25, and the maximum number of identities that can be requested for is 10. If you exceed these limits, the request will fail with a 400 error. If you are not requesting any entitlements, then there are no limits.  :::  __REVOKE_ACCESS__ * Can only be requested for a single identity at a time. * You cannot use an access request to revoke access from an identity if that access has been granted by role membership or by birthright provisioning.  * Does not support self request. Only manager can request to revoke access for their directly managed employees. * If a `removeDate` is specified, then the requested role, access profile, or entitlement will be removed on that date and time. * Roles, access profiles, and entitlements can be requested for revocation. * Revoke requests for entitlements are limited to 1 entitlement per access request currently. * You can specify a `removeDate` to add or alter a sunset date and time on an assignment. The `removeDate` must be a future date-time, in the UTC timezone. If the user already has the access assigned with a sunset date and time, the removeDate must be a date-time earlier than the existing sunset date and time.  * Allows a manager to request to revoke access for direct employees. A user with ORG_ADMIN authority can also request to revoke access from anyone. * Now supports REVOKE_ACCESS requests for identities with multiple accounts on a single source, with the help of \'assignmentId\' and \'nativeIdentity\' fields. These fields should be used within the \'requestedItems\' section for the revoke requests.  * Usage of \'requestedForWithRequestedItems\' field is not supported for revoke requests.
+     * Use this API to submit an access request in Identity Security Cloud (ISC), where it follows any ISC approval processes.  :::info The ability to request access using this API is constrained by the Access Request Segments defined in the API token\'s user context. :::  Access requests are processed asynchronously by ISC. A successful response from this endpoint means that the request has been submitted to ISC and is queued for processing. Because this endpoint is asynchronous, it does not return an error if you submit duplicate access requests in quick succession or submit an access request for access that is already in progress, approved, or rejected.  It is best practice to check for any existing access requests that reference the same access items before submitting a new access request. This can be accomplished by using the [List Access Request Status](https://developer.sailpoint.com/idn/api/v3/list-access-request-status) or the [Pending Access Request Approvals](https://developer.sailpoint.com/idn/api/v3/list-pending-approvals) APIs. You can also use the [Search API](https://developer.sailpoint.com/idn/api/v3/search) to check the existing access items an identity has before submitting an access request to ensure that you aren\'t requesting access that is already granted. If you use this API to request access that an identity already has,  without changing the account details or end date information from the existing assignment,  the API will cancel the request as a duplicate.  There are two types of access request:  __GRANT_ACCESS__ * Can be requested for multiple identities in a single request. * Supports self request and request on behalf of other users. Refer to the [Get Access Request Configuration](https://developer.sailpoint.com/idn/api/v3/get-access-request-config) endpoint for request configuration options.   * Allows any authenticated token (except API) to call this endpoint to request to grant access to themselves. Depending on the configuration, a user can request access for others. * Roles, access profiles and entitlements can be requested. * You can specify a `removeDate` to set or alter a sunset date-time on an assignment. The removeDate must be a future date-time, in the UTC timezone. Additionally, if the user already has the access assigned with a sunset date, you can also submit a request without a `removeDate` to request removal of the sunset date and time. * If a `removeDate` is specified, then the requested role, access profile, or entitlement will be removed on that date and time. * Now supports an alternate field \'requestedForWithRequestedItems\' for users to specify account selections while requesting items where they have more than one account on the source.  :::caution  If any entitlements are being requested, then the maximum number of entitlements that can be requested is 25, and the maximum number of identities that can be requested for is 10. If you exceed these limits, the request will fail with a 400 error. If you are not requesting any entitlements, then there are no limits.  :::  __REVOKE_ACCESS__ * Can only be requested for a single identity at a time. * You cannot use an access request to revoke access from an identity if that access has been granted by role membership or by birthright provisioning.  * Does not support self request. Only manager can request to revoke access for their directly managed employees. * If a `removeDate` is specified, then the requested role, access profile, or entitlement will be removed on that date and time. * Roles, access profiles, and entitlements can be requested for revocation. * Revoke requests for entitlements are limited to 1 entitlement per access request currently. * You can specify a `removeDate` to add or alter a sunset date and time on an assignment. The `removeDate` must be a future date-time, in the UTC timezone. If the user already has the access assigned with a sunset date and time, the removeDate must be a date-time earlier than the existing sunset date and time.  * Allows a manager to request to revoke access for direct employees. A user with ORG_ADMIN authority can also request to revoke access from anyone. * Now supports REVOKE_ACCESS requests for identities with multiple accounts on a single source, with the help of \'assignmentId\' and \'nativeIdentity\' fields. These fields should be used within the \'requestedItems\' section for the revoke requests.  * Usage of \'requestedForWithRequestedItems\' field is not supported for revoke requests.
      * @summary Submit access request
      * @param {AccessRequestBeta} accessRequestBeta
      * @param {*} [axiosOptions] Override http request option.
@@ -35209,7 +35250,7 @@ export declare const AccessRequestsBetaApiFactory: (configuration?: Configuratio
      */
     closeAccessRequest(requestParameters: AccessRequestsBetaApiCloseAccessRequestRequest, axiosOptions?: RawAxiosRequestConfig): AxiosPromise<object>;
     /**
-     * >**Required scopes:** ORG_ADMIN requires idn:access-request:manage. USER level requires idn:access-request-self:manage (Personal Access Token only).  Use this API to submit an access request in Identity Security Cloud (ISC), where it follows any ISC approval processes.  :::info The ability to request access using this API is constrained by the Access Request Segments defined in the API token\'s user context. :::  Access requests are processed asynchronously by ISC. A successful response from this endpoint means that the request has been submitted to ISC and is queued for processing. Because this endpoint is asynchronous, it does not return an error if you submit duplicate access requests in quick succession or submit an access request for access that is already in progress, approved, or rejected.  It is best practice to check for any existing access requests that reference the same access items before submitting a new access request. This can be accomplished by using the [List Access Request Status](https://developer.sailpoint.com/idn/api/v3/list-access-request-status) or the [Pending Access Request Approvals](https://developer.sailpoint.com/idn/api/v3/list-pending-approvals) APIs. You can also use the [Search API](https://developer.sailpoint.com/idn/api/v3/search) to check the existing access items an identity has before submitting an access request to ensure that you aren\'t requesting access that is already granted. If you use this API to request access that an identity already has,  without changing the account details or end date information from the existing assignment,  the API will cancel the request as a duplicate.  There are two types of access request:  __GRANT_ACCESS__ * Can be requested for multiple identities in a single request. * Supports self request and request on behalf of other users. Refer to the [Get Access Request Configuration](https://developer.sailpoint.com/idn/api/v3/get-access-request-config) endpoint for request configuration options.   * Allows any authenticated token (except API) to call this endpoint to request to grant access to themselves. Depending on the configuration, a user can request access for others. * Roles, access profiles and entitlements can be requested. * You can specify a `removeDate` to set or alter a sunset date-time on an assignment. The removeDate must be a future date-time, in the UTC timezone. Additionally, if the user already has the access assigned with a sunset date, you can also submit a request without a `removeDate` to request removal of the sunset date and time. * If a `removeDate` is specified, then the requested role, access profile, or entitlement will be removed on that date and time. * Now supports an alternate field \'requestedForWithRequestedItems\' for users to specify account selections while requesting items where they have more than one account on the source.  :::caution  If any entitlements are being requested, then the maximum number of entitlements that can be requested is 25, and the maximum number of identities that can be requested for is 10. If you exceed these limits, the request will fail with a 400 error. If you are not requesting any entitlements, then there are no limits.  :::  __REVOKE_ACCESS__ * Can only be requested for a single identity at a time. * You cannot use an access request to revoke access from an identity if that access has been granted by role membership or by birthright provisioning.  * Does not support self request. Only manager can request to revoke access for their directly managed employees. * If a `removeDate` is specified, then the requested role, access profile, or entitlement will be removed on that date and time. * Roles, access profiles, and entitlements can be requested for revocation. * Revoke requests for entitlements are limited to 1 entitlement per access request currently. * You can specify a `removeDate` to add or alter a sunset date and time on an assignment. The `removeDate` must be a future date-time, in the UTC timezone. If the user already has the access assigned with a sunset date and time, the removeDate must be a date-time earlier than the existing sunset date and time.  * Allows a manager to request to revoke access for direct employees. A user with ORG_ADMIN authority can also request to revoke access from anyone. * Now supports REVOKE_ACCESS requests for identities with multiple accounts on a single source, with the help of \'assignmentId\' and \'nativeIdentity\' fields. These fields should be used within the \'requestedItems\' section for the revoke requests.  * Usage of \'requestedForWithRequestedItems\' field is not supported for revoke requests.
+     * Use this API to submit an access request in Identity Security Cloud (ISC), where it follows any ISC approval processes.  :::info The ability to request access using this API is constrained by the Access Request Segments defined in the API token\'s user context. :::  Access requests are processed asynchronously by ISC. A successful response from this endpoint means that the request has been submitted to ISC and is queued for processing. Because this endpoint is asynchronous, it does not return an error if you submit duplicate access requests in quick succession or submit an access request for access that is already in progress, approved, or rejected.  It is best practice to check for any existing access requests that reference the same access items before submitting a new access request. This can be accomplished by using the [List Access Request Status](https://developer.sailpoint.com/idn/api/v3/list-access-request-status) or the [Pending Access Request Approvals](https://developer.sailpoint.com/idn/api/v3/list-pending-approvals) APIs. You can also use the [Search API](https://developer.sailpoint.com/idn/api/v3/search) to check the existing access items an identity has before submitting an access request to ensure that you aren\'t requesting access that is already granted. If you use this API to request access that an identity already has,  without changing the account details or end date information from the existing assignment,  the API will cancel the request as a duplicate.  There are two types of access request:  __GRANT_ACCESS__ * Can be requested for multiple identities in a single request. * Supports self request and request on behalf of other users. Refer to the [Get Access Request Configuration](https://developer.sailpoint.com/idn/api/v3/get-access-request-config) endpoint for request configuration options.   * Allows any authenticated token (except API) to call this endpoint to request to grant access to themselves. Depending on the configuration, a user can request access for others. * Roles, access profiles and entitlements can be requested. * You can specify a `removeDate` to set or alter a sunset date-time on an assignment. The removeDate must be a future date-time, in the UTC timezone. Additionally, if the user already has the access assigned with a sunset date, you can also submit a request without a `removeDate` to request removal of the sunset date and time. * If a `removeDate` is specified, then the requested role, access profile, or entitlement will be removed on that date and time. * Now supports an alternate field \'requestedForWithRequestedItems\' for users to specify account selections while requesting items where they have more than one account on the source.  :::caution  If any entitlements are being requested, then the maximum number of entitlements that can be requested is 25, and the maximum number of identities that can be requested for is 10. If you exceed these limits, the request will fail with a 400 error. If you are not requesting any entitlements, then there are no limits.  :::  __REVOKE_ACCESS__ * Can only be requested for a single identity at a time. * You cannot use an access request to revoke access from an identity if that access has been granted by role membership or by birthright provisioning.  * Does not support self request. Only manager can request to revoke access for their directly managed employees. * If a `removeDate` is specified, then the requested role, access profile, or entitlement will be removed on that date and time. * Roles, access profiles, and entitlements can be requested for revocation. * Revoke requests for entitlements are limited to 1 entitlement per access request currently. * You can specify a `removeDate` to add or alter a sunset date and time on an assignment. The `removeDate` must be a future date-time, in the UTC timezone. If the user already has the access assigned with a sunset date and time, the removeDate must be a date-time earlier than the existing sunset date and time.  * Allows a manager to request to revoke access for direct employees. A user with ORG_ADMIN authority can also request to revoke access from anyone. * Now supports REVOKE_ACCESS requests for identities with multiple accounts on a single source, with the help of \'assignmentId\' and \'nativeIdentity\' fields. These fields should be used within the \'requestedItems\' section for the revoke requests.  * Usage of \'requestedForWithRequestedItems\' field is not supported for revoke requests.
      * @summary Submit access request
      * @param {AccessRequestsBetaApiCreateAccessRequestRequest} requestParameters Request parameters.
      * @param {*} [axiosOptions] Override http request option.
@@ -35466,7 +35507,7 @@ export declare class AccessRequestsBetaApi extends BaseAPI {
      */
     closeAccessRequest(requestParameters: AccessRequestsBetaApiCloseAccessRequestRequest, axiosOptions?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<object, any>>;
     /**
-     * >**Required scopes:** ORG_ADMIN requires idn:access-request:manage. USER level requires idn:access-request-self:manage (Personal Access Token only).  Use this API to submit an access request in Identity Security Cloud (ISC), where it follows any ISC approval processes.  :::info The ability to request access using this API is constrained by the Access Request Segments defined in the API token\'s user context. :::  Access requests are processed asynchronously by ISC. A successful response from this endpoint means that the request has been submitted to ISC and is queued for processing. Because this endpoint is asynchronous, it does not return an error if you submit duplicate access requests in quick succession or submit an access request for access that is already in progress, approved, or rejected.  It is best practice to check for any existing access requests that reference the same access items before submitting a new access request. This can be accomplished by using the [List Access Request Status](https://developer.sailpoint.com/idn/api/v3/list-access-request-status) or the [Pending Access Request Approvals](https://developer.sailpoint.com/idn/api/v3/list-pending-approvals) APIs. You can also use the [Search API](https://developer.sailpoint.com/idn/api/v3/search) to check the existing access items an identity has before submitting an access request to ensure that you aren\'t requesting access that is already granted. If you use this API to request access that an identity already has,  without changing the account details or end date information from the existing assignment,  the API will cancel the request as a duplicate.  There are two types of access request:  __GRANT_ACCESS__ * Can be requested for multiple identities in a single request. * Supports self request and request on behalf of other users. Refer to the [Get Access Request Configuration](https://developer.sailpoint.com/idn/api/v3/get-access-request-config) endpoint for request configuration options.   * Allows any authenticated token (except API) to call this endpoint to request to grant access to themselves. Depending on the configuration, a user can request access for others. * Roles, access profiles and entitlements can be requested. * You can specify a `removeDate` to set or alter a sunset date-time on an assignment. The removeDate must be a future date-time, in the UTC timezone. Additionally, if the user already has the access assigned with a sunset date, you can also submit a request without a `removeDate` to request removal of the sunset date and time. * If a `removeDate` is specified, then the requested role, access profile, or entitlement will be removed on that date and time. * Now supports an alternate field \'requestedForWithRequestedItems\' for users to specify account selections while requesting items where they have more than one account on the source.  :::caution  If any entitlements are being requested, then the maximum number of entitlements that can be requested is 25, and the maximum number of identities that can be requested for is 10. If you exceed these limits, the request will fail with a 400 error. If you are not requesting any entitlements, then there are no limits.  :::  __REVOKE_ACCESS__ * Can only be requested for a single identity at a time. * You cannot use an access request to revoke access from an identity if that access has been granted by role membership or by birthright provisioning.  * Does not support self request. Only manager can request to revoke access for their directly managed employees. * If a `removeDate` is specified, then the requested role, access profile, or entitlement will be removed on that date and time. * Roles, access profiles, and entitlements can be requested for revocation. * Revoke requests for entitlements are limited to 1 entitlement per access request currently. * You can specify a `removeDate` to add or alter a sunset date and time on an assignment. The `removeDate` must be a future date-time, in the UTC timezone. If the user already has the access assigned with a sunset date and time, the removeDate must be a date-time earlier than the existing sunset date and time.  * Allows a manager to request to revoke access for direct employees. A user with ORG_ADMIN authority can also request to revoke access from anyone. * Now supports REVOKE_ACCESS requests for identities with multiple accounts on a single source, with the help of \'assignmentId\' and \'nativeIdentity\' fields. These fields should be used within the \'requestedItems\' section for the revoke requests.  * Usage of \'requestedForWithRequestedItems\' field is not supported for revoke requests.
+     * Use this API to submit an access request in Identity Security Cloud (ISC), where it follows any ISC approval processes.  :::info The ability to request access using this API is constrained by the Access Request Segments defined in the API token\'s user context. :::  Access requests are processed asynchronously by ISC. A successful response from this endpoint means that the request has been submitted to ISC and is queued for processing. Because this endpoint is asynchronous, it does not return an error if you submit duplicate access requests in quick succession or submit an access request for access that is already in progress, approved, or rejected.  It is best practice to check for any existing access requests that reference the same access items before submitting a new access request. This can be accomplished by using the [List Access Request Status](https://developer.sailpoint.com/idn/api/v3/list-access-request-status) or the [Pending Access Request Approvals](https://developer.sailpoint.com/idn/api/v3/list-pending-approvals) APIs. You can also use the [Search API](https://developer.sailpoint.com/idn/api/v3/search) to check the existing access items an identity has before submitting an access request to ensure that you aren\'t requesting access that is already granted. If you use this API to request access that an identity already has,  without changing the account details or end date information from the existing assignment,  the API will cancel the request as a duplicate.  There are two types of access request:  __GRANT_ACCESS__ * Can be requested for multiple identities in a single request. * Supports self request and request on behalf of other users. Refer to the [Get Access Request Configuration](https://developer.sailpoint.com/idn/api/v3/get-access-request-config) endpoint for request configuration options.   * Allows any authenticated token (except API) to call this endpoint to request to grant access to themselves. Depending on the configuration, a user can request access for others. * Roles, access profiles and entitlements can be requested. * You can specify a `removeDate` to set or alter a sunset date-time on an assignment. The removeDate must be a future date-time, in the UTC timezone. Additionally, if the user already has the access assigned with a sunset date, you can also submit a request without a `removeDate` to request removal of the sunset date and time. * If a `removeDate` is specified, then the requested role, access profile, or entitlement will be removed on that date and time. * Now supports an alternate field \'requestedForWithRequestedItems\' for users to specify account selections while requesting items where they have more than one account on the source.  :::caution  If any entitlements are being requested, then the maximum number of entitlements that can be requested is 25, and the maximum number of identities that can be requested for is 10. If you exceed these limits, the request will fail with a 400 error. If you are not requesting any entitlements, then there are no limits.  :::  __REVOKE_ACCESS__ * Can only be requested for a single identity at a time. * You cannot use an access request to revoke access from an identity if that access has been granted by role membership or by birthright provisioning.  * Does not support self request. Only manager can request to revoke access for their directly managed employees. * If a `removeDate` is specified, then the requested role, access profile, or entitlement will be removed on that date and time. * Roles, access profiles, and entitlements can be requested for revocation. * Revoke requests for entitlements are limited to 1 entitlement per access request currently. * You can specify a `removeDate` to add or alter a sunset date and time on an assignment. The `removeDate` must be a future date-time, in the UTC timezone. If the user already has the access assigned with a sunset date and time, the removeDate must be a date-time earlier than the existing sunset date and time.  * Allows a manager to request to revoke access for direct employees. A user with ORG_ADMIN authority can also request to revoke access from anyone. * Now supports REVOKE_ACCESS requests for identities with multiple accounts on a single source, with the help of \'assignmentId\' and \'nativeIdentity\' fields. These fields should be used within the \'requestedItems\' section for the revoke requests.  * Usage of \'requestedForWithRequestedItems\' field is not supported for revoke requests.
      * @summary Submit access request
      * @param {AccessRequestsBetaApiCreateAccessRequestRequest} requestParameters Request parameters.
      * @param {*} [axiosOptions] Override http request option.
@@ -44852,23 +44893,23 @@ export declare const IAIRoleMiningBetaApiAxiosParamCreator: (configuration?: Con
     getSavedPotentialRoles: (sorters?: string, offset?: number, limit?: number, count?: boolean, axiosOptions?: RawAxiosRequestConfig) => Promise<RequestArgs>;
     /**
      * This method updates an existing potential role using the role mining session id and the potential role summary id.  The following fields can be modified:  * `description`  * `name`  * `saved`   >**NOTE: All other fields cannot be modified.**
-     * @summary Update a potential role in session
+     * @summary Update potential role in session
      * @param {string} sessionId The role mining session id
      * @param {string} potentialRoleId The potential role summary id
-     * @param {Array<JsonPatchOperationBeta>} jsonPatchOperationBeta
+     * @param {Array<JsonPatchOperationRoleMiningBeta>} jsonPatchOperationRoleMiningBeta
      * @param {*} [axiosOptions] Override http request option.
      * @throws {RequiredError}
      */
-    patchPotentialRoleSession: (sessionId: string, potentialRoleId: string, jsonPatchOperationBeta: Array<JsonPatchOperationBeta>, axiosOptions?: RawAxiosRequestConfig) => Promise<RequestArgs>;
+    patchPotentialRoleSession: (sessionId: string, potentialRoleId: string, jsonPatchOperationRoleMiningBeta: Array<JsonPatchOperationRoleMiningBeta>, axiosOptions?: RawAxiosRequestConfig) => Promise<RequestArgs>;
     /**
      * This method updates an existing potential role.  The following fields can be modified:  * `description`  * `name`  * `saved`   >**NOTE: All other fields cannot be modified.**
      * @summary Update a potential role
      * @param {string} potentialRoleId The potential role summary id
-     * @param {Array<PatchRoleMiningPotentialRoleRequestInnerBeta>} patchRoleMiningPotentialRoleRequestInnerBeta
+     * @param {Array<JsonPatchOperationRoleMiningBeta>} jsonPatchOperationRoleMiningBeta
      * @param {*} [axiosOptions] Override http request option.
      * @throws {RequiredError}
      */
-    patchRoleMiningPotentialRole: (potentialRoleId: string, patchRoleMiningPotentialRoleRequestInnerBeta: Array<PatchRoleMiningPotentialRoleRequestInnerBeta>, axiosOptions?: RawAxiosRequestConfig) => Promise<RequestArgs>;
+    patchRoleMiningPotentialRole: (potentialRoleId: string, jsonPatchOperationRoleMiningBeta: Array<JsonPatchOperationRoleMiningBeta>, axiosOptions?: RawAxiosRequestConfig) => Promise<RequestArgs>;
     /**
      * The  method updates an existing role mining session using PATCH. Supports op in {\"replace\"} and changes to pruneThreshold and/or minNumIdentitiesInPotentialRole. The potential roles in this role mining session is then re-calculated.
      * @summary Patch a role mining session
@@ -45130,23 +45171,23 @@ export declare const IAIRoleMiningBetaApiFp: (configuration?: Configuration) =>
     getSavedPotentialRoles(sorters?: string, offset?: number, limit?: number, count?: boolean, axiosOptions?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<Array<RoleMiningSessionDraftRoleDtoBeta>>>;
     /**
      * This method updates an existing potential role using the role mining session id and the potential role summary id.  The following fields can be modified:  * `description`  * `name`  * `saved`   >**NOTE: All other fields cannot be modified.**
-     * @summary Update a potential role in session
+     * @summary Update potential role in session
      * @param {string} sessionId The role mining session id
      * @param {string} potentialRoleId The potential role summary id
-     * @param {Array<JsonPatchOperationBeta>} jsonPatchOperationBeta
+     * @param {Array<JsonPatchOperationRoleMiningBeta>} jsonPatchOperationRoleMiningBeta
      * @param {*} [axiosOptions] Override http request option.
      * @throws {RequiredError}
      */
-    patchPotentialRoleSession(sessionId: string, potentialRoleId: string, jsonPatchOperationBeta: Array<JsonPatchOperationBeta>, axiosOptions?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<object>>;
+    patchPotentialRoleSession(sessionId: string, potentialRoleId: string, jsonPatchOperationRoleMiningBeta: Array<JsonPatchOperationRoleMiningBeta>, axiosOptions?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<object>>;
     /**
      * This method updates an existing potential role.  The following fields can be modified:  * `description`  * `name`  * `saved`   >**NOTE: All other fields cannot be modified.**
      * @summary Update a potential role
      * @param {string} potentialRoleId The potential role summary id
-     * @param {Array<PatchRoleMiningPotentialRoleRequestInnerBeta>} patchRoleMiningPotentialRoleRequestInnerBeta
+     * @param {Array<JsonPatchOperationRoleMiningBeta>} jsonPatchOperationRoleMiningBeta
      * @param {*} [axiosOptions] Override http request option.
      * @throws {RequiredError}
      */
-    patchRoleMiningPotentialRole(potentialRoleId: string, patchRoleMiningPotentialRoleRequestInnerBeta: Array<PatchRoleMiningPotentialRoleRequestInnerBeta>, axiosOptions?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<object>>;
+    patchRoleMiningPotentialRole(potentialRoleId: string, jsonPatchOperationRoleMiningBeta: Array<JsonPatchOperationRoleMiningBeta>, axiosOptions?: RawAxiosRequestConfig): Promise<(axios?: AxiosInstance, basePath?: string) => AxiosPromise<object>>;
     /**
      * The  method updates an existing role mining session using PATCH. Supports op in {\"replace\"} and changes to pruneThreshold and/or minNumIdentitiesInPotentialRole. The potential roles in this role mining session is then re-calculated.
      * @summary Patch a role mining session
@@ -45344,7 +45385,7 @@ export declare const IAIRoleMiningBetaApiFactory: (configuration?: Configuration
     getSavedPotentialRoles(requestParameters?: IAIRoleMiningBetaApiGetSavedPotentialRolesRequest, axiosOptions?: RawAxiosRequestConfig): AxiosPromise<Array<RoleMiningSessionDraftRoleDtoBeta>>;
     /**
      * This method updates an existing potential role using the role mining session id and the potential role summary id.  The following fields can be modified:  * `description`  * `name`  * `saved`   >**NOTE: All other fields cannot be modified.**
-     * @summary Update a potential role in session
+     * @summary Update potential role in session
      * @param {IAIRoleMiningBetaApiPatchPotentialRoleSessionRequest} requestParameters Request parameters.
      * @param {*} [axiosOptions] Override http request option.
      * @throws {RequiredError}
@@ -46052,10 +46093,10 @@ export interface IAIRoleMiningBetaApiPatchPotentialRoleSessionRequest {
     readonly potentialRoleId: string;
     /**
      *
-     * @type {Array<JsonPatchOperationBeta>}
+     * @type {Array<JsonPatchOperationRoleMiningBeta>}
      * @memberof IAIRoleMiningBetaApiPatchPotentialRoleSession
      */
-    readonly jsonPatchOperationBeta: Array<JsonPatchOperationBeta>;
+    readonly jsonPatchOperationRoleMiningBeta: Array<JsonPatchOperationRoleMiningBeta>;
 }
 /**
  * Request parameters for patchRoleMiningPotentialRole operation in IAIRoleMiningBetaApi.
@@ -46071,10 +46112,10 @@ export interface IAIRoleMiningBetaApiPatchRoleMiningPotentialRoleRequest {
     readonly potentialRoleId: string;
     /**
      *
-     * @type {Array<PatchRoleMiningPotentialRoleRequestInnerBeta>}
+     * @type {Array<JsonPatchOperationRoleMiningBeta>}
      * @memberof IAIRoleMiningBetaApiPatchRoleMiningPotentialRole
      */
-    readonly patchRoleMiningPotentialRoleRequestInnerBeta: Array<PatchRoleMiningPotentialRoleRequestInnerBeta>;
+    readonly jsonPatchOperationRoleMiningBeta: Array<JsonPatchOperationRoleMiningBeta>;
 }
 /**
  * Request parameters for patchRoleMiningSession operation in IAIRoleMiningBetaApi.
@@ -46320,7 +46361,7 @@ export declare class IAIRoleMiningBetaApi extends BaseAPI {
     getSavedPotentialRoles(requestParameters?: IAIRoleMiningBetaApiGetSavedPotentialRolesRequest, axiosOptions?: RawAxiosRequestConfig): Promise<import("axios").AxiosResponse<RoleMiningSessionDraftRoleDtoBeta[], any>>;
     /**
      * This method updates an existing potential role using the role mining session id and the potential role summary id.  The following fields can be modified:  * `description`  * `name`  * `saved`   >**NOTE: All other fields cannot be modified.**
-     * @summary Update a potential role in session
+     * @summary Update potential role in session
      * @param {IAIRoleMiningBetaApiPatchPotentialRoleSessionRequest} requestParameters Request parameters.
      * @param {*} [axiosOptions] Override http request option.
      * @throws {RequiredError}