I've been looking at GEOS-8671
<https://osgeo-org.atlassian.net/browse/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. So I now suspect that at some
point the security code is adding the authentication code to the URL - I
guessed that SecuredWMTSLayer might be the place to look, but that seems to
nothing to the URL, tracking back I came to SecuredWMTSStoreInfo which
looks possible as it calls SecuredObjects.secure(wms, policy) - but I can't
for the life of me work out what is going on in there.

The worrying thing is that all that SecuredWMTS* code is a straight copy
and paste from SecuredWMS* so if this fails for WMTS I suspect it will fail
for WMS.

Can any one point me to the code that actually rewrites the URL to insert
the authenicationkey?


Ian Turton
Check out the vibrant tech community on one of the world's most
engaging tech sites, Slashdot.org! http://sdm.link/slashdot
Geoserver-devel mailing list

Reply via email to