You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Harold Mills <ha...@novaspeech.com> on 2007/06/19 14:07:43 UTC

unexpected author property behavior

We are serving SVN locally via Apache under Windows XP. The Location
directive we have in our httpd.conf file is:

 

<Location /svn>
   DAV svn
   SVNParentPath C:/Svn
</Location>

 

which permits anonymous access to our repositories. I thought I understood
that in such a situation SVN will not issue an authentication challenge when
changes are committed to a repository, so that it will not know who is
performing the commit and will set the author property to "(no author)" on
the corresponding revision. However, while in our case SVN does not seem to
be issuing authentication challenges, for some users accessing some
repositories the author property still gets set to their Windows user name.
However, this does not happen for all users, or for a given user on all
repositories. When it doesn't happen, the author property is set to "(no
author)" as expected. Can anybody tell me how SVN is getting these user
names, and how I can make it happen consistently across both users and
repositories? I would prefer this to configuring HTTP authentication if it's
simpler, which it seems it might be.

 

Thanks,

 

    Harold Mills

 

 

 


Re: unexpected author property behavior

Posted by Ryan Schmidt <su...@ryandesign.com>.
On Jun 19, 2007, at 09:07, Harold Mills wrote:

> We are serving SVN locally via Apache under Windows XP. The  
> Location directive we have in our httpd.conf file is:
>
>
>
> <Location /svn>
>    DAV svn
>    SVNParentPath C:/Svn
> </Location>
>
>
>
> which permits anonymous access to our repositories. I thought I  
> understood that in such a situation SVN will not issue an  
> authentication challenge when changes are committed to a  
> repository, so that it will not know who is performing the commit  
> and will set the author property to “(no author)” on the  
> corresponding revision. However, while in our case SVN does not  
> seem to be issuing authentication challenges, for some users  
> accessing some repositories the author property still gets set to  
> their Windows user name. However, this does not happen for all  
> users, or for a given user on all repositories. When it doesn’t  
> happen, the author property is set to “(no author)” as expected.  
> Can anybody tell me how SVN is getting these user names, and how I  
> can make it happen consistently across both users and repositories?  
> I would prefer this to configuring HTTP authentication if it’s  
> simpler, which it seems it might be.


Maybe you had the repository set up with authentication before, and  
during that time, some users accessed the repository, and entered  
their usernames and passwords, which were then cached in the  
directory ~/.subversion/auth (or wherever the equivalent directory is  
on Windows)? If so, you could remove those files from the auth  
directory on those clients.


---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
For additional commands, e-mail: users-help@subversion.tigris.org