Re: [Geoserver-devel] how does GeoServer modify a WMS/WMTS request to add authentication?

Hi Andrea, Ian, I think that WMS/WMTS/WFS cascading never supported anything besides > basic and maybe digest authentication. > ​I can report that I did WMS Cascading​ ​with Authkey successfully and it works. So I wanted to Cascade WMTS in similar way so I can reuse tiles from the source Geoserv

Re: [Geoserver-devel] how does GeoServer modify a WMS/WMTS request to add authentication?

Ah, Ian, I think that WMS/WMTS/WFS cascading never supported anything besides basic and maybe digest authentication. A mechanism such as "authkey" requires the server to add the key into the capablilities backlinks (geoserver authkey does that, barring any bug), otherwise the client has to know abo

Re: [Geoserver-devel] how does GeoServer modify a WMS/WMTS request to add authentication?

I think that code only handles the "basic" authentication whereas this bug is related to authkey - so at some point someone writes authkey=x into the URL, I just can't work out where. Ian On 15 April 2018 at 10:31, Andrea Aime wrote: > Hi Ian, > I'm not too familiar with the code bases, but

Re: [Geoserver-devel] how does GeoServer modify a WMS/WMTS request to add authentication?

Hi Ian, I'm not too familiar with the code bases, but think that the authentication does not happen in the WMS/WMTS code, but in the HTTP client instead, e.g.: https://github.com/geotools/geotools/blob/master/modules/library/main/src/main/java/org/geotools/data/ows/SimpleHttpClient.java#L138 https

[Geoserver-devel] how does GeoServer modify a WMS/WMTS request to add authentication?

I've been looking at GEOS-8671 thinking it was a simple find and replace issue in the WMTS code but it looks like all the WMTS code does is take the URL from the getCapabilities response (or the server URL if that fails) and makes a request to that