Our Subversion repository is hosted by Atlassian OnDemand. Currently, we use usernames and passwords to check out and commit code. I would like to utilize an alternate authentication method, as I am setting up a Jenkins server that needs to check out the code periodically. I don't want to store a username and password in a plain text file on the Jenkins server because that's not a secure practice. I understand SSH public/private keys are not supported but are SSL certificates supported? How can I set up the Subversion repository to allow code checkouts without a username/password combination?
I'm afraid this is not possible in OnDemand. There's no way to modify the internal SVN repository to use SSH+SVN instead of the basic user authentication.
It already uses SSL by default, but you would to add an internal user and password to access it through Jenkins.
It's officially Tuesday, which means it's officially time for another tip to help you better navigate this space we call the Atlassian Community. 😄 I got a great question from community member, Sa...
Connect with like-minded Atlassian users at free events near you!Find a group
Connect with like-minded Atlassian users at free events near you!
Unfortunately there are no AUG chapters near you at the moment.Start an AUG