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

Hi Stefan,
Cool. I'll grab the next nightly build.

See the attached from some screen shots of the "forbidden" message when trying to WRITE to a READ-ONLY directory. It did NOT clear the auth cache in the registry -- did NOT request a new cert choice. It's almost identical with our current version (1.7.11) doing the same thing... (that screen shot is also in the PDF)

Do you know yet which stable branch this change will appear in? We'd like to keep an eye for it.
We'll use the nightly build for now.

Thanks.
Bob

Bob Bogardus - DMDC Contract Support
DAP Development
robert.k.bogardus.ctr_at_mail.mil
831/583-2400x4236
DSN 878-2951

-----Original Message-----
From: Stefan Küng [mailto:tortoisesvn_at_gmail.com]
Sent: Tuesday, February 26, 2013 11:25 AM
To: Bogardus, Robert K Jr CTR DODHRA DMDC (US)
Cc: Long, Charles A CIV DODHRA DMDC (US); Calmus, Michael G CTR OSD (US); Jennings, Jared L CTR (US); Dale, Delmar; Dale, Delmar W Jr CTR DODHRA DMDC (US); users
Subject: Re: TortoiseSVN with DoD CAC (Smart Card) configuration help

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
    HKCU\Software\TortoiseSVN\CAPIAuthz
    ...

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.

Stefan

-- 
        ___
   oo  // \\      "De Chelonian Mobile"
  (_,\/ \_/ \     TortoiseSVN
    \ \_/_\_/>    The coolest interface to (Sub)version control
    /_/   \_\     http://tortoisesvn.net
------------------------------------------------------
http://tortoisesvn.tigris.org/ds/viewMessage.do?dsForumId=4061&dsMessageId=3049913
To unsubscribe from this discussion, e-mail: [users-unsubscribe_at_tortoisesvn.tigris.org].