[Feature Request]: Enable WFS-T (Editing) via LWC's shared URL

[meyerlor]

What is the bug? (in English)

If i share the WFS of a LWC project and add layers from it to a QGIS project, i can not edit the layer. The user used to login/access the WFS has appropriate rights in Lizmap.

Steps to reproduce the issue

1. Publish Project via LWC
2. Get WFS URL via LWC metadata, add as connection in QGIS
3. Add layer from connection
4. Edit not possible (can not even activate it)

Versions, safeguards, check summary etc

Versions :

• Lizmap Web Client : 3.8.11 - commit 51c30f8 51c30f8fd
• Lizmap plugin : 4.5.3
• QGIS Desktop : 3.40.8
• QGIS Server : 3.40.7
• Py-QGIS-Server : 1.9.4
• QGIS Server plugin atlasprint : 3.4.2
• QGIS Server plugin lizmap_server : 2.13.1
• QGIS Server plugin wfsOutputExtension : 1.8.3

List of Lizmap Web Client modules :

* altiProfil : 0.5.9 * altiProfilAdmin : 0.5.9

List of safeguards :

* Mode : normal
* Allow parent folder : no
* Prevent other drive : yes
* Prevent PG service : yes
* Prevent PG Auth DB : yes
* Force PG user&pass : yes
* Prevent ECW : yes

Check Lizmap plugin

• I have done the step just before in the Lizmap QGIS desktop plugin before opening this ticket. Otherwise, my ticket is not considered valid and might get closed.

Operating system

Ubuntu 24.04

Browsers

Firefox

Browsers version

Latest FF

Relevant log output

[meyerlor]

I found out by reading the code etc that WFS-Transaction is probably not wanted by design - so i tried exposing py-qgis-server to the web (behind a password ofc) - but py-qgis-server also does not seem to support WFS-T. Can you confirm this @Gustry ? And do you have a suggestion how to make WFS-T somehow work? I really need that data to be editable via WFS - direct postgres connections are not possible due to the customers firewall.

[rldhont]

@meyerlor

• Did you configured WFS layers as editable in the QGIS Project properties ?
• Does your WFS GetCapabilities contain edition capabilities ?

[meyerlor]

@rldhont I had them configured and checked the boxes for Add, Update & Delete. After a while, I found the problem in the settings of py-qgis-server. I followed the documentation when installing it without thinking about it much. Changing the setting in /srv/qgis/config/qgis-service.env from QGIS_SERVER_FORCE_READONLY_LAYERS=TRUE to false enabled WFS-T for those layers.

For now this is fine for me, but I would love to have Lizmap's user/rights management for WFS (instead of having to directly use py-qgis-server as the WFS server). Do you think that's possible as a roadmap goal for Lizmap? Sponsoring it would be possible from our side, I think. It would be awesome to have proper rights management like Lizmap offers for WFS services.

I often have the use case where 95% of users are fine with LWC, but some power users need to work with QGIS on the same PostgreSQL layers. Since many corporate firewalls won't accept direct PostgreSQL connections (the port is blocked), I need to make use of WFS, which is not blocked.

[guenterw]

I feel the same way as @meyerlor. WFS-T for use in QGIS for users who cannot access the PG database is necessary. This also works perfectly without the Py-QGIS-Server.
Even changing the variable “QGIS_SERVER_FORCE_READONLY_LAYERS” to ‘false’ (or “FALSE” ?) does not work for me. The loaded WFS service cannot be edited.
With the same project from an older server without Py-QGIS-Server it works as usual.
Is there anything else that needs to be considered?