Community technical support mailing list was retired 2010 and replaced with a professional technical support team. For assistance please contact: Pre-sales Technical support via email to email@example.com.
Thanks Peter. That is one option which seems to work. It may not be possible for me to convert my organisation to using sspi instead of pserver. If this is the case, do you know of a way I can get pserver to work using domain accounts? Thanks again, Estelle On 1/31/08, Peter Crowther <Peter.Crowther at melandra.com> wrote: > > From: Estelle Carr > > I now want to start using the Windows domain accounts instead. So I > > added an entry to the passwd file as follows: > > > > alias::domain\username > > > > However, when I try to login as 'alias' the CVS client says: > > > > Fatal error, aborting. > > cvs [login aborted]: domain\username: no such user > > > > This user is definitely a domain user, as I can login to the > > server with it. > > > > Does anyone have any ideas what might be wrong? > > Assuming your workstations and CVSNT server are all in the same domain, > there are no irritating firewalls in the way, and you want users to use > their Windows authentication: > > - You should use SSPI as your authentication mechanism. Each user's CVSROOT > should be something like :sspi:cvsserver:/repo - note the lack of any user > identity in there! > > - Users should *not* use cvs login. If they already are, they should cvs > logout. cvs login doesn't work with SSPI. > > Everything should magically work then, although you might have some fun > updating sandboxes with the new root. WinCVS has a macro to do this, for > example. > > - Peter >