Eclipse, Subclipse 1.8.2, SVN 1.7.0 asks password every action

Question

After I installed new Eclipse Indigo, it asks me for password every action I do in SVN Repository perspective (e.g. browse through every single

Answer 1

for svn+ssh create system variable: SVN_SSH

and set it like this:

C:\\Program Files\\TortoiseSVN\\bin\\TortoisePlink.exe" -l user -pw password

Answer 2

My observation (with Subclipse 1.6.13 and JavaHL 1.6.12 on Eclipse 3.7.1) is that Subclipse (even with the JavaHL connector) is able to cache the credentials if you create the repository connection in the "SVN Repositories" view.

When you create the the repository connection in the "Checkout projects from SVN" import wizard, the credentials will not get saved. In this case, they won't even get saved when recreating it in the "SVN Repositories" view until the next restart of Eclipse.

You can see if any credentials are saved by looking at the contents of the following folder: C:\Users\\AppData\Roaming\Subversion (on Windows 7). When any credentials are stored, an "auth" subdirectory exists in this directory.

Answer 3

When first time I am facing the same problem I change my windows password and that worked. Actually, in my company, we have the policy to change the password after every 3 months and my password was expired, so I was facing the problem.

The second time I just Restarted the eclipse that works for me.

Answer 4

If anybody has the same problem with Kepler and Subversive (on Ubuntu), I was able to solve it by checking 'UI Prompt' in General -> Security -> Security Storage -> [Password]

Answer 5

For some reason, I had both SVNKit and JavaHL installed. I needed to update my Eclipse preferences to use SVNKit instead of JavaHL.

In Preferences > Team > SVN > SVN Interface
switch:
JavaHL (JNI) ...
to:
SVNKit (Pure Java) SVNKit ....

Answer 6

The once per session caching is a feature that SVNKit provides. JavaHL does not provide this. It sounds like you do not allow SVN to cache your credentials or you are using svn+ssh:// in which case SVN cannot cache your credentials. If it is the latter, you can store your SSH key on the server to avoid logging in and run ssh-agent on your client to provide the certificate to the SSH client.