[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: Re: Offer re-prompt to change user authn after failed commit?

From: Karl Fogel <kfogel_at_red-bean.com>
Date: Mon, 6 Feb 2017 07:42:51 -0800 (PST)

(Replying to Stefan here, but thanks also to Philipp Mott for his reply, which said basically the same thing.)

On 2017-02-03, Stefan Küng wrote:
> Sorry, there's not re-prompt feature implemented.
> Subversion only asks for authentication (username/password) if
> necessary. Since auth data is already stored locally, it uses that data
> to authenticate. But the authentication succeeds! So it doesn't ask the
> user for authentication anymore.
> The problem is that the authorization later fails, which comes much
> later than the authentication.

Thank you. Yes, I understand the problem. But TortoiseSVN could still re-prompt, using this recipe:

  1) Perform default authentication
  2) Attempt the authz-requiring operation (e.g., commit)
  3) If (2) fails, look at the exact error, and...
  4) ...if it's an authz error, prompt again for new authn
     credentials and continue as if from (1).

Even though authorization comes later than authentication, TortoisSVN can still remember things and link them together when it's appropriate to do so.

> There's a workaround though:
> in the settings dialog, Sync page you can export all settings to a file.
> If you check the box "sync stored auth data", then that export file will
> contain also all the stored auth data. You can then delete the stored
> auth data, do your commit and then import the exported file again.

Ah, I didn't know about that, and it helps as a workaround. But there is a chance for TortoiseSVN to offer an even friendlier user experience here, I think, as described above.

> Also: settings dialog->saved data
> There's not just a "Clear" button next to "Authentication data" but also
> a "Clear..." button. If you click the "Clear..." button you'll get a
> dialog showing you all the stored auth data, and there you can select
> just the one stored data to delete.
> Maybe that's the easiest way.

Also useful as a workaround.

> (note: just in case you forgot your password(s): on that dialog you can
> Ctrl+Shift+DoubleClick to have it show you the passwords in clear).

Even better, thank you.

> Hope that helps a little bit.

It definitely helps to have these workarounds. But if you think the above proposed new behavior is a good idea, could we file an enhancement ticket in the tracker? I realize maybe no one has time to implement it right now (and I have zero Windows development chops, unfortunately), but at least having the ticket filed provides a starting point, and would give people something to refer to.

Best regards,

> On 03.02.2017 19:53, Karl Fogel wrote:
>> In TortoiseSVN 1.9.5, on a Windows 10 box [1], I needed to do a
>> commit from an existing working copy, but on that machine, Tortoise
>> only had cached authentication credentials for a read-only user for
>> the repository in question.
>> "No problem," I thought, "It'll just fail the first commit attempt,
>> because it will default first to the cached user creds, but then it
>> will prompt me for a new username / password pair, the way the
>> command-line client would, and let me commit with those."
>> That's not what happened. I right-clicked on the file and chose
>> "TortoiseSVN Commit", and as expected the initial commit attempt
>> failed... but that was it. There was no re-prompt interface at
>> which I could enter a different username and password. The only
>> client-side solution would have been to wipe out all the cached
>> authentication credentials, which of course I didn't want to do (I
>> didn't want to lose the creds for the read-only user, I just wanted
>> to do this commit as another user.) The solution I actually used
>> was to temporarily enable read-write for the original user on the
>> repository side, commit, and then use propset to change the
>> "svn:author" revprop. But that's obviously not ideal, and would
>> have been impossible if I didn't have admin access to the
>> repository.
>> Is there a re-prompt feature in TortoiseSVN and I just didn't
>> manage to find it? Or if not, would this be a desirable feature to
>> have? (I looked in the ChangeLog, the users@ archive, and in the
>> bug tracker, and did not see any discussion of this enhancement.)


To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2017-02-06 16:43:03 CET

This is an archived mail posted to the TortoiseSVN Users mailing list.