Auth problem with automated build - svnant auth cache and http/ldap

How do you normally solve the problem with authentication and automated builds?

I require basic http authentication via ldap with my svn repository
and I want that auth cached so my automated builds can do their
checkouts and imports (we presently store built artifacts in a
disribution repository). Oh, and my builds are distributed across
many flavors of linux and windows with repository access happening at
the beginning, middle and end of the build.

My repositories use basic ldap auth. The native client caches its
creds and gives a user experience similar to cvs and this is good. The
java svntask does not and checkouts mid build fail due to "auth
cancelled.". Finally, I'd like to use a pure java solution because
some of my unix boxes cannot be update with newer libraries to support
the svn client.

I could use environment variables or hard code username/password into
my ant scripts but is is bad for two reasons;
- insecure. I usually produce a debug level log with the build and all
environment variable are captured
- private builds by users would force them to put their password into
an env variable.

I gather I can use a public / private key with SSH but I don't
presently use SSH for repository access and the key would mean that my
users need to configure their systems like the build system with their
own key.

What solution are normally used for this problem? Is there a way to
force the javahl svnant tasks to use the credentials in the home dir
or some other key? Is there a way to push the problem up by using
auth other than basic ldap (ldap with a key?)

Thanks for the help.

-- 
Peter Kahn
citizenkahn_at_gmail.com
pkahnpie1_at_AIM
http://citizenkahn.myplaxo.com
Awareness - Intention - Action
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe_at_subversion.tigris.org
For additional commands, e-mail: users-help_at_subversion.tigris.org