You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@subversion.apache.org by Felix Ritter <ri...@mevis.de> on 2006/09/25 16:31:35 UTC

MacOS: SVN keychain and automated tasks

Hi Mac users,

the new keychain support in subversion 1.4 is giving me a hard time.  
I've some automated builds using svn that are started via cron deamon  
(Mac OS 10.4.7). Since the cron jobs runs as a user who never  
actually unlocked the keychain tool (e.g. by login into a MacOS  
desktop session), the svn checkout or update stops with prompting the  
user for a keyword to unlock the keychain (the repository is accessed  
via https). Thus the whole build process hangs. Any advice on how to  
use svn on MacOS in automated processes like this would be greatly  
appreciated.

	Cheers,

	Felix

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

Re: MacOS: SVN keychain and automated tasks

Posted by Christian Schaffner <ch...@users.sourceforge.net>.
On 16.10.2006, at 17:22, Christopher Elkins wrote:

> On Oct 16, 2006, at 2:55 PM, Christian Schaffner wrote:
>
>>> On 25.09.2006, at 11:31, Felix Ritter wrote:
>>>
>>>> Hi Mac users,
>>>>
>>>> the new keychain support in subversion 1.4 is giving me a hard  
>>>> time. I've some automated builds using svn that are started via  
>>>> cron deamon (Mac OS 10.4.7). Since the cron jobs runs as a user  
>>>> who never actually unlocked the keychain tool (e.g. by login  
>>>> into a MacOS desktop session), the svn checkout or update stops  
>>>> with prompting the user for a keyword to unlock the keychain  
>>>> (the repository is accessed via https). Thus the whole build  
>>>> process hangs. Any advice on how to use svn on MacOS in  
>>>> automated processes like this would be greatly appreciated.
>>>>
>>>> 	Cheers,
>>>>
>>>> 	Felix
>>
>> I am the author of the Fink svn packages, which I updated to svn  
>> 1.4.0 recently. I am having exactly the same problem, since we run  
>> an automated script that updates our internal test web site every  
>> time we check something into svn. The user of the script is 'www'  
>> which doesn't have a keychain. Did you find a solution to that  
>> problem? Anybody else?
>
> One workaround, although somewhat inconvenient, is to use a 1.3  
> client to authenticate for the first time (thereby caching the  
> credentials in plain-text) and then use a 1.4 client for further  
> access (which will use the cached credentials as-is).

Reading through the commit logs and mailing lists (there doesn't seem  
to be too much documentation about this feature) it looks like adding  
'--non-interactive' to svn commands should disable user interaction  
with keychain too.

Read about the keychain API at:
http://developer.apple.com/documentation/Security/Reference/ 
keychainservices/Reference/reference.html#//apple_ref/c/func/ 
SecKeychainSetUserInteractionAllowed

Did you try that? (I can't try right now...)

Christian.

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

Re: MacOS: SVN keychain and automated tasks

Posted by Christopher Elkins <ch...@gmail.com>.
On Oct 16, 2006, at 2:55 PM, Christian Schaffner wrote:

>> On 25.09.2006, at 11:31, Felix Ritter wrote:
>>
>>> Hi Mac users,
>>>
>>> the new keychain support in subversion 1.4 is giving me a hard  
>>> time. I've some automated builds using svn that are started via  
>>> cron deamon (Mac OS 10.4.7). Since the cron jobs runs as a user  
>>> who never actually unlocked the keychain tool (e.g. by login into  
>>> a MacOS desktop session), the svn checkout or update stops with  
>>> prompting the user for a keyword to unlock the keychain (the  
>>> repository is accessed via https). Thus the whole build process  
>>> hangs. Any advice on how to use svn on MacOS in automated  
>>> processes like this would be greatly appreciated.
>>>
>>> 	Cheers,
>>>
>>> 	Felix
>
> I am the author of the Fink svn packages, which I updated to svn  
> 1.4.0 recently. I am having exactly the same problem, since we run  
> an automated script that updates our internal test web site every  
> time we check something into svn. The user of the script is 'www'  
> which doesn't have a keychain. Did you find a solution to that  
> problem? Anybody else?

One workaround, although somewhat inconvenient, is to use a 1.3  
client to authenticate for the first time (thereby caching the  
credentials in plain-text) and then use a 1.4 client for further  
access (which will use the cached credentials as-is).

-- 
Christopher Elkins



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

Re: MacOS: SVN keychain and automated tasks

Posted by Christian Schaffner <ch...@users.sourceforge.net>.
Hi Felix

I am the author of the Fink svn packages, which I updated to svn  
1.4.0 recently. I am having exactly the same problem, since we run an  
automated script that updates our internal test web site every time  
we check something into svn. The user of the script is 'www' which  
doesn't have a keychain. Did you find a solution to that problem?  
Anybody else?

Thanks, Christian.

On 25.09.2006, at 11:31, Felix Ritter wrote:

> Hi Mac users,
>
> the new keychain support in subversion 1.4 is giving me a hard  
> time. I've some automated builds using svn that are started via  
> cron deamon (Mac OS 10.4.7). Since the cron jobs runs as a user who  
> never actually unlocked the keychain tool (e.g. by login into a  
> MacOS desktop session), the svn checkout or update stops with  
> prompting the user for a keyword to unlock the keychain (the  
> repository is accessed via https). Thus the whole build process  
> hangs. Any advice on how to use svn on MacOS in automated processes  
> like this would be greatly appreciated.
>
> 	Cheers,
>
> 	Felix
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@subversion.tigris.org
> For additional commands, e-mail: users-help@subversion.tigris.org

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