Client credentials caching (HTTPS)

J S Green
Posts: 31
Joined: Wed Apr 12, 2006 12:28 am
Location: UK

Client credentials caching (HTTPS)

Postby J S Green » Mon May 22, 2006 5:46 pm

I am using Windows XP but the principles should apply to any operating system.

When using https (or svn+ssh) protocols, Subversion caches client credentials in [%APPDATA%\Subversion\auth\svn.*] where %APPDATA% is, for example, [Documents and Settings\Me\Application Data]. If there are no credentials cached there, and you run, for example, 'svn list' on the command line, you get a prompt:

Error validating server certificate for '':
- The certificate is not issued by a trusted authority. Use the fingerprint to validate the certificate manually!
Certificate information:
- Hostname:
- Valid: from xxx until xxx
- Issuer: xxx, xxx, xxx, xxx, xxx
- Fingerprint: xxx
(R)eject, accept (t)emporarily or accept (p)ermanently?

If you select (p), a new encrypted file is written into the appropriate cache, for example, %APPDATA%\...\auth\svn.ssl.server.

If you use Subversive only, this caching is not done. That means that every time you restart Eclipse, you get asked to accept the certificate. (In earlier releases, this used to happen several times per session but 1.0.0.RC1 remembers throughout the session).

Is it possible for Subversive to cache the credentials as well? It would probably mean offering an extra button on the dialog and using Subversion to do the caching. This would simplify the setup process for new users.

Posts: 473
Joined: Tue Jan 03, 2006 11:57 am
Location: Kharkiv, Ukraine

Postby ivinnykov » Thu May 25, 2006 2:01 pm

Dear John,

Thank you for the valuable note. It makes sense to have this feature, so we requested support in JavaSVN from Alexander Kitaev (JavaSVN author). Please see task SBV-1887 - Allow caching of SSL certificates ... e-SBV-1887
Best regards,
Igor Vinnykov
Polarion Team

Return to “Polarion Subversive - Eclipse Client for SVN”

Who is online

Users browsing this forum: No registered users and 4 guests