On Tue, Mar 22, 2011 at 3:38 AM, Noel Grandin <noel_at_peralex.com> wrote:
> This is a long standing issue with subclipse.
Your information below is all incorrect.
> The issue is that subclipse will not ask you for a username/password if the
> anonymous account has default read-access.
No Subversion client will. It is impossible to provide Subversion
with credentials if the server is anonymous read access. The
Subversion client never pushes credentials to the server, it only
responds to challenges from the server and the server does not send
the challenge when read is anonymous. For example this works fine:
svn co --username bogus --password bogus
http://svn.apache.org/repos/asf/subversion/trunk/notes/svnpatch
> This means that it is not possible to checkout a repository under your own
> username, which in turn means that it is not possible to commit.
Besides being incorrect for the previous reason, this would also be
incorrect if the repository requires username and password.
Subversion does not store anything about the user that checked out the
working copy. Go ahead and try it. Zip up a working copy and give it
to a colleague. They can unzip it and use it fine. In a shared
environment you can even both work in the same working copy.
> The only solution (that I know of) is to checkout use the command-line
> subversion client, and then create a project in eclipse using that
> directory, at which point subclipse will pick up the correct credentials.
The only real issue is that Subversion does not provide any API's or
user interface to work with its credentials cache. So you cannot ask
it to delete the credentials for a certain site. This is mainly an
issue if you do something like access a site as one user and then want
to switch to some other user. Subclipse used to ask you to store the
username and pasword in Eclipse but this made things way worse than
they are today. When things would happen like your password needing
to be changed you lose the ability to be prompted to change it and
since the cache is shared amongst all Subversion clients you lose the
ability to have those changes automatically reflect in all clients.
If the server disables accounts for invalid passwords it was also a
common problem that this would happen because there is no error or
prompt given when the credentials are being suppiled to the API
instead of being handled via the callback.
I wish there was an API to delete credentials so that we could provide
UI to do this, but there isn't. So you have to delete them manually
today. In an environment where you only have one user account this
should never be a real problem.
--
Thanks
Mark Phippard
http://markphip.blogspot.com/
------------------------------------------------------
http://subclipse.tigris.org/ds/viewMessage.do?dsForumId=1047&dsMessageId=2713141
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_subclipse.tigris.org].
Received on 2011-03-22 12:44:19 CET