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 'https://www.xxx.com/443':
- The certificate is not issued by a trusted authority. Use the fingerprint to validate the certificate manually!
- Hostname: www.xxx.com
- 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.