SVN credentials not remembered for session any more

[andyg1001]

I have just upgraded Subclipse to the current latest version, but I am also using the JavaHL 1.10 libraries.

Previously Subclipse would remember my SVN login details while Eclipse was running, asking me only the first time for my login details after starting up Eclipse for each SVN repository that I accessed.

I do not wish to save my login details.

However, following the Subclipse upgrade, it now does not remember my login details for the session, but asks me every single time I perform an operation using SVN.

Please can the old behaviour be reinstated.

[markphip]

I cannot think of any changes in Subclipse (ever) that would be responsible or related. What version did you upgrade from? We have not done any major changes in about 10 years and we have not done anything with credentials since the pre-1.0 days which was maybe 18 years ago.

We rely on the Subversion library (JavaHL or SVNKit) to manage the credentials. We supply a callback API that the library uses whenever it wants you to ask for credentials. Any caching of the credentials is handled in the library and the decision to ask for the credentials is asked for by the library.

Are you sure you did not switch between SVNKit and JavaHL at some point? Maybe the behavior of the libraries is different in some way.

[caroso-de]

I recently noticed that there were changes to the secure storage where eclipse stores its credentials somewhere around Eclipse 2019.
Did you just update subclipse or did you also update Eclipse?

[markphip]

Subclipse does not store credentials, so the Eclipse secure storage probably does not matter.

The JavaHL library stores credentials the same way as the svn command line client .. meaning they are stored according to the configuration in ~/.subversion . SVNKit is kind of a mixed bag. I think it will use the native Subversion store for compatibility but it may also use the Eclipse storage if nothing is already cached in the SVN area.

On systems where Subversion does not have a secure password store available (Linux) I believe SVN stopped caching passwords, but I believe it will use any that have already been cached.

[jmduke239]

I too am having credential rememberence issues; however, unlike the original author, I've asked for it to save the credentials. Multiple SVN requests within the same session of eclipse work fine and I'm not prompted. I am prompted if I switch workspaces (same repository), do a restart to keep the same workspace, or shutdown eclipse and relaunch. My id is saved but my password isn't. This seems to have started once eclipse updated itself to 2021-06 (4.20.0). I use SVNKit (Pure Java) v1.10.1.10777 along with Subclipse 4.3.0.201901172050. The 'auth' folder appears to be in ~/.subversion with my ID and some encoded text.

[markphip]

The previous answers all stand ... Subclipse is not involved in the process of caching or not caching passwords. It is handled by the API provider.

I would expect, if using SVNKit, that it would cache the passwords but I do not know if it looks at your ~/.subversion/config and servers files at all to make the decision. I also seem to recall that unless you have already cached your password in the auth area it will use the Eclipse secure password storage to cache the password. This is just going off old memories at this point.