Topic 6.2.1: Overview
- Systems
- The Security System panel allows the definition of new security systems and the configuration of the existing ones.
- A security system is a group of layers and instance exceptions that will be available at the runtime. Security systems used along with security roles and security users allows defining witch layers and instances are available to which users.
- GISIZE GEOSpatial security is effective at the repository level. That means each repository has its own security configuration. Security is enabled or disabled at the Administration panel of each repository.
- By default, a GISIZE GEOSpatial repository comes without security and no security system defined.
- Roles
- The Security Roles panel allows the definition of new security roles and the configuration of the existing ones.
- A security role is a combination of application permissions and security systems that defines the user’s capacity to interact with the repository at the design time and the runtime.
- GISIZE GEOSpatial security is effective at repository level. That means that each repository has its own security configuration. Security is enabled or disabled at the Administration panel of each repository.
- By default, a GISIZE GEOSpatial repository comes without security but with a read-only ‘Administrator’ security role defined.
- Role Permissions
- This is a tree view control that allows the selection of the available design time permissions at the current security role. Existing permissions are just selectable, not editable. Permissions are self-explanatory and are:
- Administration – Can Create/Modify/Delete Repository
- Administration – Can Generate Runtime Repository/File
- Map Providers – Can Create/Delete Map Providers
- Map Providers – Can Modify Map Providers
- Security Systems – Can Create/Delete Systems
- Security Systems – Can Modify Systems
- Roles – Can Create/Delete Roles
- Security Roles – Can Modify Roles
- Security Roles – Can Modify ‘System-Role’ relations
- Security Users – Can Create/Delete Users
- Security Users – Can Modify Users
- Layers – Can Create/Delete Layers
- Layers – Can Modify Layers
- Navigation Models – Can Create/Delete Navigation Models
- Navigation Models – Can Modify Navigation Models
- Templates – Can Create/Delete Templates
- Templates – Can Modify Templates
- Instances – Can Create/Delete Instances
- Instances – Can Modify Instances
- MultiLanguage – Can Create/Delete Languages
- MultiLanguage – Can Modify Languages
- Can Start Runtime Preview.
- This is a tree view control that allows the selection of the available design time permissions at the current security role. Existing permissions are just selectable, not editable. Permissions are self-explanatory and are:
- Users
- The Security Users panel allows the definition of new security users and the configuration of the existing ones.
- A security user is a GISIZE GEOSpatial user with one or more security roles associated. The user will have sum of all the permissions and security systems of the assigned roles that defines the user’s capacity to interact with the repository at the design time and the runtime.
- GISIZE GEOSpatial security is effective at the repository level. That means that each repository has its own security configuration. Security is enabled or disabled at the Administration panel of each repository.
- By default, a GISIZE GEOSpatial repository comes without security and no security user defined.
Last modified: Wednesday, 6 May 2020, 10:29 AM