-adding possiblity to mark fields as "masked"

[peterneubauer]

• they are searchable via CQL filters, but the output is set to null in order to prevent accidental discovery of e.g. UUIDs that are private for just one customer. Feedback on this feature welcome before writing some tests.

[sjudeng]

I think for this you could use the propertyName parameter in your WFS/WMS requests to limit the attributes that you want included in the response.

http://docs.geoserver.org/latest/en/user/services/wms/vendor.html#propertyname

[peterneubauer]

Thing is, this should be decided not by the request but in the layer setup in order to constrain the fields exposed. On Jun 23, 2015 7:13 PM, "sjudeng" notifications@github.com wrote:

I think for this you could use the propertyName parameter in your WFS/WMS requests to limit the attributes that you want included in the response.

http://docs.geoserver.org/latest/en/user/services/wms/vendor.html#propertyname

— Reply to this email directly or view it on GitHub https://github.com/ngageoint/elasticgeo/pull/7#issuecomment-114575509.

[sjudeng]

In this case you might not want to allow public access to your GeoServer instance. GeoServer API calls could be managed by your services/applications which, among other things, can incorporate the logic to limit the attributes included in GetFeature/GetFeatureInfo responses.