Attribute(s)
Design Templates
Description
Template Security Overview: Explanation of the security issues.
Motivation
This document describes the security related design-issues that are by default implemented in the start template. All template-users should be aware of these issues before they start developing.
Example / Details
Template Security Overview:Start Template
-Default- access: Manager -> CHANGE THIS WHEN INSTALLING THE TEMPLATE ON A SERVER!
Roles: (?ConfigAdmin?) used for application-administrator functionality (e.g. needed for designer and 'super-user').
Only the role AppManager:
- gives read-access to the (not hidden) Application Management views, to be able to maintain documentation, keywords and references.
- gives edit-access to the editor-history number (field T_HistoryNumber) in the subform T-DocumentManagement.
- gives read- and edit-access to the standard header table in the form T-Application Management\Documentation.
Enforce consistent ACL: Enabled (also needed to use roles when working on a local client).
Maximum Internet Access: Editor -> CHANGE THIS ACCORDING TO THE APPLICATION REQUIREMENTS.
Author-fields: none
Reader-fields: None
Signing: Sign the templates with a seperate Sign ID.