On Fri, Nov 18, 2022 at 10:48 AM VANDENSCHRICK, Grégoire <gvandenschrick@…11635…> wrote:
A precision again:
even with only the geofence client plugin only does the /gwc becomes inaccessible.
Greg
De : VANDENSCHRICK, Grégoire <gvandenschrick@…11635…>
Envoyé : vendredi 18 novembre 2022 09:25
À : Jody Garnett <jody.garnett@…84…>
Cc : geoserver-users@lists.sourceforge.net <geoserver-users@lists.sourceforge.net>
Objet : Re: [Geoserver-users] geoserver 2.21.2 /gwc inaccessible with geofence server plugin installed
I’m not sure I catch precisely what you mean and don(t know how to check this.
Global services are on I would say (I have the problem with the demo dataset coming with geoserver, I assume in this data directory, global services are on, right?);
One of my colleagues was in the process of recreating a data directory on geoserver 2.21.2 with all the extensions we need via REST (we port the data directory configuration from one geoserver version to the new stable one with a python script automating this). We were arrived at the step of creating the geowebcache definitions for the layers that require them, when we found out that geoserver/gwc was not available, hence we could not use its REST api to modify the geowebcached layers (choosing the proper projection, tiles format and so on).
So I went back the a clean geoserver 2.21.2 without our data (only the demo dataset) and tested out the availability simply of geoserver/gwc (via for instance the link in the Caching Defaults page of the Tile Caching menu in the GUI), that’s how I found out the all the extensions I added did not hinder or modify that url, except the geofence server one.
Don’t know what to do I fear…
Greg
De : Jody Garnett <jody.garnett@…84…>
Envoyé : vendredi 18 novembre 2022 06:22
À : VANDENSCHRICK, Grégoire <gvandenschrick@…11635…>
Cc : geoserver-users@lists.sourceforge.net <geoserver-users@lists.sourceforge.net>
Objet : Re: [Geoserver-users] geoserver 2.21.2 /gwc inaccessible with geofence server plugin installed
There were some security fixes for GWC; and a fix so it so would still work if global services were off.
Chances are it is mapping to a virtual WMS endpoint for the layer now? Rather than a global service layer.
Do you think you can check?
You are the first person to report this - thanks for speaking up.
—
Jody
On Thu, Nov 17, 2022 at 5:37 AM VANDENSCHRICK, Grégoire <gvandenschrick@…11635…> wrote:
Hi,
sorry, double post.
All the best,
Greg
De : VANDENSCHRICK, Grégoire <gvandenschrick@…11635…>
Envoyé : jeudi 17 novembre 2022 11:33
À : geoserver-users@lists.sourceforge.net <geoserver-users@lists.sourceforge.net>
Objet : [Geoserver-users] geoserver 2.21.2 /gwc inaccessible with geofence server plugin installed
Hi,
I have some trouble trying to feed via rest a new version of geoserver 2.21.2.
Basically, I’m loosing localhost:8080/geoserver/gwc/ as soon as I add the geofence server plugin.
I tested side effects by testing geoserver 2.21.2 vanilla, with it own internal data data directory, and adding all the extensions I need, being precise on the proper version number.
I added incrementally and in this order the app schema, csw, inspire, printing, all of them do let me access geoserver/gwc.
But as soon as I add the geofence server plugin, this geoserver/gwc returns an HTTP 404.
I discovered it’s still accessible, but under localhost:8080/geoserver.
This one usually redirects towards geoserver/web.
Adding a general rule ‘allow everything to ADMIN’ in geofence does not clear this.
I tried also something suggested on stackexchange (https://gis.stackexchange.com/questions/417999/geoserver-gwc-sending-404-when-geofence-is-activated), ie adding gwc.context.suffix=gwc in geofence-server.properties but it does not help either.
I tried also to deploy geoserver2.21.2 with the geofence server plugin only, and I get exactly the same issue, with or without the stackexchange suggestion.
Hence it does not seem to be a problem of some interactions with other extensions, but only an interference between geofence server plugin and gwc.
Does someone experience the same issue? Is there a known workaround?
All the very best,
Gregoire Vandenschrick, BruGIS (https://gis.urban.brussels/)
Geoserver-users mailing list
Please make sure you read the following two resources before posting to this list:
If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
–
–
Jody Garnett
Geoserver-users mailing list
Please make sure you read the following two resources before posting to this list:
If you want to request a feature or an improvement, also see this: https://github.com/geoserver/geoserver/wiki/Successfully-requesting-and-integrating-new-features-and-improvements-in-GeoServer
Geoserver-users@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/geoserver-users
Ing. Alessio Fabiani
Con riferimento alla normativa sul trattamento dei dati personali (Reg. UE 2016/679 - Regolamento generale sulla protezione dei dati “GDPR”), si precisa che ogni circostanza inerente alla presente email (il suo contenuto, gli eventuali allegati, etc.) è un dato la cui conoscenza è riservata al/i solo/i destinatario/i indicati dallo scrivente. Se il messaggio Le è giunto per errore, è tenuta/o a cancellarlo, ogni altra operazione è illecita. Le sarei comunque grato se potesse darmene notizia.
This email is intended only for the person or entity to which it is addressed and may contain information that is privileged, confidential or otherwise protected from disclosure. We remind that - as provided by European Regulation 2016/679 “GDPR” - copying, dissemination or use of this e-mail or the information herein by anyone other than the intended recipient is prohibited. If you have received this email by mistake, please notify us immediately by telephone or e-mail.
