Beginning with Release 2.4, system administrators will have more control over local Snarl installations within their corporate environment. Control will initially be based around centrally managed configuration files but may be expanded into Group Policy Objects over time.
This page explains the current proposed functionality available to system administrators. Note that this is very much work in progress.
This document is aimed at system administrators in corporate or educational environments who wish to control access to deployed instances of Snarl running on multiple computers.
Briefly, the process is as follows:
Snarl administration is based around simple configuration files which are easy to edit and distribute.
When Snarl starts it will look to see if there is a file called sysconfig.ssl in the current program directory (typically this will be /Program Files/full phat products/Snarl/). This file is a simple INI-style text file which should contain a single entry:
The configuration folder can have any name and can reside at any (accessible to the user) location. This allows system administrators to provide rudimentary role-based Snarl configuration by deploying multiple sysconfig.ssl files with different target folders to different groups of computers. For example, the Development Team may use configuration folder //server1/snarl/dev_team/ while the Call Centre staff may use the more restrictive //server1/snarl/callcentre/ folder instead. This is achieved by deploying different sysconfig.ssl files to the appropriate machines.
To avoid user interference with the sysconfig.ssl, administrators should ensure that users only have read access to this file on their computer.
This should follow the same structure as the Snarl user configuration folder created as part of the Snarl installation. Specifically it must contain an /etc/ folder to be considered valid. The folder need not contain any other files; these will be created dynamically by Snarl as required.
This is a new file which contains administration settings specific to Snarl. Note that the contains of this file may be subsumed into the existing .snarl file in future revisions. This file must exist in the supplied Snarl configuration folder for it to be loaded by Snarl.
The following settings are currently available:
Some points to note:
To try this out, do the following: