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

Re: Only one username per realm stored in cached credentials

From: Stefan Sperling <stsp_at_elego.de>
Date: Mon, 21 Jul 2008 10:45:57 +0200

On Sun, Jul 20, 2008 at 08:08:56PM -0500, shannon carey wrote:
> *bump*
> On Mon, Jul 14, 2008 at 9:23 PM, shannon carey <rehevkor5_at_gmail.com>
> wrote:
> In my experience, authenticating to a realm with a certain user/password
> will cause that information to overwrite any other stored credentials
> which were for the same realm.
> Why is this a problem?
> I have two users which interact with my repositories. My main user
> which has rw access but no access to the synched backup repositories,
> and my backup user which has r access but can commit to the synched
> backup repositories.
> The synch is run via a scheduled task, with --username specified as the
> backup user. As long as the backup user's credentials are cached, it's
> ok. However, if I perform a commit and provide my rw user's
> credentials, those overwrite the backup user's credentials... You can
> see the fix I am in.

I don't understand why your two different users step on each other's
caches. Aren't they separate accounts on your client system? If so,
their caches should be in their home directories, separate from each
> I could solve this problem by putting the backup user's password and
> --no-auth-cache (or whatever) directly in the scheduled task's command
> line, but that is less than desirable.
> Does anybody anticipate a way that SVN could allow multiple user
> credentials to be cached per realm?

No, the auth data is keyed by realm internally. Subversion assumes
that auth data is stored per system user on the client system.
I don't know why this does not seem to be the case for you though.
Are you sure your real and your backup user run under different
user IDs?


  • application/pgp-signature attachment: stored
Received on 2008-07-21 10:45:49 CEST

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.