Subsections
WANdisco Security Agent provides security services for a Software Configuration Management (SCM)
repository such as CVS or
Subversion. It allows an SCM user to transparently connect to the SCM repository via a network proxy that acts as a security agent. The SCM user connects to the Security Agent on the standard SCM port (configurable) such as
2401 for CVS,
3690 for Subversion,
80 for Subversion-HTTP. The Security Agent in turn connects to the underlying SCM repository server.
In this administration guide, you will learn how to easily setup WANdisco Security Agent.
- SCM Repository
- Software Configuration Management repository like CVS or Subversion.
- SCM Server
- A network server that provides remote access to an SCM Repository
- Group Resources
- A list of file or directories a group has access to.
- Principal
- A security term for a User or Group
- Security Agent
- The intermediary that acts as an application proxy or gateway between the SCM client and the SCM server. Each Security Agent has an associated SCM Repository. This agent is responsible for enforcing security policies, Role based access control (RBAC) setup by the administrator.
- Security_Agent_root directory
- The base directory under which WANdisco Security Agent is installed.
- GUID
- Globally Unique Identifier. WANdisco Security Agent use 16 byte DCE UUIDs.
This guide is intended for an SCM administrator or a user who is reasonably
comfortable with:
- Setting up a CVS or Subversion repository
- Configuring inetd/xinetd service on Unix, Cygwin or Windows platform
- Installing Perl and required Perl modules
- Installing Apache 2.0+ server if using Subversion/HTTP protocol
- Installing Java
- Unix or Windows system administration
- Reading the WANdisco Security Agent administration guide
cover-to-cover
If you don't meet the above pre-requisites you may want to contact your SCM administrator.
