On 06.02.2017 16:42, Karl Fogel wrote:
> (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).
That's certainly possible to do. Not as easy as it sounds, but
> Even though authorization comes later than authentication, TortoisSVN can still remember things and link them together when it's appropriate to do so.
> 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.
I've opened a ticket for this:
oo // \\ "De Chelonian Mobile"
(_,\/ \_/ \ TortoiseSVN
\ \_/_\_/> The coolest interface to (Sub)version control
/_/ \_\ http://tortoisesvn.net
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
Received on 2017-02-06 21:15:23 CET