Skip to content
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

Improvement on Context permissions management #189

Closed
tdipisa opened this issue Mar 3, 2020 · 2 comments
Closed

Improvement on Context permissions management #189

tdipisa opened this issue Mar 3, 2020 · 2 comments
Labels
enhancement New feature or request New

Comments

@tdipisa
Copy link
Collaborator

tdipisa commented Mar 3, 2020

Since there is a relationship between an application context and maps created within it, there must be specific rules to prevent inconsistent states like:

  • The final user has permissions to access a map resource but not the related application context resource
  • The application context is deleted so a map within that context is no longer accessible

Below are the constraints and actions that need to be developed to enhance the Application Context tool:

  1. When you create a map in a context, the map must have the same permissions of the context, these permissions cannot be changed by the final user

  2. If the administrator try to change context's permissions, a confirmation dialog must appear to confirm the following action:

  1. If a context is deleted, a confirmation dialog must appear to the administrator to confirm the following action:
  • Use the MS's default context for maps within the deleted context: if confirmed, a batch update request to the MS backend will remove all map attributes containing the ID of the context to automatically use the default one (in that case map permissions can be maintained as they are, the default context is public). Also this point requires Provide Entry point for batch attribute update geosolutions-it/geostore#205.
@tdipisa tdipisa added enhancement New feature or request New labels Mar 3, 2020
@tdipisa tdipisa added this to the Phase IV milestone Mar 3, 2020
@offtherailz
Copy link
Collaborator

offtherailz commented Mar 10, 2020

Increased a little the estimation because "assigning the same permission of the context" in case of user maps may need a little adjustment ( permissions of the context (as other resources) are not accessible for users that has read only access).
One solution is to limit the creation of maps in context by read-only users to only private maps. @tdipisa

@tdipisa
Copy link
Collaborator Author

tdipisa commented Apr 17, 2020

Moved to MapStore as enhancement (geosolutions-it/MapStore2#5149)

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request New
Projects
None yet
Development

No branches or pull requests

2 participants