[Geoserver-users] Flaw in Service activation?

GeoServer GeoServer User
1

L.S.

WMR has recently upgraded to GeoServer 2.20.1 (weeks) and a few days ago we noticed that for a Workspace intended to only server WMS the WFS-service was also active.

Possible flaw 1: GeoServer is to lenient during an upgrade and activates e.g. WFS on workspaces/stores/layers that were defined as WMS-only.
I am not sure that this has happened during the latest upgrade, it may have happened earlier. Which actually makes it worse as we may have leaked data for much longer.

I have checked the changelogs for recent versions and have not noticed warnings about such behaviour/changes.

To remedy the leak I have started at the top level with attempts to deactivate the WFS-activation.

However setting WFS to inactive and only leaving WMS active for the Workspace did give the desired result.

Next the Stores that are involved where change to only have WMS active. Still the layers were visible for WFS.

Finally each layer that should not have a WFS has been modified and only then did the unwanted WFS-layers disappear.

I have used [Reload]-button from the Server Status pages in between changes, expecting that that would activate my edits.

Possible flaw 2: Deactivating WFS (or WMS or …) apparently does not propagate down to the lower levels. Which I expect is not how this is intended to work as it results in much more administrative work.

Interested in knowing whether other have come across this behaviour. You may have to check for this.

Interested in how I may have misinterpreted the settings, thus lumbering myself with all that extra work.

Kind regards,

Jan Tjalling van der Wal

Wageningen Marine Research (IMARES) Institute for Marine Resources & Ecosystem Studies

Ankerpark 27, 1781 AG Den Helder

Postbus 57, 1780 AB Den Helder

Tel. +31 (0)317-4 87147 #

GSM +31(0)626120915 (privé) #

Ma+Di 09:00-18:00, Wo XX, Do+Vr 09:00-18:00

Jan_Tjalling.vanderWal@anonymised.com

WUR_RGB_standard

www.wur.nl/marine-research (NL) / www.wur.eu/marine-research (ENG)

www.disclaimer-nl.wur.nl / www.disclaimer-uk.wur.nl

2

Keep in mind that the “global” settings for WM, WFS, WCS act more as defaults; enabling workspace WFS is really only enabling an override so you can customize the service title and description (for example) when accessing the virtual WFS service for that workspace.

So how did you have it setup? Did you enable the workspace WFS override, and then go into those settings and disable the WFS?

Jody

image001.png

···

–
Jody Garnett

3

Hi Jody,

Thanks for that first and quick reaction.

I admit that initially I had the WFS-override inactive. But as that did not result in the expected result, I explored further. Found the options behind and tried again.

I have worked my way down the hierarchy in attempts to deactivate the unwanted WFSs.

For the workspace I have activated the override, then used the link that gets activated (text WFS becomes clickable when the tick is present).

To disable the WFS-option. As shown below.

Saved those changes, reloaded the configuration.

And checked whether the WFS I wanted to disable were no longer offered.

Alas, they were still showing.

Next I did similar modifications to the settings for the datastore(s).

No fresh screenshots taken, as they would be very similar to the ones above.

Still WFS were showing.

Then finally I modified each layer like shown below.

All in all I think I have gotten this override thing handled correctly.

I had expected that the actions with Workspace (preferred, least amount of work) or with Stores would have resulted in disabling WFS for all layers underneath.

Unfortunately not.

Please note that initially the tickmark for Selectively enable services for layers was not set. Therefore the layers should have followed their containers setting (no WFS once those were disabled).

For me the way it now works is not as expected.

Kind regards,

Jan Tjalling van der Wal

Jan_Tjalling.vanderWal@anonymised.com10991…

Tel. +31 (0)317-4 87147 #

GSM +31(0)626120915 (privé) #

Ma+Di 09:00-18:00, Wo XX, Do+Vr 09:00-18:00

image001.png

···

From: Jody Garnett jody.garnett@anonymised.com
Sent: 20 January 2022 21:58
To: Wal, Jan Tjalling van der jan_tjalling.vanderwal@anonymised.com
Cc: geoserver-users@lists.sourceforge.net
Subject: Re: [Geoserver-users] Flaw in Service activation?

Keep in mind that the “global” settings for WM, WFS, WCS act more as defaults; enabling workspace WFS is really only enabling an override so you can customize the service title and description (for example) when accessing the virtual WFS service for that workspace.

So how did you have it setup? Did you enable the workspace WFS override, and then go into those settings and disable the WFS?

Jody

On Thu, Jan 20, 2022 at 7:31 AM Wal, Jan Tjalling van der <jan_tjalling.vanderwal@anonymised.com> wrote:

L.S.

WMR has recently upgraded to GeoServer 2.20.1 (weeks) and a few days ago we noticed that for a Workspace intended to only server WMS the WFS-service was also active.

Possible flaw 1: GeoServer is to lenient during an upgrade and activates e.g. WFS on workspaces/stores/layers that were defined as WMS-only.
I am not sure that this has happened during the latest upgrade, it may have happened earlier. Which actually makes it worse as we may have leaked data for much longer.

I have checked the changelogs for recent versions and have not noticed warnings about such behaviour/changes.

To remedy the leak I have started at the top level with attempts to deactivate the WFS-activation.

However setting WFS to inactive and only leaving WMS active for the Workspace did give the desired result.

Next the Stores that are involved where change to only have WMS active. Still the layers were visible for WFS.

Finally each layer that should not have a WFS has been modified and only then did the unwanted WFS-layers disappear.

I have used [Reload]-button from the Server Status pages in between changes, expecting that that would activate my edits.

Possible flaw 2: Deactivating WFS (or WMS or …) apparently does not propagate down to the lower levels. Which I expect is not how this is intended to work as it results in much more administrative work.

Interested in knowing whether other have come across this behaviour. You may have to check for this.

Interested in how I may have misinterpreted the settings, thus lumbering myself with all that extra work.

Kind regards,

Jan Tjalling van der Wal

Wageningen Marine Research (IMARES) Institute for Marine Resources & Ecosystem Studies

Ankerpark 27, 1781 AG Den Helder

Postbus 57, 1780 AB Den Helder

Tel. +31 (0)317-4 87147 #

GSM +31(0)626120915 (privé) #

Ma+Di 09:00-18:00, Wo XX, Do+Vr 09:00-18:00

Jan_Tjalling.vanderWal@anonymised.com

WUR_RGB_standard

www.wur.nl/marine-research (NL) / www.wur.eu/marine-research (ENG)

www.disclaimer-nl.wur.nl / www.disclaimer-uk.wur.nl

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

4

Thanks for the detailed testing and notes; I expected the WFS setting (ie disabled) to be picked up as a default by the workspaces and layers.

Can you make a bug report with the notes you have collected please.

Jody

image001.png

image006.jpg

image007.jpg

image010.jpg
image010.jpg1054×757 41.4 KB

···

–
Jody Garnett