Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved


Chapter 11 Configuring Access Control for a Project : Working with Access Control Files

Working with Access Control Files
Access control settings are created using XML files with the extension .ac. You can create or modify an RMSProjectName.ac file using any XML editor. This section explains the elements used to define access control, ways you can add or edit access control files, and where to place the files so they can be used by the RMS, Decision Manager components, and TIBCO BusinessEvents WebStudio.
Examples shipped with the product contain access control files you can use as models.
Required Location of Access Control Files
The access control file for an RMS project must be placed in the location specified by the RMS server CDD property ws.projects.acl.location. An RMS project’s ACL file must be named using the format RMSProjectName.ac.
Specifying and Grouping Project Resources
In the resources element, you group the project resources in whatever way supports the permissions you want to set. You give each grouping or individual resource an ID that is used when defining the permissions.
Using Resource Type as a Filter
How you specify the resource group is partly determined by the resource type attribute. The resource type can act as a filter. For example, suppose in the name attribute you specify a directory that includes events and concepts. If you set the type attribute to "CONCEPT" then the ID associated with this grouping is used to set permissions only on the concepts in that folder (and its subdirectories).
You could create a second grouping whose type specifies "EVENT" so that you can set permissions on events in that folder branch separately.
Specifying an Individual Resource
To specify an individual resource, provide the project path to the resource in the name attribute. The project path is the folder path to the ontology entity, as seen in the Explorer panel. The example below shows how to specify an ID that is associated with the FirstName property of the Person concept:
<resource name="/Concepts/Person/FirstName" id="FN" type="PROPERTY"/>
Grouping Resources Using Wildcards
You can associate groups of resources with an ID using the wildcard character in the project path. The asterisk (*) is used as the wildcard character. For example:
<resource name="/someFolder/* "id="AllP" type="PROPERTY"/>
Grouping Resources by Resource Type
The broadest resource grouping is provided by setting permissions at the level of resource type. This method groups all resources of that type in the project. To set a resource type resource group, you associate an ID with a resource type, and you do not use the name attribute:
<resource id="ID" type="ResourceType"/>
For example: <resource id="C" type="CONCEPT"/>
See Table 34, Resource Types and Their Allowable Action Types for a list of resource types, and the action types that are valid for each resource type.
Defining Permissions
As explained in Specifying and Grouping Project Resources, you define a list of resource IDs according to the way you want to group resources and actions. All items included under one resource ID must be of the same resource type (or type of activity, such as checking out a project).
For each user role you add a set of permissions.

 
   <role name="Administrator"/>
   <permissions>
      <permission resourceref="#PRJ">
         <action type="checkout">ALLOW</action>
      </permission>
. . . . . . . . . . . . . . . . . . . . . . . . . .
   </permissions>

 
Each resourceref points to a resource ID. You create permissions using the actions available for the resource type specified for that ID, such as create, read, and modify. See Table 34, Resource Types and Their Allowable Action Types for the resource types and their available action types.
By default, all permissions are denied. If a certain permission is not explicitly given to a role, then the role does not have the permission. This approach ensures unauthorized users do not accidentally gain access to restricted resources.
Permissions are not hierarchical. That is, a create permission does not imply a modify permission or a read permission. All privileges are mutually exclusive. So, for example, if you want users to be able to modify some resources of a certain resource type, be sure to also give users the ability to view that resource type.
Note that for use in TIBCO BusinessEvents Decision Manager, most TIBCO BusinessEvents project resources have only a read action type.

Copyright © TIBCO Software Inc. All Rights Reserved
Copyright © TIBCO Software Inc. All Rights Reserved