# svn login credentials

**URL:** <https://forum.ansible.com/t/svn-login-credentials/12023>\
**Category:** Ansible Project\
**Tags:** ansible-project\
**Created:** [October 24, 2012, 11:59am UTC](https://forum.ansible.com/t/svn-login-credentials/12023 "2012-10-24T11:59:04Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Michael\_DeHaan](https://avatars.discourse-cdn.com/v4/letter/m/c4cdca/32.png) [@Michael\_DeHaan](https://forum.ansible.com/u/Michael_DeHaan)\
**Post date:** [October 24, 2012, 11:59am UTC](https://forum.ansible.com/t/svn-login-credentials/12023/1 "2012-10-24T11:59:04Z")

</div>

Looks like it currently can't do it, but from the example supports SSH  
keys. Unencrypted keys should be ok. If your key is encrypted, it  
probably doesn't work that well. Can you enable public read-only  
access?

---

<div class="post-metadata">

**Author:** ![James\_Reece](https://avatars.discourse-cdn.com/v4/letter/j/8edcca/32.png) [@James\_Reece](https://forum.ansible.com/u/James_Reece)\
**Post date:** [October 25, 2012, 3:23am UTC](https://forum.ansible.com/t/svn-login-credentials/12023/2 "2012-10-25T03:23:12Z")

</div>

This reply kicked off a decent conversation with my pal in the infrastructure team and it sounds like this cat can be skinned a number of ways.

Many thanks

---

<div class="post-metadata">

**Author:** ![James8](https://avatars.discourse-cdn.com/v4/letter/j/ec9cab/32.png) [@James8](https://forum.ansible.com/u/James8)\
**Post date:** [December 27, 2012, 8:17pm UTC](https://forum.ansible.com/t/svn-login-credentials/12023/3 "2012-12-27T20:17:37Z")

</div>

James,  
What approach did you take to solve this problem?

Thanks,  
James