This is the documentation to setup a new CVS repository using the CvsNt software. In our setup we have a top level repository with "sub-repositories" for each customer beneath that. Employees log into the master repository, customers log into their specific repository. This needed to be done because CVS requires "list" permissions in the root directory or it pukes and we didn't want customers to be able to see each others directories. -- AdamShand

Introduction

The main purpose of moving to CvsNt was to allow the application engineers to have decent levels of control over their repositories. Because of the dynamic nature of their interaction with customers their CVS needs are quit different then the majority of our other CVS users.

The AE CVS server lives in a domain called DOMAIN. Since this is a different domain then our main Domain, new user accounts must be created in order to gain access to the CVS repositories. With this setup there are two ways of controlling access to repositories with our CvsNt configuration.

Using Repositories

Each company that we work with gets their own repository. The repository will be have a directory path of /cvsroot/CUSTOMER. This means that each company can only access from that point and lower in the directory hierarchy.

Using File Permissions

File permissions are what do the majority of the security work. Because all users belong to the same domain (both external employees and customers) technically any user can log into any repository. What stops this from happening is file permissions. In order to log in to a CVS repository the user must have the ability to read the CVSROOT/* files, and we set the permissions so that each customer can only read their own files.

Maintenance Tasks

Connecting to the CVS Server

In order to manage users, groups and repositories you need to log into the CVS server.

Adding a new Employee

All employees have privileged access to the CVS repository and can see all company repositories with a single log in. To create a new account:

Once created they should be able to log in with this CVSROOT (where USER is their username):

Setting up a New Company and Repository

When we start collaboration with a new customer and need a CVS repository setup here's what you do.

You are now ready to add users for that company.

Adding a User

Before you can add a users account their company repository and group needs to already exist. If it doesn't please do that first.

Once created they should be able to log in with this CVSROOT (where USER is their username and COMPANY is the name of the repository you just created):

Resetting a User's Password

If a user has forgotten their password or needs it changed for security reasons (eg. someone else knows their password) you can change their password by:

Enabling or Disabling a User's Account

If you wish to disable an account:

To enable a disabled account do the same thing only choose "Enable Account". You will be able to tell if the account is disabled by the red circle with an X in it before their name.

Removing a Company's Access

Most of the time you won't want to actually remove a repository, you will just want to revoke a companies ability to access it.

Removing a User

When a user no longer works for the company or is no longer working on a project their account should be removed:

Administrative Notes


CategoryGeek

CvsNtAdministration (last edited 2003-03-27 16:57:12 by AdamShand)