authenticating with different SVN credentials to the same svn authentication realm

[Jorg Heymans-4]

Hi,

My problem is summarized in this post from 2007 [1]. Basically our svn
infra consists of using one svn repository per project. The repos all
run on the same server, so we have a bunch of urls like
http://oursvnserver/svn/projectA, http://oursvnserver/svn/projectB,
http://oursvnserver/svn/projectC etc. The problem seems to be how
Hudson stores scm credentials in a Map<String,Credential> which is
keyed on authentication realm (SubversionSCM.java line 1262), so that
credentials gets overwritten by another user that happens to
authenticate to the same realm.

Other than using a common 'ci' svn account for all projects, is there
a workaround for this ?

Thanks
Jorg

[1] http://www.nabble.com/followup%3A-subversion-credentials-td13783576.html#a13783576

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

[Michael Donohue]

There was a similar thread just this month:

http://www.nabble.com/Just-one-credential-per-SVN-Realm---tt25799488.html

-Michael
[phone]

On Tue, Oct 27, 2009 at 11:00 AM, Jorg Heymans <[hidden email]> wrote:

Hi,

My problem is summarized in this post from 2007 [1]. Basically our svn
infra consists of using one svn repository per project. The repos all
run on the same server, so we have a bunch of urls like
http://oursvnserver/svn/projectA, http://oursvnserver/svn/projectB,
http://oursvnserver/svn/projectC etc. The problem seems to be how
Hudson stores scm credentials in a Map<String,Credential> which is
keyed on authentication realm (SubversionSCM.java line 1262), so that
credentials gets overwritten by another user that happens to
authenticate to the same realm.

Other than using a common 'ci' svn account for all projects, is there
a workaround for this ?

Thanks
Jorg

[1] http://www.nabble.com/followup%3A-subversion-credentials-td13783576.html#a13783576

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

[Jorg Heymans-4]

On Tue, Oct 27, 2009 at 4:04 PM, Michael Donohue
<[hidden email]> wrote:
> There was a similar thread just this month:
> http://www.nabble.com/Just-one-credential-per-SVN-Realm---tt25799488.html

thanks for the pointer, i'll track the issue then.

Jorg

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]

[Thierry Carre]

The key used by Hudson in its Map is made (in my context) of the SVN host and a String after a ";". This String come from the value of the "AuthName" Apache parameter, inside <Location>.

This string was the same for each projet (auto-generated by our process that create new projects in svn), so we had the same problem like you. We modified our svn configuration (or more specifically Apache configuration) to have something like this for each project :

<Location /svn/ProjectA>
 ...
 AuthName "SVN Referential for ProjectA"
 ...
</Location>
<Location /svn/ProjectB>
 ...
 AuthName "SVN Referential for ProjectB"
 ...
</Location>
etc.

From now, we can have one credential per project on the same SVN server because each Hudson key is different.
I hope this will be helpful in youir case.

Jorg Heymans-3 wrote

On Tue, Oct 27, 2009 at 4:04 PM, Michael Donohue
<[e-mail]> wrote:
> There was a similar thread just this month:
> http://www.nabble.com/Just-one-credential-per-SVN-Realm---tt25799488.html

thanks for the pointer, i'll track the issue then.

Jorg

---------------------------------------------------------------------
To unsubscribe, e-mail: [e-mail]
For additional commands, e-mail: [e-mail]

[Jorg Heymans-4]

On Wed, Oct 28, 2009 at 9:37 AM, Thierry Carre <[hidden email]> wrote:

>
> The key used by Hudson in its Map is made (in my context) of the SVN host and
> a String after a ";". This String come from the value of the "AuthName"
> Apache parameter, inside <Location>.
>
> This string was the same for each projet (auto-generated by our process that
> create new projects in svn), so we had the same problem like you. We
> modified our svn configuration (or more specifically Apache configuration)
> to have something like this for each project :
>
> <Location /svn/ProjectA>
>  ...
>  AuthName "SVN Referential for ProjectA"
>  ...
> </Location>
> <Location /svn/ProjectB>
>  ...
>  AuthName "SVN Referential for ProjectB"
>  ...
> </Location>
> etc.
>
> From now, we can have one credential per project on the same SVN server
> because each Hudson key is different.
> I hope this will be helpful in youir case.

Thanks, that probably would've worked as well for my case. For now i
settled on using one read-only account for all projects instead.

Jorg

---------------------------------------------------------------------
To unsubscribe, e-mail: [hidden email]
For additional commands, e-mail: [hidden email]