I'm a Systems Admin supporting a team of developers, and our subversion repository is protected by HTTP basic authentication tied to a single-signon solution. We also share our infrastructure with some other teams and subs. The developers want an account they can use to automatically write to the SVN (e.g. automatically checkin some generated scripts, or automatically publish entire releases to a directory), either by storing the account password within the script or using SSH for passwordless login.
A colleague of mine over in IT thinks that this would be a very bad idea, and I'm inclined to agree, there seems to be a very high security risk both from malicious intent or just a badly written script gone haywire and wreaking havoc on the repository. However, more people and other teams and subs keep asking for it, and when I've tried to do some of my own research I haven't been able to find any supporting material to help me convince them, which makes me wonder if I'm wrong and it's not as bad as I think it is.
Am I right about the potential security threat these automated scripts pose to our repository? Are there any alternatives or protective measures that I'm missing? If not, can anyone point me in the direction of any supporting material out there that might help me get the point across?
[Edit] I forgot to mention we also use Jenkins for continuous integration: http://en.wikipedia.org/wiki/Jenkins_%28software%29