SailPoint plans to enable HTTP2 in Cloudflare on Jul 27, 2026 at 10am CDT. This provides better security and performance than HTTP1.1 but we are not deprecating HTTP1.1 at this time. All environments will be affected simultaneously.
How long is the maintenance and why?
The change is immediate. The reason we are communicating this change is that you could be affected if you are making API calls to ISC that expect case-sensitive header keys to be returned. Example header key X-Total-Count will become x-total-count once HTTP2 is enabled. There is a scenario, though unlikely, that customers API calls or scripts could fail to expect this change and handle it gracefully.
Action Required
Customers should review their API calls and scripts, especially those they deem critical, to ensure they will not be impacted by this change. If customers suspect they have been impacted by this change after it has been made, they should know to put in a ticket with SailPoint Support who will assist them in troubleshooting any API calls/scripts they suspect are affected.
@collin_cornelius where do I raise that the API documentation is now needing updated, There are references to Response headers but they are now incorrectly cased, such as Retry-After, X-Total-Count, etc.
This seems like a pretty big deal to roll to all environments at the same time. We have noted issues with paging templates using things like $responseHeaders.Link changing to $responseHeaders.link and not resolving. It may need a little more due diligence before mass rollout as it could trigger attempted mass deletions on sources.
One of our sandbox sources started collecting the first page, considered that complete, and then attempted to deleted everyone that wasn’t on that first page. Thankfully the delete threshold prevented that, but that seems to be a bad idea to subject people to all at once.
Hi Kyle, we haven’t enabled HTTP2 for customers yet, so the issue you saw with $responseHeaders.Link changing to $responseHeaders.link was a separate issue (speculating but maybe that was a similar change made by a 3rd party you’ve integrated with).
In terms of due diligence, we’ve had HTTP2 enabled internally in our Dev environment for about 8 months now so it has been tested extensively, however there is still the possibility that customers could have custom scripts that will be affected. If you are concerned this may be the case, please submit a support ticket with config details so SailPoint can review. Thanks.
