In our geoserver setup(2.28.0), we have several non-admin users. While admin user has access to ‘Tile Caching’ menu item on left side panel, non-admin users dont’t have.
Without it, how are non-admin users supposed to tile layers as seed/truncate/empty options are available on ‘Tile Caching’ screen only. Attached is the image of menu item I am talking about.
I don’t think they are supposed to be able to do that, it would be a bad idea to let random users truncate your cache.
Ian
Or even starting a seed that migth take hours/days and consume terabytes of disk storage… LOL.
Andrea
Then how would those users do it. They are not programmers to call some API. They need to do it manuall via UI.
If you trust them then you can make them admins alternatively they would need to mail an admin to do it for them. Even the API would require them to authenticate
Ian
Q: When you say non-admin users, are they assigned “workspace admin” permissions (data security permission a) allowing them to edit layer configuration?
If so it would be desirable for these users to take responsibility for truncating / seeding TileSet associated with the layer…
Can you follow the Container Considerations - Workspace Admin instructions and double check please.
So I have created data security rule for such users under Security → Data, like:
.a.
I have also assigned role GROUP_ADMIN.
Seems this is not enough.
Thanks for checking, I also checked by navigating to geoserver/gwc landing page, and although the link for seeding is present access is indeed restricted.
Maybe I can modify the corresponding plugin to workaround it, for my local consumption.
