I like the idea, care should be taken in the description as this is not the only security consideration in play when trying to access a layer.
Thoughts for discussion: - Consider moving to a security heading on the Data tab to be clear it is about the raw data itself... not sure I like it. - Not all the data restrictions are defined layer-by-layer, how do you wish to show the workspace restrictions? "tiger.*" in your example? One though would be to add a similar tab to the workspace screen, .. - To communicate workspace restrictions a text description of the workspace restrictions could be provided below the proposed roles table - This may also be a good though to provide a summary of the service restrictions in play for the layer? - A better thought would be to show the workspace restrictions in the same roles table, but grayed out and not editable ... - Do we need to consider the tileset permissions separately? Putting the above together: a) add "name" column to the roles table so both "tiger.*" and "tiger.tiger_roads" are listed b) workspace rows are grayed out, only used to communicate data access restrictions already in place c) consider adding a similar tab to the workspace screen if you want to go for consistency -- Jody Garnett On Thu, 10 Oct 2019 at 02:26, [email protected] < [email protected]> wrote: > Dear all, > > I would like to submit to your attention the following geoserver > improvement proposal: > > https://github.com/geoserver/geoserver/wiki/GSIP-182. > > Best regards, > Marco Volpini > _______________________________________________ > Geoserver-devel mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/geoserver-devel >
_______________________________________________ Geoserver-devel mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/geoserver-devel
