Cannot print reports on co-ordinate maps on saturated tiles

[bhavyarm]

Kibana version: 7.3.1 BC1 7.3.0

Elasticsearch version: 7.3.1 BC1 7.3.0

Server OS version: darwin_x86_64

Browser version: chrome latest

Browser OS version: OS X

Original install method (e.g. download page, yum, from source, etc.): from staging

Describe the bug: If user has saturated tiles - maps reporting fails.

Steps to reproduce:

1. Create a co-ordinate map
2. Uncheck the option Desaturate tiles
3. Click share and generate PDF report - Kibana fails to do so.

Please note - we get reports on desaturated tiles without any issues
error:

Unable to generate report
Error: Request to [https://tiles.maps.elastic.co/styles/osm-bright-desaturated/2/1/1.png?elastic_tile_service_tos=agree&my_app_name=kibana&my_app_version=7.3.1&license=e7bd95ed-f647-4b65-b00b-4df52dfb0be3] failed! [net::ERR_ABORTED]

Screenshots (if relevant):

[tsullivan]

• Is this happening consistently?
• Are you able to see the URL logged in the request to ... failed message?

[bhavyarm]

Yep only on saturated tiles

[bhavyarm]

yep - https://tiles.maps.elastic.co/styles/osm-bright-desaturated/2/1/1.png?elastic_tile_service_tos=agree&my_app_name=kibana&my_app_version=7.3.1&license=e7bd95ed-f647-4b65-b00b-4df52dfb0be3

[bhavyarm]

also why is it going to desaturated tiles when I have unchecked that option?

[elasticmachine]

Pinging @elastic/kibana-gis

[bhavyarm]

Same bug on 7.4.1 BC1

[joelgriffith]

Unfortunately this is an issue baked into chrome, wherein you can load (tiles it seems) certain network requests when you've instrumented chrome to mutate requests, which we do for security and authorization.

I haven't heard much back from the chromium team, and I fear that we'll likely have to change how we pass through authorization and credentials due to this gnarly bug, but for the time being we'll have to live with it :/

[thomasneirynck]

Closed with #55137