Description:
When duplicating an HTTP operation in the Web Services SaaS connector UI, hidden configuration data is retained if the operation type is changed. Specifically, if an operation with a Paging configuration (e.g., “Account Aggregation”) is copied and converted into an operation that does not display the Paging tab in the UI (e.g., “Update Account”), the paginationSteps persist in the underlying JSON configuration.
Steps to Reproduce:
-
Open a Web Services SaaS source in the Identity Security Cloud UI.
-
Select an existing HTTP operation that has a Paging configuration (e.g., “Account Aggregation”).
-
Duplicate this operation.
-
Change the “Operation Type” of the newly copied operation to “Update Account” and the HTTP Method to PUT.
-
Observe that the “Paging” menu option is removed from the UI.
-
Save the source.
Actual Behavior:
The Paging tab disappears from the UI, making it impossible to edit or remove the paging settings. However, the paginationSteps array remains populated in the source JSON configuration. I verified this through the VSCode extention
During runtime, this hidden paging logic executes. It dynamically overrides the context URL (e.g., evaluating to a generic ?cursor=null list endpoint instead of the targeted $plan.nativeIdentity$ endpoint), causing the account update to fail. This is extremely difficult to troubleshoot as the UI indicates no paging is active.
Expected Behavior:
When changing the “Operation Type” to one that does not utilize the Paging UI, the system should automatically purge the paginationSteps from the underlying JSON payload.