Hi Nuno,
So I just found a solution thanks to Andrea and Darell van der Voort.
Precisely as you've pointed out it all about the
> *GeoServer \ GeoWebCache security mechanism,*
So apparently is you are having rules in Geofence or the Geoserver Data
Security Subsystem that prevent access to
I see, thanks for sharing your findings :)
On 09/29/2017 02:24 PM, Steve Omondi wrote:
Hi Nuno,
So I just found a solution thanks to Andrea and Darell van der Voort. Precisely
as you've pointed out it all about the **
*GeoServer \ GeoWebCache security mechanism,*
So apparently is you
Cool.
Thank you too.
Kind regards,
Steve Omondi
On Fri, Sep 29, 2017 at 4:41 PM, Nuno Oliveira <
nuno.olive...@geo-solutions.it> wrote:
> I see, thanks for sharing your findings :)
>
>
> On 09/29/2017 02:24 PM, Steve Omondi wrote:
>
> Hi Nuno,
>
> So I just found a solution thanks to Andrea and
Hi,
there was some recent changes in GeoServer \ GeoWebCache security mechanism, I
was not involved in that work
so I don't know the details ... could you precise which version of GeoServer
you are using ? This may help the involved
developers to give you some feedback.
That said, based on
Hi,Did you get any solutions for this?I'm facing same issue and I can't
figure out how to go about it.Kindly share yours solution.
-
Kind Regards,
Steve Omondi
GIS & DB Developer/DBA
Ramani Online, Ramani Geosystems
--
Sent from:
Hi list,
I am spent a couple of days try to find a solution for this so If only I
could find help here that would be great.
Problem specification:
I am using GeoServer rest to truncate and seed layers after upload process
(done using the rest too).
Weird thing is /rest/truncate/masstruncate
