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

Re: TortoiseSVN with DoD CAC (Smart Card) configuration help

From: Stefan Küng <tortoisesvn_at_gmail.com>
Date: Tue, 26 Feb 2013 20:24:54 +0100

On 25.02.2013 22:39, Bogardus, Robert K Jr CTR DODHRA DMDC (US) wrote:
> Hi Stefan, It works perfectly! I've attached the test cases I've run
> and they all work just fine.
> Our repositories are readable by everyone, just some are
> write-restricted - this version works fine with that.
> A function to remove the cached index for the last connection is a
> great solution - we'll need that for sure.

I'm on it. Should be ready soon.

> Let me know if you need any other testing and when you've committed a
> version we can use.

Yes. First thanks for testing!
Now, in your test report you have this:
6) Checkout app2 (I have READ-ONLY permission)
- no cert requests
- Edited a file. Tried to commit...
   - no cert requests
   - Failed (this is correct)
     Error: Commit failed
     POST of '...': 403 Forbidden

7) Clear cached cert selection from registry

When the commit failed with "forbidden", did that clear the auth cache
in the registry? If not, what was the exact error message?
I've changed TSVN to clear the cached cert index in case of
authentication errors. But maybe the "403 Forbidden" doesn't get
translated by the svn library into an auth error code.

Anyway: I've committed the e_capi patch now, so all nightly builds will
use it from now on. Note however that this change won't get backported
to the stable branch since it's a major change and not a bugfix.


   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 2013-02-26 20:25:04 CET

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

This site is subject to the Apache Privacy Policy and the Apache Public Forum Archive Policy.