-
Notifications
You must be signed in to change notification settings - Fork 25
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature editor doesn't handle geOrchestra's roles #414
Comments
as seen in the call today, none of the mapstore plugins provide integration with georchestra roles for now..... upcoming improvement. |
yes it's not very friendly :/ |
I tried to use the current available configuration with the "Can view" and "Can edit" functions to find a solution. I supposed that "Can view" activate the "USER" role and "Can edit" activate the "ADMIN" one. @tdipisa Are the "Can edit" and "Can view" mapstore's permissions activating some mapstore's role that we can use in plugins configuration ? |
On my side I found that "can edit" applied on an application context allows the users of this context to modify the backgrounds (delete, add,...) |
Hi, |
Fixed in : geosolutions-it/MapStore2#9179 |
When configuring the attribute table with "editingAllowedRoles" options, we only have choice between "ADMIN" or "USER".
If we add some geOrchestra's defined roles, it not restrict the edit tools display.
As all connected user have the mapstore's "USER" role, add it to allowed roles means every connected user have edit tools displayed.
The text was updated successfully, but these errors were encountered: