What Changed

The SAP BTP CCF connector was failing to collect paginated API responses due to incorrect next-page token parsing. The fix implements proper token transformation to extract pagination handles from the API response format.

Security Impact (Visibility & Fidelity)

Deployments running the previous SAP BTP connector version experienced a critical blind spot: when SAP BTP API responses exceeded a single page, only the first page of audit events was ingested. Subsequent pages were silently dropped due to malformed pagination token processing.

The connector now properly parses the paging response header using delimiter splitting to extract the continuation handle, ensuring complete event collection across all API result pages.

Affected Files

Solutions/SAP BTP/Data Connectors/SAPBTPPollerConnector/SAPBTP_PollingConfig.json
(packaging artefacts: mainTemplate.json, Solution_SAPBTP.json, ReleaseNotes.md, 3.0.10.zip)