I am controlling a Subversion client via a shell script executed from an
First, Apache generates a local folder for every subversion session for
I have to check out different revisions by different subversion users in
different folders on my local machine (svn server is accessed via http).
Then, Apache starts the script that checks some sourcecode out into the
This works fine and if I add --config-dir= (without giving a folder
name) subversion creates the necessary metadata "auth" in every session
folder itself so I hope that the different revisions checked out by
different users don't get mixed.
If the script issues the svn parameters --username foo --password bar
everything would work fine as far as I see.
However, I'd like to avoid to send the unencrypted password everytime a
svn session is opened. Therefore, I'd like to use the permanent password
storage function of svn if possible:
I imagine that I could issue svn checkout manually for every user once
so their passwords would get stored permanently somewhere on the machine
- so the next time my bash script containing the svn command is called
from the webserver (without giving a password) I imagine that svn should
remember that this user has been authenticated already and just do the job.
Is this possible and how? The webserver user which calls the script is
Maybe the conflict is here:
If I use always the same global config file for all users and sessions,
the sessions would get probably mixed up but subversion would probably
store the passwords of all users as desired.
As every session has now their individual config dir the sessions dont
get mixed up but I have to provide username AND password each time I
check something out...
Is there a way to solve this?
Thanks in advance
Received on 2012-05-11 12:12:04 CEST