Hi Andrea,
Sure. To clarify, my goal is to add data to WFS transaction which will
influence how it is written to Accumulo (and consequently queried back
out). In some sense, it'd be akin to providing ingest hints /
instructions. For example, suppose that some data could only be seen by
'ad
On Fri, Apr 8, 2016 at 4:09 PM, Jim Hughes wrote:
> My high-level goal is to find a way to add security info to a WFS
> transaction.
Can you elaborate why just an authentication + authorization rules
would not work?
Cheers
Andrea
--
==
GeoServer Professional Services from the experts! Visit
Cool, yeah I think the TransactionPlugin could have some interesting uses
for sure, I think it’s kind of under utilized.
Re the user data attributes I think personally think it could be general
enough. The whole user data idea about shuffling attributes along that you
don’t want to model explicitl
Hi Justin,
Thanks. I forgot to mention that I had seen the TransactionPlugin
extension point; that one is awesome and I see how to use it support my
second suggestion.
Would changes in the GML2/3ParsingUtils to inject attributes into a
SimpleFeature's userData be sensible / more broadly use
Hey Jim,
The wfs native element might be the cleanest way to handle this. I’ve seen
folks use it before for security and validation type stuff with some
success. In GeoServer you can plug in WFS transactions callbacks pretty
easily using the TransactionPlugin
<[https://github.com/geoserver/geoserv
Hi all,
Apologies for the cross-post, but my question hits a little of how
GeoServer handles WFS transactions and a little bit of how GeoTools may
handle WFS/GML parsing.
My high-level goal is to find a way to add security info to a WFS
transaction. I can see three big options: 1. add some b
