Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 312771 - Prompting for users credentials every time I contact SVN server
Summary: Prompting for users credentials every time I contact SVN server
Status: RESOLVED DUPLICATE of bug 314490
Alias: None
Product: Subversive
Classification: Technology
Component: UI (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Igor Burilo CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-05-13 06:42 EDT by Ricardo Gladwell CLA
Modified: 2010-06-21 05:35 EDT (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Ricardo Gladwell CLA 2010-05-13 06:42:47 EDT
Build Identifier: 20100218-1602

Even though Subversive is successfully storing my user credentials, it still prompts me with a "User Credentials" dialog when contacting the SVN server.

This happens sometimes as many as 5 times in one operation. I have to click OK for each time, when it would be nicer if it just used my credentials silently each time.

Reproducible: Always
Comment 1 Igor Burilo CLA 2010-05-14 05:14:46 EDT
Please, check whether you specified credentials in repository location for some particular realm or for whole repository location: in SVN Repositories View for repository location call 'Location Properties' action and check 'Show Credentials For' combo box (it shows <Repository Location> and realms for which to store credentials), please be sure that you specified correct credentials for <Repository Location>; there may be the case that for  <Repository Location> you specified incorrect credentials but for some realm you specified corrected ones; also if you don't need realm you can freely delete it.
Comment 2 Ricardo Gladwell CLA 2010-05-14 05:25:10 EDT
Thanks, that seemed to do the trick.

But shouldn't subversive update the credentials for both realm and repository when they are changed or become out of sync?

Mine changed as part of of our security teams password expiry policy and this is when this issue started to occur. Perhaps this could be an issue for other users?
Comment 3 Igor Burilo CLA 2010-05-17 04:56:57 EDT
> But shouldn't subversive update the credentials for both realm and repository when they are changed or become out of sync?
There can be several realms with different credentials so it's not correct to mix credentials for repository and realm.

> Perhaps this could be an issue for other users?
I agree that it should be noted somewhere, e.g. in FAQ or in Prompt dialog.
Comment 4 Ricardo Gladwell CLA 2010-05-17 09:03:28 EDT
I'm not sure I understand the distinction between a repository and realm. The use case I'm thinking of is when a user's subversion password changes: modifying it during your next commit should propagate so that Subversive no longer uses that password for future submits against that project.

What I happened to me was that Subversive was trying the old password, and then for some reason prompting me to enter the new password.

This caused issues as my company's Security team sent me an angry email.
Comment 5 Igor Burilo CLA 2010-05-18 03:36:54 EDT
Ricardo, thanks, we'll think what we can do with it.
In order to be more precise here's what happened: when user's subversion password changed you got authentication prompt dialog where credentials were saved for realm but not for repository location; next times for connecting to svn there were used credentials from repository location (obsolete credentials) but not credentials from realm (correct, updated credentials).
Comment 6 Ricardo Gladwell CLA 2010-05-19 06:13:54 EDT
I have to admit, I'm still not entirelyclear on the distinction, but actually I *think* the reverse is true: I got authentication prompt dialog when my password changed and credentials were updated for repository location but not the realm; next times for connecting to svn there were used credentials from realm location (obsolete credentials) but not credentials from repository (correct, updated credentials).

Correcting the realm credentials seemed to fix the issue.

However, I cannot easily confirm/reproduce this for you without breaking my local project install and risking the wrath of my security team.
Comment 7 Mike Schrag CLA 2010-06-01 16:03:13 EDT
I'm also seeing this problem on Mac OS X. The first SVN session for each repository requires me to accept the saved credentials. I would expect that if i check to save my credentials that I would not ever see the authentication dialog again.
Comment 8 Igor Burilo CLA 2010-06-21 05:35:03 EDT
Problems described in this bug were fixed in bug 314490

*** This bug has been marked as a duplicate of bug 314490 ***