[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

Re: Test login

From: Fabian Cenedese <Cenedese_at_indel.ch>
Date: 2005-09-15 13:52:53 CEST

>> Is there a command to check if the user credentials are already known
>> or would be asked if e.g. a commit was performed? I have a script which
>> does perform various tasks and also a commit and I don't want it to
>> stop in the middle because it needs user password or even worse will
>> fail because of a wrong password.
>> CVS has the login command to do this step by itself so further commands
>> wouldn't need a password again. I already have the
>> [auth]
>> store-auth-creds = yes
>> but that still needs to be filled first. So I'd like to do the login step
>> without actually doing a command on the repository.
>I don't know of a way to test for write permission without actually changing
>something since commit doesn't take a dry run option (AFAICT).
>How about this idea - have a dummy repository or part of a repository that
>requires authentication and authorisation to be able to read from it, assign
>the same user you want to test permission for to this special area and do a
>svn ls on the area at the start of your script?

In this case the script will still ask for a password so it's not really better.
But I just found the --non-interactive flag that will just fail if the user is not
known. So I could make the script fail before it does anything else. Now
I just need another way to ignite authentication. I don't like the dummy
repository idea that much. Maybe the locked down read access is a
better way. Need to think it over.

Thanks for ideas.

bye Fabi

To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org
Received on Thu Sep 15 13:54:59 2005

This is an archived mail posted to the Subversion Users mailing list.

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.