Page tree
Skip to end of metadata
Go to start of metadata

What

Permissions.xml

Config group

SystemConfigFiles

Required

no

Description

Set permissions for user groups

schema location

http://fews.wldelft.nl/schemas/version1.0/permissions.xsd

What

UserGroups.xml

Config group

SystemConfigFiles

Required

no

Description

Define user groups

schema location

http://fews.wldelft.nl/schemas/version1.0/userGroups.xsd

General

Permissions can be added to the FEWS configuration to allow users (user groups) to access Explorer tasks, Data Editor functions, Filters, etc..  Permissions can be optionally configured in the following configuration files:

  • Explorer.xml
    • Restrict access to explorer tasks such as the Time Series Dialog or the Grid Display. The tasks will not be available in the menus or toolbar for users which do not have the right permissions
  • TimeSeriesDisplayConfig.xml
    • Control who can add and edit values in the data editor window
    • Control who can add and edit labels in the data editor window
    • Control who can add and edit comments in the data editor window
  • ScenarioEditor.xml
    • Control who can create, edit, delete, persist and run scenarios in the scenario editor window
  • GridDisplay.xml
    • Control which displays are visible in the spatial plot window for the current user
  • Filters.xml
    • Control which filters are visible in the FEWS explorer for the current user
  • DisplayGroups.xml
    • Control which shortcuts are visible in the Time Series Display for the current user
  • WorkflowDescriptors.xml
    • Control which users can view, run and approve workflows in the Forecast Dialog and Manual Forecast Dialog.
    • Also control which users can delete forecasts and change expiry times of forecasts in the Forecast Dialog.
    • NOTE: Using permissions on workflows indirectly influences the behaviour of the scenario editor window. Scenario's, based on hidden or non-runnable workflows are not shown in the scenario editor.

Permissions are to be configured as follows

  • Configure optional permission names in any of the above described configuration files.
  • Create the permissions in the permissions configuration file (Permissions 1.00 default.xml) and configure usergroup names which should have access to the permissions.
  • Create the usergroups in in the usergroup configuration file (Usergroups 1.00 default.xml) and assign them user names.

Configure optional permission names

This can be achieved by adding the optional permission tag to the configuration and give it a self-describing name.

Create the permissions configuration file

When available on the file system, the name of the XML file is for example:

      Permissions 1.00 default.xml

      Permissions                             Fixed file name for the permissions configuration

      1.00                                        Version number

      default                                     Flag to indicate the version is the default configuration (otherwise omitted).


Figure 3 Elements in the Permissions configuration

Permissions 1.00 default.xml
<?xml version="1.0" encoding="UTF-8"?>
<permissions xmlns=".....">
	<permission id="AllowDataEditor">
		<userGroup id="Hydroloog"/>
		<userGroup id="Veldmedewerker"/>
	</permission>
	<permission id="AllowManualForecast">
		<userGroup id="Hydroloog"/>
	</permission>
	<permission id="AllowLabelEditor">
		<userGroup id="Hydroloog"/>
	</permission>
	<permission id="AllowCommentEditor">
		<userGroup id="Hydroloog"/>
		<userGroup id="Veldmedewerker"/>
	</permission>
	<permission id="AllowValueEditor">
		<userGroup id="Hydroloog"/>
	</permission>
</permissions>
Permission

Unique name of the permission

Usergroup

Id of each usergroup that is granted the given permission

create the user groups

When available on the file system, the name of the XML file is for example:

      Usergroups 1.00 default.xml

      Usergroups                             Fixed file name for the user group configuration

      1.00                                        Version number

      default                                     Flag to indicate the version is the default configuration (otherwise omitted).


Figure 4 Elements in the Usergroups configuration

UserGroups 1.00 default.xml
<?xml version="1.0" encoding="UTF-8"?>
<userGroups xmlns="....">
  <userGroup id="Veldmedewerker">
    <user id="Stephan Zuiderwijk" />
    <user id="Marc van Dijk"/>
  </userGroup>
  <userGroup id="Hydroloog">
    <user id="Toon van Peel"/>
  </userGroup>
  <userGroup id="SystemUsers">
    <user systemUserGroup="DOMAIN\userid"/>
  </userGroup>
</userGroups>
Usergroup

Base tag for a usergroup configure one for each user group. Usergroups can contain other usergroups. A user group can contain three types of sub-items:

user id = This is the id of the user that is executing the process.

group id = This is a link to an other user group

systemUserGroup = This is fully qualified domain user or domain group. If the executing user is member of the specified system user group then the permissions  assigned to this group are applied.

User

Name of the user that belongs to the usergroup. Users can be placed in multiple usergroups.

Example of permissions in the Explorer XML and TimeSeriesDisplayConfig XML file.

Explorer 1.00 default.xml
....
	<explorerTask name="Data Editor">
		<iconFile>%FEWSDIR%/icons/table.gif</iconFile>
		<mnemonic>E</mnemonic>
		<arguments>table</arguments>
		<taskClass>nl.wldelft.fews.gui.plugin.timeseries.TimeSeriesDialog</taskClass>
		<toolbarTask>false</toolbarTask>
		<menubarTask>true</menubarTask>
		<accelerator>ctrl E</accelerator>
		<permission>AllowDataEditor</permission>
	</explorerTask>
....
TimeSeriesDisplayConfig 1.00 default.xml
....
	<generalDisplayConfig>
		<convertDatum>true</convertDatum>
		<valueEditorPermission>AllowValueEditor</valueEditorPermission>
		<labelEditorPermission>AllowLabelEditor</labelEditorPermission>
		<commentEditorPermission>AllowCommentEditor</commentEditorPermission>
	</generalDisplayConfig>
....
  • No labels