While trying to aggregate accounts, our integration with google workspace is now failing due to a 400 HTTP code, returning the message “Invalid input”. Do remember google uses the pageToken and nextPageToken way of paginating through results.
Our evidence using postman suggests IdentityNow is malforming the pageToken, possibly by removing special characters such as - / or = while reinserting the last nextPageToken inside the next URL.
Has there been any modification in the way the OOTB connector is handling the paging token? This has always been working for us, up until now.
This has broken our integrations inside production environments…