How should I protect the Repository from unwanted changes?

Top  Previous  Next

CS-RCS supports security settings which are sufficient in most scenarios. The server security features protect the repository from any unauthorized access by non-team members and external users. However, as the repository resides on a shared server drive, it may be exposed to unauthorized access by non-cooperative team members. If you manage mission-critical projects and wish to avoid any unauthorized operations, you should use the RCSBrowser add-on that implements a true client/server architecture. When using the RCSBrowser add-on, access to the repository is done through authorized protocol calls only. This ensures that unauthorized users are unable to manipulate the repository by any mean. For full details, see:
http://www.componentsoftware.com/products/RCSBrowser

If you cannot use the RCSBrowser add-on, you may get better security by using the file-server permission mechanism to control user access to sections of the Repository tree:

·

Set read/write permission for normal users.

·

Set read-only permission for users who need the Repository section for reference only.

·

Set read-only permission to the files CSRCS.STP, prjprm.stp and UsgData.stp at the Repository root, to avoid unauthorized setup changes. This file should have a read-write status only for the CS-RCS administrator.

·

Set read-only permission to the whole Repository root to avoid project creation/changes.

Tip: Backup the Repository regularly.