Managing users and passwords: Difference between revisions
No edit summary |
No edit summary |
||
| Line 1: | Line 1: | ||
Subclipse does not own the information about users and passwords, so there is no way for you to manage it from Subclipse itself. It is controlled via the client interface you have chosen in the preferences. JavaHL shares the same cache location as Subversion command line and other clients that use the Subversion libraries. On Windows this is located in %APPDATA%\Subversion. On *nix it is in ~/.subversion. | Subclipse does not own the information about users and passwords, so there is no way for you to manage it from Subclipse itself. It is controlled via the client interface you have chosen in the preferences. JavaHL shares the same cache location as Subversion command line and other clients that use the Subversion libraries. On Windows this is located in %APPDATA%\Subversion\auth\. On *nix it is in ~/.subversion/auth. | ||
The SVNKit stores users and passwords in the Eclipse keyring. It is named .keyring and is in the Eclipse configuration folder by default. | The SVNKit stores users and passwords in the Eclipse keyring. It is named .keyring and is in the Eclipse configuration folder by default. | ||
To delete cached password information you can delete the keyring file (in the SVNKit case) or the contents of the auth folder (in the JavaHL case). | To delete cached password information you can delete the keyring file (in the SVNKit case) or the contents of the auth folder (in the JavaHL case). | ||
In the case you delete the auth folder, instead of the files in it, you will stumble upon a Subversion bug in JavaHL, where it will not recreate the proper structure. So now it is not able to cache these values. If you have access to the SVN command line, just run a command and it will create the structure. Then you should be back to normal. | |||
Revision as of 10:59, 25 January 2007
Subclipse does not own the information about users and passwords, so there is no way for you to manage it from Subclipse itself. It is controlled via the client interface you have chosen in the preferences. JavaHL shares the same cache location as Subversion command line and other clients that use the Subversion libraries. On Windows this is located in %APPDATA%\Subversion\auth\. On *nix it is in ~/.subversion/auth.
The SVNKit stores users and passwords in the Eclipse keyring. It is named .keyring and is in the Eclipse configuration folder by default.
To delete cached password information you can delete the keyring file (in the SVNKit case) or the contents of the auth folder (in the JavaHL case).
In the case you delete the auth folder, instead of the files in it, you will stumble upon a Subversion bug in JavaHL, where it will not recreate the proper structure. So now it is not able to cache these values. If you have access to the SVN command line, just run a command and it will create the structure. Then you should be back to normal.