How and where does Fisheye keep Subversion user name and password? It is not preferred that one user logs in to Subversion and access code base in case user name and password are revealed.
How does Fisheye deal with security issues in general?
FishEye stores repository configuration information, such as username and password, in <FishEye_Home_Directory>/config.xml. This is a sample SVN configuration found in config.xml:
<repository name="SVN" description="This is a sample SVN repo" store-diff="true" enabled="true"> <svn url="file:///C:/Repositories/SVN" path="" follow-base="false" initial-import="none"> <symbolic auto-rules="true"/> <auth username="the_repo_user_name" password="the_repo_user_pwd"/> </svn> <linker/> <security use-defaults="true" allow-anon="false" allow-logged-in="false" allow-anon-write="false" allow-logged-in-write="false"> <required-groups/> <required-write-groups/> </security> </repository>
Our goal is to make this file super secure. Even if someone reaches the machine that this file is kept in, s/he won't be able to read the user name/password.
We are intending to use Crowd in near future. Can Crowd be a solution for this, in general what are our options to hide user name and password information ?
Atlassian Summit is an excellent opportunity for in-person support, training, and networking.Learn more
...there's anything I've learnt from working, it's that people are lazy! No offense to anyone reading this, but it's true and we can all admit it. The easier you make something for someone, the more...
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
You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs