Re: [stellation-res] why doesn't stellationd require a "password" argume

["Mark C. Chu-Carroll" <mcc@xxxxxxxxxxxxxx>]

On Monday 22 July 2002 10:41 pm, Florin Iucha wrote:
> On Sun, Jul 21, 2002 at 08:38:58AM -0400, Mark C. Chu-Carroll wrote:
> > When you access a repository, by default, it gets your username
> > from either the "--username" parameter, your .svcrc file, or
> > your login name, in that order. For the password, it's the "--password"
> > parameter, then the .svcrc file.
>
> It's not working. Check bug 21791.

I think it is working, and you're actually seeing a different bug, but I want 
to verify it before I do anything in bugzilla. I'm able to use "--user" and
"--password" myself with no problem; they seem to work fine, with
multiple usernames, with correct response for both valid and invalid
usernames and passwords.

Based on your bugzilla report, I think you're misusing the commands in
an interesting way, which is revealing a different bug.

You say "assume a repository created by "scott" with the password "tiger"."

You then go on to do a "configure username" for scott. First problem: there
is no command test username, and on my system, it properly returns
an error. This may just be a typo in your example. If it's not, then it's
a different bug.

In any case: assuming you did a "config user". It should *still* have
failed;  configure user takes two parameters: the name and password
of the new user to create.

Assuming that that's also just a typo, then you're adding a duplicate 
username, which should be an error. IT looks like *that* would get 
past the system, which is definitely a bug. We need a key constraint 
in the database to prevent that from happening. 

So, moving on. Once the system erronneously creates two users with
the same username, things get wierd, and you'll see unpredictable
behavior if you log in with the username that has two entries in
the users table. 

So... I think that that's the cause of your problem, not that "--password"
doesn't work.


Does this make sense with what you're seeing?

Can you try creating a different user, like:
	svc --location=... config user mcc test

And then try 
	svc --location=... --username=mcc --password=test -v test connect

And see if it works? 

Thanks!
	-Mark



>
> > So, for another user to access the repository, you'd do an
> > "svc configure user". Then the user would put their
> > username and password into their .svcrc file, and then use svc.
>
> florin

-- 
Mark Craig Chu-Carroll,  IBM T.J. Watson Research Center  
*** The Stellation project: Advanced SCM for Collaboration
***		http://www.eclipse.org/stellation
*** Work Email: mcc@xxxxxxxxxxxxxx  ------- Personal Email: markcc@xxxxxxxxxxx