Designing and Implementing Business Process Models : Configuring the VCS Integration Feature : Security Considerations : About VCS Users : User Mappings for Visual SourceSafe and Subversion
User Mappings for Visual SourceSafe and Subversion
Integration Server users gain access to the Visual SourceSafe or Subversion repository by being mapped to a Visual SourceSafe or Subversion user name and password. Each Integration Server user can map him or herself to a Visual SourceSafe or Subversion user. Integration Server users with administrator privileges can create mappings for other Integration Server users. For more information, see Configuring Access to the VCS Repository.
The VCS Integration feature uses Visual SourceSafe or Subversion user credentials to interact with the Visual SourceSafe or Subversion repository; this means the Visual SourceSafe or Subversion user credentials must be stored on Integration Server. The VCS Integration feature encrypts the password portion of the credentials and stores the passwords in encrypted format.
The VCS Integration feature maintains the user mappings in the users.cnf file in the Integration Server_directory \instances\instance_name\packages\WmVCS\config directory. However, anyone with write access to the users.cnf file can open the file and modify the mappings. Because the VCS Integration feature encrypts the passwords for the Visual SourceSafe or Subversion users, a malicious user cannot gain access to the Visual SourceSafe or Subversion repository by defining a new mapping in the users.cnf file, but operation of the VCS Integration feature can be disrupted if entries in the users.cnf file are deleted or corrupted. It is recommended that you set permissions on the users.cnf file so that only trusted users have write access to the file.
Copyright © 2016 Software AG, Darmstadt, Germany.

Product LogoContact Support   |   Community   |   Feedback