Andrea, thought I'd chime in from MassGIS on what we're looking for in security.
We are currently serving 602 layers. 99% of them are public, meaning full access. We would not want any need for authentication to see or use these layers. We want users to be able to use these layers in as many clients as possible (ArcMap, uDig, OpenLayers, Google maps, etc). There are a few layers for which we hide certain fields, this already can be done. There are a few layers for which we limit WFS features, this already can be done. (make the user work with one feature at a time). There are a few layers which I haven't loaded into GeoServer yet because I would like only certain users to access them. I don't think we care if people know that they exist (see them in a GetCapabilities) (although if they didn't, that would be a plus), but the key is that only authorized users can do WMS/WFS with these layers. Maybe we fall in the MIXED category then. There are few layers that are editable and we'd like to set up authorization so that only certain users can edit these layers. -- View this message in context: http://www.nabble.com/Some-amendments-to-the-per-layer-security-proposal-tp18321497p18363936.html Sent from the GeoServer - Dev mailing list archive at Nabble.com. ------------------------------------------------------------------------- Sponsored by: SourceForge.net Community Choice Awards: VOTE NOW! Studies have shown that voting for your favorite open source project, along with a healthy diet, reduces your potential for chronic lameness and boredom. Vote Now at http://www.sourceforge.net/community/cca08 _______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
