AW: Re: Offer re-prompt to change user authn after failed commit?
From: Philipp Mott <Philipp.Mott_at_giffits.de>
Date: Mon, 6 Feb 2017 16:30:33 +0000
I can imagine logical / concept conflicts between TSVN and the underlying SVN. The auth cache is handled by SVN; TSVN just uses the SVN "API" (it's not a real API, but anyway, TSVN interfaces SVN). Rewriting SVN functionality could break with integration of the next SVN update.
There might be a solution using Autohotkey, but once you committed yourself to the dark side of hacking with AHK there hardly is a way back...
I never experimented with all the hooking features - Is there a way to call a hook upon unsuccessful authentication?
(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:
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
Sitz der Gesellschaft: Hamburg
Diese E-Mail und alle beigefügten Dateien sind vertraulich und nur für den Adressaten bestimmt.
This email is only intended for the addressee. The content of this email, including all attachments is confidential and includes privileged material.
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].
This is an archived mail posted to the TortoiseSVN Users mailing list.