[Issue 1020] New - Username and password not cached and not prompted for

View: New views
3 Messages — Rating Filter:   Alert me  

[Issue 1020] New - Username and password not cached and not prompted for

by Jim Showalter-4 :: Rate this Message:

Reply (Restricted by the Administrator) | Reply to Author | View Threaded | Show Only this Message

http://subclipse.tigris.org/issues/show_bug.cgi?id=1020
                 Issue #|1020
                 Summary|Username and password not cached and not prompted for
               Component|subclipse
                 Version|current
                Platform|JavaHL
              OS/Version|Windows XP
                     URL|
                  Status|NEW
       Status whiteboard|
                Keywords|
              Resolution|
              Issue type|DEFECT
                Priority|P3
            Subcomponent|core
             Assigned to|issues@subclipse
             Reported by|jimshowalter






------- Additional comments from jimshowalter@... Sun Oct 25 13:43:34 -0700 2009 -------
The FAQ says that usernames and passwords are cached once and then not prompted
for, and to be re-prompted requires deleting the cached info
(http://subclipse.tigris.org/wiki/PluginFAQ#head-d507c29676491f4419997a76735feb6ef0aa8cf8).

But I just installed Subversion and Subclipse for the very first time, created a
repository, tried to create a remote folder in Eclipse, and got the mkdir -m ""
svn://localhost Authorization failed error. I was never prompted for username or
password.

This supposedly indicates inadequate cached credentials. But I have no cached
credentials--this is an install of SVN for the very first time. No Eclipse
keyring, nothing but empty directories in %APPDATA%\Subversion​\auth, etc.

All of the responses online such as
http://subclipse.tigris.org/ds/viewMessage.do?dsForumId=1047&dsMessageId=860995
refer to cached credentials, which I don't have, so none of the responses online
are helpful.

Is there some other location in which I should be looking for cached credentials?

------------------------------------------------------
http://subclipse.tigris.org/ds/viewMessage.do?dsForumId=1046&dsMessageId=2411220

To unsubscribe from this discussion, e-mail: [issues-unsubscribe@...].

[Issue 1020] Username and password not cached and not prompted for

by Mark Phippard-3 :: Rate this Message:

Reply (Restricted by the Administrator) | Reply to Author | View Threaded | Show Only this Message

http://subclipse.tigris.org/issues/show_bug.cgi?id=1020






------- Additional comments from markphip@... Mon Oct 26 07:51:17 -0700 2009 -------
Subversion works via a challenge-based auth system. So you cannot push the credentials and have them
used.  Basically, the server decides if it needs credentials and then challenges the client.  The client in turn
calls a callback function to get the credentials.  Our role in this equation is simply to provide the
implementation of the callback function.

I think your problem is that you have not edited the svnserve.conf file on your repository to setup the auth
rules and usernames/passwords.  The behavior you describes matches the default for a new repository
before this has been done.

------------------------------------------------------
http://subclipse.tigris.org/ds/viewMessage.do?dsForumId=1046&dsMessageId=2411403

To unsubscribe from this discussion, e-mail: [issues-unsubscribe@...].

[Issue 1020] Username and password not cached and not prompted for

by Jim Showalter-4 :: Rate this Message:

Reply (Restricted by the Administrator) | Reply to Author | View Threaded | Show Only this Message

http://subclipse.tigris.org/issues/show_bug.cgi?id=1020






------- Additional comments from jimshowalter@... Fri Nov  6 14:50:05 -0800 2009 -------
Yes, that was the problem. I had edited the passwd file to add users and
passwords, but had not enabled password-db in the svnserv file. Please close this.

------------------------------------------------------
http://subclipse.tigris.org/ds/viewMessage.do?dsForumId=1046&dsMessageId=2415286

To unsubscribe from this discussion, e-mail: [issues-unsubscribe@...].