Ability to turn off Transactions

Description

Users have requested the ability to turn 'off' transaction capabilities, so that users of their WFS's can not modify their databases. I'm not sure if this is in 1.2 yet or not, but we should get the fix in there, and in a 1.1.1 bug fix release. It should be pretty easy to implement, just have a configuration setting to turn it off, and transactions check with that global value before letting a transaction go through.

Actually, a slightly more elegant approach could be to allow admins to lock all their tables, to make that happen from the web admin interface. Though that would need more testing than just not allowing any access.

Environment

None

Activity

Show:
codehaus
April 10, 2015, 4:25 PM

CodeHaus Comment From: jgarnett - Time: Tue, 10 Feb 2004 13:32:13 -0600
---------------------
<p>2.3.4 Configure Level of WFS Support</p>

<p>GeoServer is compliant with the full "Transactional Web Feature Server" level ofservice as defined by the OGC. The ability to limit the capabilities of GeoServer has been frequently requested.</p>

<p>The OGC defines two levels of service that a Web Feature Server may provide and still remain compliant:</p>
<ul class="alternate" type="square">
<li>Basic WFS:

GetCapabilities, DescribeFeatureType and GetFeature</li>
<li>Transactional WFS:

Transaction operation, with optional LockFeature</li>
</ul>

<p>To meet user requests we propose adding a service level tag to the configuration process.</p>

<p>Intended modification to services.xml:

&lt;service type="WFS"&gt;

&lt;title&gt; My WFS &lt;/title&gt;

...

&lt;serviceLevel&gt;Basic&lt;/serviceLevel&gt;

...

&lt;/service&gt;</p>

<p>The following defines our recommended level of Service.</p>

<p>Basic</p>
<hr />
<p>Operations: GetCapabilities

DescribeFeatureType

GetFeature

OGC: Basic Web Feature Server</p>

<p>Transactional

-------------

Opperations: Transaction

OGC: Transactional Web Feature Server</p>

<p>Complete

--------

Opperations: LockFeature</p>

<p>This recommendation does not interact with the Validation Processor. The Validation Processor, if configured, will be used for all Transaction operations regardless of level of service.</p>

codehaus
April 10, 2015, 4:25 PM

CodeHaus Comment From: cholmes - Time: Tue, 10 Feb 2004 13:57:27 -0600
---------------------
<p>EXTERNAL MESSAGE:

SUBJECT: Re: <span class="error">&#91;jira&#93;</span> Commented: (<a href="https://jira.codehaus.org/browse/GEOS-58" title="Ability to turn off Transactions" class="issue-link" data-issue-key="GEOS-58"><del>GEOS-58</del></a>) Ability to turn off Transactions

Yes, I like the semantic, and it is consistent with what I put in 1.1.1.

It currently just does Basic and non-basic, so the transaction/complete is

a fine addition. Are you planning on featureType level support at this

time? Or control over individual transactions (like update and insert,

but not delete)? Both have been requested, and would be nice to support,

or at least think about while we're on this issue.</p>

<p>&#8211;</p>

codehaus
April 10, 2015, 4:25 PM

CodeHaus Comment From: emperorkefka - Time: Tue, 17 Feb 2004 14:52:41 -0600
---------------------
<p>Just disable the transaction support for 1.2.0 beta, we can hit getCapabilities and locking for 1.2.0</p>

codehaus
April 10, 2015, 4:25 PM

CodeHaus Comment From: dzwiers - Time: Tue, 17 Feb 2004 18:06:26 -0600
---------------------
<p>Fixed for get capabilites and transaction servlet.</p>

codehaus
April 10, 2015, 4:25 PM

CodeHaus Comment From: jgarnett - Time: Fri, 20 Feb 2004 17:53:33 -0600
---------------------
<p>ServiceLevel is now a bit mask to allow separate control of INSERT, DELETE, UPDATE, LOCK</p>

Assignee

Unassigned

Reporter

codehaus

Triage

None

Fix versions

Affects versions

Priority

Medium
Configure