You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by shannon carey <re...@gmail.com> on 2008/07/15 02:23:18 UTC
Only one username per realm stored in cached credentials
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 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?
Thanks!
-Shannon Carey
Re: Only one username per realm stored in cached credentials
Posted by shannon carey <re...@gmail.com>.
I see.
No, both tasks are being from a single Windows user (and a single Linux
user, for that matter). The SVN user name is specified on the command
line. I don't remember the details, but I tried running it under a
"service" user but had problems due to the fact that Vista's ability to
control user permissions are nerfed compared to XP Pro (no poledit, for
example). I guess the solution is to run it under two different users.
-Shannon
On Mon, Jul 21, 2008 at 3:45 AM, Stefan Sperling <st...@elego.de> wrote:
> 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 <re...@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
> other.
>
> > 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?
>
> Stefan
>
Re: Only one username per realm stored in cached credentials
Posted by Stefan Sperling <st...@elego.de>.
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 <re...@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
other.
> 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?
Stefan
Re: Only one username per realm stored in cached credentials
Posted by shannon carey <re...@gmail.com>.
*bump*
On Mon, Jul 14, 2008 at 9:23 PM, shannon carey <re...@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 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?
>
> Thanks!
>
> -Shannon Carey
>