You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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:
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
If the administrator try to change context's permissions, a confirmation dialog must appear to confirm the following action:
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.
The text was updated successfully, but these errors were encountered:
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
Since there is a relationship between an application context and maps created within it, there must be specific rules to prevent inconsistent states like:
Below are the constraints and actions that need to be developed to enhance the Application Context tool:
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
If the administrator try to change context's permissions, a confirmation dialog must appear to confirm the following action:
The text was updated successfully, but these errors were encountered: